You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
With http.proxy set and http.proxySupport to override, trying to connect to a server through the proxy doesn't work (using something like ssh -o ProxyCommand="connect-proxy -H ..." works).
To Reproduce
Steps to reproduce the behavior:
Set http.proxy
Try to connect to proxy-only server
See error
Desktop
OS: Win
VSCode Version 1.35.1
Extension Version 1.12.7
Extension Logs from Startup
[06-18 15:23:13] [debug] Local ident: 'SSH-2.0-ssh2js0.4.2'
[06-18 15:23:13] [debug] Client: Trying 192.168.xx.xx on port 22 ...
[06-18 15:23:23] [debug] Outgoing: Writing DISCONNECT (BY_APPLICATION)
[06-18 15:23:23] [error] Error: [192.168.xx.xx]: Timed out while waiting for handshake
In #440, microsoft/vscode#60773 was mentioned, but that bug has been closed and the issue still persists.
The text was updated successfully, but these errors were encountered:
I encounter the same problem - and indeed everybody working with a the Google Cloud will, too: It is recommended to connect to virtual machines on the Google Cloud via a bastion server [LINK]. The connection needs to be created running the "gcloud" command line utility and this currently cannot be configured in vscode-sftp. Especially, the implemented "connection hopping" functionality cannot handle this setup.
On the command line this can easily be achieved by setting a proxy command in .ssh/config and Microsofts own ssh-connection plugin [LINK] can easily handle this setup.
@development team: Could you please verify, if the same functionality can be implemented in vscode-sftp as well?
Do you read the FAQ?
Describe the bug
With
http.proxy
set andhttp.proxySupport
to override, trying to connect to a server through the proxy doesn't work (using something likessh -o ProxyCommand="connect-proxy -H ..."
works).To Reproduce
Steps to reproduce the behavior:
http.proxy
Desktop
Extension Logs from Startup
In #440, microsoft/vscode#60773 was mentioned, but that bug has been closed and the issue still persists.
The text was updated successfully, but these errors were encountered: