Description
Summary
I use Zed to connect via ssh to 3 different Servers, that i manage. All of them have a Debian 12 - Docker - Traefik - Crowdsec Setup. On 1 of those 3 I get Connection Issues with Zed (since the beginning of March 2025).
It seams to have problems with symlinks created by Crowdsec.
Strangely it does not have the same problems with the other 2 Servers.
Symlink Issues have been discussed here (e.g. #20143) but i wanted to add the strange behaviour of my Setup, where 1 of 3 Servers does not like to be connected to.
Issue Description
When connecting to a VPS with CrowdSec installed via Zed's remote development feature, the connection fails with numerous "error reading target of symlink" errors. This issue only occurs with Zed editor, while VS Code, Windsurf, and terminal connections work fine.
Environment
- Zed version: Latest (as of March 29, 2025)
- Server OS: Debian 12
- Docker setup with CrowdSec v1.6.8
- Traefik and CrowdSec stack
Steps to Reproduce
- Set up a VPS with Debian 12, Docker, Traefik, and CrowdSec
- Configure CrowdSec with standard collections (http-cve, base-http-scenarios, etc.)
- Attempt to connect to the VPS using Zed remote development
Error Logs
The connection fails with numerous errors like:
error reading target of symlink "/opt/containers/traefik-crowdsec-stack/data/crowdsec/config/scenarios/http-w00tw00t.yaml": No such file or directory (os error 2)
Followed by:
[ERROR] (remote proxy) encountered error while forwarding messages: stderr_task failed
[ERROR] proxy process terminated unexpectedly
Expected Behavior
Zed should successfully connect to the remote server and handle symlinks properly, as other editors like VS Code do.
Actual Behavior
Zed's remote server crashes when encountering symlinks in the CrowdSec configuration directory, making it impossible to connect to the VPS.
Additional Information
- The issue appears to be specific to how Zed handles symlinks in Docker volume mounts
- The problem occurs even after copying actual files instead of symlinks
- The issue persists across CrowdSec version updates and configuration changes
- Other remote development tools handle these symlinks correctly
Workarounds Attempted
- Reinstalling CrowdSec
- Updating CrowdSec to v1.6.8
- Copying configuration files from a working server
- Changing ownership of directories
- Recreating the configuration structure
None of these workarounds resolved the issue.
Zed Version and System Specs
Zed: v0.179.4 (Zed)
OS: Linux Wayland fedora 41
Memory: 15.3 GiB
Architecture: x86_64
GPU: Intel(R) UHD Graphics 620 (WHL GT2) || Intel open-source Mesa driver || Mesa 25.0.2