-
Notifications
You must be signed in to change notification settings - Fork 259
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" when open Remote Workspace #7324
Comments
Log here
|
Same here. it works when I move the remote code folder, so weird. |
It seems like we tried to open a terminal to connect with ssh, and it did eventually connect, but took a really long time. Is there a difference if you set If that doesn't work, is there a difference if you set @Tyriar just a guess, is there any reason a local hidden terminal might take a long time to start when the remote resolver is running, in 1.72? |
@roblourens not that I'm aware of, I think the main difference is the hidden terminal's dimensions would be different. Did something happen on the client side to trigger the connection working? |
I tried to set this to true but it doesn't work.
It has already been set true. As in #7326, the issue comes with the new version 1.72 VSCode, I have to go back on 1.71.2 temporary for working. |
I may meet same issue. |
I could reproduce with this.
|
This same problem occurs for me as well - see issue 7327 |
Could someone do this
Also, I was wondering whether Workspace Trust is relevant here - is anyone opening workspaces that are not trusted? |
Here is "Log (Window)" output in my environment. |
I can repro this. Sorry for the break, working on a fix. One workaround is to set Steps I'm using, adapted from above.
What I know right now:
|
I don't see what has changed, but I think something like this is happening:
None of this code has changed recently, I'll have to check out an old version. |
https://github.com/microsoft/vscode/pull/159666/files is probably the culprit |
The local terminal contrib has to be registered early: https://github.com/microsoft/vscode/pull/159666/files#diff-75105ca3082321c8fcb66566fc19044ad68fe59240b5326dd66e1c2dcbc235c1R24 And also this needs to not wait on LifecyclePhase.Restored: microsoft/vscode@07ceed3#diff-f7c1e5b972aa08636e0ecff0d5af7ad06b3153173dee39093cd280ac0656f988R100 |
Thanks for this. It seemingly was set to |
The same for me. |
I tried explicitly setting this to true in my user settings.json on Windows but it still doesn't work for me. |
|
Yeah, I have that pop up too. There is another open issue on this problem. But you can just ignore it. |
This should be fixed in the latest VS Code Insiders, please let me know if not! |
Thanks for the heads up. I see the same error as before, which is a successful connection then immediate time-out. Here's the log for one of the connections. I hid the hostname and MOTD but it connects successfully.
|
@citizenrich, this seems to be a different issue- could you please file a new bug in the remote-release repo. Thanks! |
Thanks @eleanorjboyd. #7520 I would note that remote-ssh now connects successfully on two other hosts, just not two others. |
This way works! |
@CMinHong, is this issue you are experiencing on the new insiders? If not can you please try it there and let me know if the issue persists. Thanks! |
@roblourens wrote
@roblourens where is this state saved? I would have loved to just delete it altogether but I can't find it. thanks |
I am facing this issue OSX ventura, I did not get any solution, but then even formatted my OSX and downgraded to Monterey , and still the same. |
I've experienced the same problem. Once it errored out, I closed the secondary sidebar, retried, and it worked perfectly fine. Thanks to those who figured this out. |
@MitchTalmadge Thanks for the response, I read this couple of time, but not sure exactly what that means. Closing the secondary sidebar means ?? I have attached the screenshot of how it looks likes, could you please point out the next steps ?? |
Oh My God! I can't believe all my troubles are caused by me using the secondary side bar! I can't wait for this stupid bug to be fixed. Thanks to the contributors. |
Hello @eladeyal-intel the place where you can find and delete this saved workspace state is different per machine type but here is the location for each type: https://code.visualstudio.com/docs/setup/uninstall#_clean-uninstall |
Additionally for any of those still experiencing errors please make sure you try the new insiders version of VS Code. If you tried this version and it is still not working please submit another issue to this repo so we can reduce clutter in this thread. Thanks! |
See my comment linked below for exact steps to mitigate |
I'm using 1.73.1 (system setup),still have this problem. |
@CMinHong Same issue |
@santhoshcameo |
Using VS Code 1.73.1, also confirmed that closing the sidebar fixes the issue. @lurk26 you're a life saver thank you! |
1.73.1 is the stable build- 1.74 should have the fix! This build is only accessible via VS Code insiders. |
Even in 1.74 I got the broken pipe issue, but then below solution solved in MAC OSX The problem solved <3 this issue started since 1 month for me, and just now solved it by adding the following line into
|
1.74 definitely does NOT have a fix. SSH use is now worse than ever, to the point whereby it starts up successfully then pies me off 10 seconds later claiming it's dropped, then doesn't connect again. (This is completely unusable.) I noticed the command being used in the output terminal: [Edit] Log from "Remote - SSH" output when it happens:
For some reason it just suddenly decided it was no longer fine? (This is not a network issue. In parallel I've got another SSH session open to the same remote host for terminal use, and remains up and working all day.) |
This issue seems to be getting wrapped up into multiple different issues with the Remote - SSH extension. I can confirm that, specifically, the issue with opening a Remote SSH session with the Secondary Side Bar open is fixed in 1.74. Tested on:
|
I can also confirm that the issue with the secondary side bar and remote SSH has been fixed for me in 1.74. |
+1, I can confirm it works. I suggest to create separate reports for SSH extension problems. |
@AdamReece-WebBox if you could please file a new issue using this form, we can work to troubleshoot your issue, thanks! |
Hello,
After the last VSCode update, I have this strange bug. I still can connect to host with Remote-SSH, by clicking "Connect to host" or "Connect current window to host", but when I tried to open a saved workspace (from file on remote), the extension has an "Timed out" error.
Oddly, if I create a new workspace and save as a new file (on remote), I can reconnect to this new workspace few times after this creation, but after a while, the same error occurs again.
In the log, we can see there is "got some output, clearing connection timeout" very far after several Timed out errors.
Does this issue occur when you try this locally?: N/A
Does this issue occur when you try this locally and all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: