-
Notifications
You must be signed in to change notification settings - Fork 257
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]: SSH-Agent Forwarding stoped working #9662
Comments
Does it make a difference if you set |
Yes If I set this option to false the agent will be forwarded and I can tunnel to the next host |
I have been seeing the issue same as microsoft/vscode#168202 since Mar 22, 2024. Disabling
|
I had the same issue today. Disabling |
@roblourens It worked, thanks! Just make sure to reload window afterwards |
I just went back to still available older versions of the extension and
|
Same issue here, also fixed by disabling remote.SSH.useExecServer |
Confirmed this problem happened for me with plugin version |
If the remote Server has no connection to the Internet then the upgrade Prozess of VSCode Remote Server runs into some timeouts. |
Can confirm |
Wanted to comment that this still appears to be an issue for me too, but that "remote.SSH.useExecServer": false seems to solve the issue too. |
Is there an existing issue for this bug?
Required Troubleshooting Steps
remote.SSH.useLocalServer
settingConnect Locally
It connects successfully
->
No response
Expected Behavior
I would expect to get the ssh-agent forwarded to the ssh client. But that isn't working anymore.
If I directly connect to the same Host, the ssh agent is forwarded, and can be used.
Steps To Reproduce
ForwardAgent yes
is setRemote-SSH Log
Remote-SSH Log
Anything else?
ssh-add -l
via direct ssh connection to the hosts lists the same keys as on the notebook I connected to the host. These Keys are also set so use on other hostsssh-add -l
got the following output, when used in the VS Code Bash Terminal.VS Code Version
With VS Code Version does it work!
The text was updated successfully, but these errors were encountered: