Skip to content

Unable to configure filesync or connect via SSH #131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
matifali opened this issue Apr 9, 2025 · 2 comments
Open

Unable to configure filesync or connect via SSH #131

matifali opened this issue Apr 9, 2025 · 2 comments

Comments

@matifali
Copy link
Member

matifali commented Apr 9, 2025

While trying out Fileync in v0.3.0, It always fails with this error.

I have tried,

  1. Quitting and Restarting Coder Desktop
  2. Uninstalling and Reinstalling Coder Desktop
  3. Logging Out and Logging back in
Image

Additionally, I am using the latest Coder CLI, which has the SSH suffix changes for config-ssh.

So I tried coder logout, and the error updates to,

Image

This makes me think that Coder Desktop is trying to use the CLI instead of the Coder Connect tunnel.

Here is the relevant ~/.ssh/config snippet

# ------------START-CODER-----------
# This section is managed by coder. DO NOT EDIT.
#
# You should not hand-edit this section unless you are removing it, all
# changes will be lost when running "coder config-ssh".
#
Host coder.* *.coder
        ConnectTimeout=0
        StrictHostKeyChecking=no
        UserKnownHostsFile=/dev/null
        LogLevel ERROR
        ProxyCommand /usr/local/bin/coder --global-config "/Users/matifali/Library/Application Support/coderv2" ssh --stdio --ssh-host-prefix coder. --hostname-suffix coder %h
# ------------END-CODER------------

Additional Info
Coder CLI version: Coder v2.21.0-devel+44ddc9f65 Tue Apr 8 14:35:13 UTC 2025
coder/coder@44ddc9f

@ethanndickson
Copy link
Member

ethanndickson commented Apr 10, 2025

I was able to reproduce a similar issue running Coder Desktop v0.3.0, and with an SSH config applied by the CLI running v2.21.0-devel+f2fb0caf4. I was only able to reproduce an issue when creating a file sync session against a workspace for the first time, where the Mutagen agent binary needs to be copied across, which might take some time.

2025-04-10 14:46:48.720321 [I] [sync.sync_WvGKVCEX] Beta connection failure: unable to connect to endpoint: unable to dial agent endpoint: unable to install agent: unable to copy agent binary: unable to run SCP process: Connection timed out during banner exchange\r...

Against a workspace with the agent binary already installed, I found no issues.

@ethanndickson
Copy link
Member

Same issue: coder/coder#6685

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants