microsoft / microsoft/vscode-remote-release
[Remote Tunnel] Cannot connect to tunnel though proxy because of socket hang up
Open
@connor4312 is already working on this.
Since Feb 25, 2025.
bug
tunnels
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VSCode Version:1.95.3
- VS Code Remote Tunnel 1.5.2
- Local OS Version: Windows 10
- Remote OS Version: Debian 12
- Remote Extension/Connection Type: Dev Containers/WSL/Remote - Tunnels/VS Code Server
- Logs:
2025-01-16 14:38:04.754 15:50 16/01/2025[error] Error: socket hang up
at re.from (c:\Users\username\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:940980)
at w.<anonymous> (c:\Users\username\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:963273)
at w.emit (node:events:531:35)
at h.forEach.d.<computed> (c:\Users\username\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:680126)
at ClientRequest.emit (node:events:519:28)
at emitErrorEvent (node:_http_client:101:11)
at Socket.socketOnEnd (node:_http_client:528:5)
at Socket.emit (node:events:531:35)
at endReadableNT (node:internal/streams/readable:1696:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
at At.request (c:\Users\username\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:971833)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async E.axiosRequest (c:\Users\username\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:75388)
at async E.request (c:\Users\username\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:76034)
at async E.sendRequest (c:\Users\username\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:69974)
at async E.listTunnels (c:\Users\username\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:64683)
at async c:\Users\username\.vscode\extensions\ms-vscode.remote-server-1.5.2\dist\node\extension.js:2:1201977
at async Y0.h (file:///c:/Users/username/Custom/app/vscode/VSCode-win32-x64-1.95.3/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:114:32825)
at async Promise.all (index 1)
at async t.RemoteTreeDataProvider.refreshTunnels (c:\Users\username\.vscode\extensions\ms-vscode.remote-explorer-0.4.3\dist\node\extension.js:1:7783)
at async Promise.all (index 0)
Steps to Reproduce:
- install VS Code Remote Tunnel
2.configure in Windows env for the account http_proxy and https_proxy
3 follow VS Code Remote Tunnel doc about creating a tunnel through github.com
Note: we have a corporate proxy that does MTIM. Self-signed certificates are deployed at OS level.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.