Coder Desktop on Windows v0.6.1 cannot setup File Sync
I am trying to use the following combo:
1. Windows 11
2. Coder v2.23.1
3. Coder Desktop v0.6.1
I can have Coder Desktop connect to my Coder instance and see my workspaces. I tried to setup a file sync but I am getting errors. I cannot seem to copy the text from the window so I've attached screenshots. I also tried putting the remote path in manually and received a different error.
I understand Coder Desktop is in beta so this post is more just an FYI. We already use mutagen with our Coder workspaces today over SSH. One of the common issues is which
ssh.exe is used.
14 Replies
it looks like it couldn't access the workspace in question to list directories and start the sync up for the first time
is your workspace healthy?
cc @BigCheeZ
I've been away and just got back to this issue. The workspace is healthy according to Coder. I did update to Coder v2.23.2 and Coder Desktop v0.6.3 to see if there was any change in behavior. It fails in the same way.
Sorry forgot to tag @Dean in my reply
it happens every single time, even after rebuild? or is this the same agent the whole time?
@BigCheeZ
It happens every single time. I'm not sure how this works under the hood, so here is some more info if it helps.
1. I can SSH in using the
coder ssh from PowerShell
2. The workspace is using a custom docker image based off of codercom/enterprise-desktop (based off ubuntu:noble)
If there is any debug info I can provide, let me know.
@Deancould you provide
coder-desktop-serivce.log (probably in C:\Program Files\Coder Desktop)?
@BigCheeZ@BigCheeZ
Sorry it took a while. See attached file.
@Dean
@BigCheeZ you seem to have the following interfaces on your system:
- Ethernet
- Ethernet 3
- vEthernet (Default Switch)
I'm guessing the default interface is "Ethernet" but the Coder deploiyment is behind vEthernet
The log line below makes me believe you're running into this known issue: https://github.com/coder/coder-desktop-windows/issues/147
GitHub
When connecting to a Coder server behind a different VPN, workspace...
When using another VPN like a corporate VPN (e.g. Tailscale, tested with exit nodes enabled) or a consumer VPN (e.g. Mullvad) to access Coder, workspaces stay "yellow" and are unreachable...
FYI I'm working on this bug right now, but it might take a few weeks to get released
@Dean you are right. This happens when going through a different VPN. If I get directly on the network with the Coder server then Coder Desktop works. Thanks for the help.
marking as to-github
@Phorcys closed the thread.