-
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
VSCode remote SSH to container always fails/times out in Windows #972
Comments
Also may be related to #521 in which case I see the response that theres need for work on the windows SSH and potentially missing unix utilities. So that may be the cause. If so, I suspect this can be closed and I can just +1 that. |
Hi @jansselt, thanks for reporting the issue. Could you try to increase the vscode SSH timeout and see if that helps? (Second comment on this stackoverflow question: https://stackoverflow.com/questions/59978826/why-ssh-connection-timed-out-in-vscode) |
I actually stumbled across that SO while trying to figure it out myself. I did try this and it did not work for me. I let it run for 10 mins or so. And it just keeps logging "Waiting for devpod agent to come up" occasionally. However, I will try once more later when I'm back in my network to make sure that is still the case. |
If it doesn't work out we'll take a look, thanks 👍 |
thanks @rodenj1 |
I can confirm the same problems per other users above ... works with vscode browser and
|
+1 I am facing the exact same problem my peers have. The following is my setup:
Results are the same described above.
|
Same experience as me. I am connecting via tunnel to my remote machine and I am forwarding ssh ports manually (2222). Web vscode works though. |
I have the same problem. vscode shows 'Opening Remote...' forever.
Windows 11 Pro 23H2 Please looking into this or if there is any workaround. Really appreciated. |
Hi all! Can you please attach the following tests:
Thanks a lot! |
try from vscode, there is no error, it just hang at
I have |
Yeah, I confirm I can ssh with |
update from my side. It was actually a false alarm from my side. For windows there is additional selection popup (I didn't noticed). After choosing 'Linux' it works for me. Thanks! |
Can confirm I'm running into the same issue on Windows 10 22H2 Build 19045.4529 with OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2 using the DevPod v.0.5.16 with SSH provider v0.0.12 instead of latest because of this bug. |
Hey @omniproc, we've just release v0.0.15 of the ssh provider. Does this fix your issue? |
When I try to launch my workspace with v0.0.15 it still fails with time out error. I am using the Windows ssh version, does it matter, or do I need to update to a later version? |
@jzazo @rodenj1 can you try to use the USE_BUILTIN_SSH provider option? If this doesn't work I'd need more information on your setups |
I try to run the following command to use built-in ssh client but it fails:
which succeeds. I don't know why the provider does not work with the built-in ssh client, but the ssh command works... |
It works for me! It took some doing, but it is working. Here is what I had to do.
For some reason it would not work by just enabling "Use Builtin Enabled". Let me know if you would like logs or anything on this. As a reminder, here is my config. Source system: SSHed system to System: |
The SSH "Use Builtin Enabled" doesn't work on Windows 10.. ssh provider has issues with Windows that's why the added that option. I think that the issue should be resolved on the side of devpod. |
I still haven't been able to make it work. I deleted everything as @rodenj1 indicated and then:
Can I test the built-in ssh client for running |
@jzazo You'll need to specify the IdentityFile separetely in your ssh config if you need to use the builtin ssh client, check out this section in the ssh provider |
Thank you! Adding the following section to my
|
Well.. To be true ssh_provider doesn't work even with "Use Builtin Enabled".
PS. |
What happened?
devpod starts container on remote host and opens VSCode but then is never able to SSH into the container.
What did you expect to happen instead?
VSCode to open and connect to the container. This works without issue for me in Linux. In Windows it times out no matter how long I set the timeout maximum.
How can we reproduce the bug? (as minimally and precisely as possible)
For me, create any workspace and open in VSCode. I am using an SSH provider.
My
devcontainer.json
:Local Environment:
DevPod Provider:
Anything else we need to know?
I am experiencing an issue similar to this issue I believe #850
The container is created just fine. I can use VSCode Browser just fine. However if I try to use VSCode, it always fails to SSH connect to the container.
This only happens for me on Windows. Linux works with no issues. I don't have a mac, so can't test that.
The text was updated successfully, but these errors were encountered: