Problem
When conne ting to a workspace through the VS Code extension from behind a corporate HTTP proxy, the connection hangs at "Setting up SSH Host…" and eventually times out. The root cause is that the ProxyCommand generated by the extension runs coder ssh --stdio without any proxy configuration: no proxy flag is passed, and no proxy environment variable is injected into the subprocess. The coder CLI therefore reaches the deployment only if HTTP_PROXY/HTTPS_PROXY happen to already be present in the environment VS Code inherited.
The extension does honor http.proxy for its own API client but that setting is never propagated to the SSH tunnel subprocess, so it has no effect on the actual connection.
Expected behavior
The extension uses the configured proxy (http.proxy, falling back to HTTP_PROXY/HTTPS_PROXY, and honoring coder.proxyBypass/http.noProxy) for the SSH tunnel, so the connection succeeds.
Environment
- OS: Windows
- VS Code with the Remote - SSH extension (ms-vscode-remote.remote-ssh)
- Coder extension version: 1.15.0
- Network: behind a corporate HTTP proxy; the Coder deployment is reachable only via that proxy
- http.proxy configured in settings.json
Problem
When conne ting to a workspace through the VS Code extension from behind a corporate HTTP proxy, the connection hangs at "Setting up SSH Host…" and eventually times out. The root cause is that the ProxyCommand generated by the extension runs coder ssh --stdio without any proxy configuration: no proxy flag is passed, and no proxy environment variable is injected into the subprocess. The coder CLI therefore reaches the deployment only if HTTP_PROXY/HTTPS_PROXY happen to already be present in the environment VS Code inherited.
The extension does honor http.proxy for its own API client but that setting is never propagated to the SSH tunnel subprocess, so it has no effect on the actual connection.
Expected behavior
The extension uses the configured proxy (http.proxy, falling back to HTTP_PROXY/HTTPS_PROXY, and honoring coder.proxyBypass/http.noProxy) for the SSH tunnel, so the connection succeeds.
Environment