-
Notifications
You must be signed in to change notification settings - Fork 267
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
[Remote-SSH Bug]: "Failed to set up socket for dynamic port forward" on VSCode v1.76 #8132
Comments
I have the same issue. |
Since I need this to work ASAP I have resorted to reinstalling Linux on the remote server with no luck. It (still) seems unable to forward the port, but I have no idea what could be causing that.
|
I have exact same issue with VSCode v1.76. Downgraded to v1.74.3 and it connects just fine. Something broke in VSCode 1.76 version regarding Remote SSH |
This solved it. Thanks so much Alxliv! |
@alxliv This solved the issue. Thank you so much! |
Hello! Sorry for the delay! I am looking into this now. Can someone try downgrading to the remote-ssh extension version 9.6 (the newest version is going to be 0.98 for stable). Does downgrading this fix the issue or is it only on downgrading all of vscode? Secondly what is the type of everyone's local and remote machines? |
Could you send your logs from 1.76 @alxliv ? Thanks! |
@eleanorjboyd , Hi, I wanted to reproduce this issue on VSCode v1.76.0 but could not find download v1.76.0. So I installed the latest version - v1.76.1 and could not reproduce the issue. Remote-SSH works now just fine. I guess this issue somehow got fixed (at least for me) from 1.76.0 to 1.76.1 |
Great news @alxliv! Does it work on 1.78 or is it broken there? |
@eleanorjboyd , 1.78? The latest version of VSCode I can see is 1.76.1 https://code.visualstudio.com/updates/v1_76 |
oops you're right I got my versions mixed up between the vscode version and the remote-ssh extension! It must have been the point fix that was the solution but let me know if it resurfaces. |
I have temporarily solved this problem for now, but I don't know the reason. AllowAgentForwarding no
AllowTcpForwarding no changed to AllowAgentForwarding yes
AllowTcpForwarding yes Note that these two lines appear twice in the file, once at the beginning of the # comment, I uncommented these two lines, and another time at the end of the file, I changed yes to no. systemctl restart sshd
rm -rf ~/.vscode-server/ I now understand that someone appended "no" to the end of the default configuration file and did not delete the comment item, which caused me to see the comment item and mistakenly think it is now in the default state of "yes". |
closing as it seems resolved but please comment again if this is not the case or if confusion persists. |
After updating to 1.78.2, the problem seems to show again. Sometimes it works, but sometimes it does not. Connecting to the same remote server from multiple windows takes a while to wait, if not impossible.
|
@kuang-da This issue has a workaround:microsoft/vscode#132519 (comment) |
I had similar problem one day when using 1.62 although it never happened before. I did |
For me the issue was Tailscale. I updated my .ssh/config by adding the local (non Tailscale) ip to the HostName field |
Is there an existing issue for this bug?
Required Troubleshooting Steps
remote.SSH.useLocalServer
settingConnect Locally
It connects successfully
->
No response
Expected Behavior
When trying to connect to my remote Linux server with my local Windows desktop machine, I get stuck in a loop having to enter my passphrase. It worked fine the day before. As far as I am aware, no settings have been changed.
I can connect to the remote server fine with: My Windows laptop (on the same network), a friend's Windows desktop (on another network), and on a Linux install (On the same desktop machine).
Steps I have tried:
Remote.SSH: Use Local Server
AllowTcpForwarding yes
in/etc/ssh/sshd_config
on the remote server.vscode_server/bin
from remote server.vscode_server
from remote serverSteps To Reproduce
No response
Remote-SSH Log
Remote-SSH Log
Anything else?
No response
The text was updated successfully, but these errors were encountered: