Remote-SSH connection stalls and never continues #84
Comments
|
Is TCP forwarding enabled on the ssh server? I see the exact same issue where I am testing this and we have forwarding disabled for security reasons. |
There was nothing in |
|
Hm, have you tried the same ssh command with a different client port (i.e. |
|
@davidwin I have the same issue as @joeygibson. The tunnel was established: When I tried to access Also, VS Code shows an error at right-bottom: |
|
I ran |
|
@wqfan Do you know whether Also can you share the logs from the "Remote - SSH" output channel that might explain |
|
@joeygibson I don't understand, did you try to run a curl command or is that an error that was written? |
|
@roblourens I have Here is the full output from "Remote - SSH" channel: Logs from "Log (Window)" channel: |
This warning sounds relevant, can you tell me about your remote OS? And possibly the output of |
|
@roblourens Sure. |
|
@wqfan please open another issue, I realized that you got through the SSH part successfully and |
|
@roblourens Sounds good. I opened: #103 |
|
Hi, I have the same problem. And after some debug in the server, I see this behaviour:
So, I suggest:
Regards. |
|
I have met the similar problem. I followed #75 and solved it. Please find details in #75, as follows are the main operations.
in ~/.ssh/config on local. Hope it will help for you. |
|
After reading through the comments, it's obvious that there could be multiple reasons for a stalled connection, without much logging to tell the difference. What I did to conclude that TCP forwarding was disabled was to:
|
|
I met the same problem of connecting the ubuntu 16 "install" terminal command done Tunnel(40471) stderr: Permission denied, please try again. Tunnel(40471) stderr: xxxx@192.168.111.111: Permission denied (publickey,password). Could not establish tunnel to "111" (Max wait time exhausted). |
|
After adding the And here's what showed up in my terminal: In both cases, |
|
It sounds like tcp forwarding may be disabled for you @joeygibson
Do you know whether that's the case? |
As I said here #84 (comment) I didn't see that it was disabled, so I explicitly enabled it, but to no avail. |
Hi, From my experience, the main problem isn't the tunnel. If you can connect with SSH then the tunnel only fails if the server has disabled tunnels. And this is easy to check it. The real problem is that the end of the tunnel is offline. That's the server starts and after it closes. And for this reason you can't connect. It's quite simple, but it's hard (at time) to determine the cause of the fail. So I suggest to print more logs regading the close of the server. |
|
@joeygibson can you give the contents of And please check for errors in the developer tools (Help > Toggle developer tools) Another problem that came up in another issue is that |
|
@roblourens Here's the contents of the log file: And yes, my in it |
|
Hi @joeygibson , Think on this:
... But the connection can fail if the server CLOSES. Then all connections from the client to the server fails. Please, improve the handle of this case. I belive a lot of problems are related to this cause. Regards. |
|
I also had the issue of |
|
I noticed that both processes that get started on my machine have |
Yes, this is the first cause of this message. However, when this isn't then the most likely cause is that the target port is closed (because the server has terminated).
In this case the most likely cause is that the server is not started or the script has not received (readed) the listening port. |
The script is running. I found the |
|
@joeygibson Are you able to resolve this? I am facing similar issue Remote configuration data at /home/ac043s/.vscode-remote
Error: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.18' not found (required by /home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/node_modules/spdlog/build/Release/spdlog.node) |
|
Getting this from a ubuntu server `> LESSOPEN=| /usr/bin/lesspipe %s
Has anyone been able to resolve this? |
|
Hi, The relevant part is this bug (log copied from the first post) is this: See my comment at #103 (comment) |
|
server: centos |
Exactly the same for me : ( |
|
Somehow these two values never match. Forcing the signed data to be the same as the UUID made it work for me.
Please install newer libstdc++ and point LD_LIBRARY_PATH to there from your login script (.bashrc, but somehow in my workplace it was .bash_login) P/S: While that solves running the node module, I now have problem starting the CPP extension because it requires a new libc, which cannot be easily overriden using LD_LIBRARY_PATH (due to relocation problem), but that is of course off-topic for this ticket. |
|
The "unauthorized client refused" error is being tracked here: #103 I don't believe the OP in this issue is having the same issue, this issue should focus on whatever @joeygibson is seeing which we haven't gotten to the bottom of. Sorry for neglecting this issue, my best guess is still just that tcp forwarding is somehow disabled based on seeing
|
|
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
|
As multiple people suggested, the problem was, in fact, that TCP forwarding was blocked. I tried setting |
No, quite the opposite in 99%! Cases like yours only represent 1%. But I'm glad you could work it out. 😉 |
Tried this on Centos 6 (WHM/cPanel server) without any luck. |
|
Wondering if anyone has any suggestions/best practices concerning allowing TCP Forwarding? The environment I'm working in has set Here's an example of my sshd_config: |
|
See if you can get acceptance for setting |
|
in case it helps anyone: I add similar issue, with error like this: I ran this command in Visual Code: Then re-connecting in Visual Code worked OK. It looks like the Visual Code host on server either got in a hung state OR could not be updated .... |
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
Steps to Reproduce:
Cmd-Shift-P,
Remote-SSH: Connect current window to host...Connection is successful. Remote tools are installed and server is running on remote:
$ ps -ef | grep code
root 281660 1 0 16:36 ? 00:00:00 sh /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/server.sh --port=0
root 281669 281660 5 16:36 ? 00:00:00 /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/node /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/remoteExtensionHostAgent.js --port=0
This shows up:
and it never goes beyond that.
Here's the full log:
The machine can be gotten to through
ssh, obviously, since VSCode was able install and start the server. The server has internet access through a proxy, but there's ano_proxythat covers the IP space my laptop is in.I've let it sit for over half an hour, and it never progresses any further.
If I can provide any further details, please let me know.
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes
Update: The solution to my specific problem is explained here #84 (comment)
The text was updated successfully, but these errors were encountered: