-
Notifications
You must be signed in to change notification settings - Fork 336
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
Connecting with SSH timed out #1031
Comments
@raine-works are you experiencing the same problem with the latest v0.5.6 release? |
I updated to v0.5.6 and I am still seeing the same error.
I tried deleting that workspace and creating a new one after updating. I am seeing the same results. The devpod cli ssh command works but the standard ssh command does not. |
Hi @raine-works can you please to a test for me? Can you open the ssh config file (It should be Like:
So we can get some more useful logs from your command? |
Here is my SSH config.
Here are the logs I am seeing after adding the --debug flag.
The "inject script" portion repeats endlessly. |
Thanks @raine-works |
I assume this can be done by deleting the provider and recreating it? I did that and Its still not working. I am seeing the same error message. |
Can you post it? |
|
@raine-works, what OpenSSH version are you using? The default OpenSSH version from Windows is VERY old (8.1), so downloading the latest release from PowerShell/Win32-OpenSSH is probably necessary. Alternatively, if you don't make use of the SSH agent, you can disable the Windows service to fix it as well. |
OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3 |
Would you be open to upgrading by following this guide from Microsoft? It's most likely that the source (8.6) is incompatible with the target (likely 9.x). |
I updated to OpenSSH version 9.5.
I am still seeing a similar error.
|
So that "error" might happen a couple of times while the agent process is getting started. Then it normally goes away once the agent is ready to accept commands. Does it just continue to spin like that indefinitely? |
The longest I've let it run is for about 5 minutes. This is the log output after 3 minutes.
|
I think there is a typo in 'https://github.com/loft-sh/devpod/releases/download/v0.5.6', the URL is 404. |
The default agent URL under general in the settings is |
So that download URL is just the first fragment. The file name gets appended to it based upon the target systems OS and architecture. It was a little misleading when I was debugging that area as well, but that part is just fine from what I've seen. |
I removed the agent from the remote machine and tried re-creating the workspace. The agent was successfully re-installed on the remote machine, but still hangs when trying to open a connection. |
I find it strange that the devpod cli ssh command can connect to the remote devcontainer but open-ssh in powershell can't.
|
I copied the SSH config from the Windows file system and pasted it in the SSH config in WSL. I adjusted the proxy command to use /mnt/c.
In WSL it worked immediately.
My issue must be related to the open-ssh version like you suggested before. Although updating to 9.x didn't solve the problem. |
@raine-works try using the new version of the ssh provider, I had the same problem as you. The new version fixed the problem for me. (Even though it introduced another bug :/) |
Hallelujah! It works!!!! |
What happened?
Attempting to connect to provider remote host via SSH times out with error: "Waiting for Devpod agent to come up..." Cannot connect via SSH with VSCode or the terminal. The Devpod CLI SSH command works as intended.
What did you expect to happen instead?
Devcontainer to be accessible via SSH.
How can we reproduce the bug? (as minimally and precisely as possible)
My
devcontainer.json
:My
Dockerfile
:My SSH
config
:Local Environment:
devpod 0.5.5
DevPod Provider:
Anything else we need to know?
I am able to connect to the remote host via SSH directly.
Docker engine on remote host has the following custom remote access config:
The text was updated successfully, but these errors were encountered: