vscode: Unable to create remote tunnel through a proxy
Type: Bug
If you create a remote tunnel, you will get an error as below.
ubuntu@devserver:~/bin$ ./code tunnel
*
* Visual Studio Code Server
*
* By using the software, you agree to
* the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and
* the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement).
*
✔ Do you accept the terms in the License Agreement (Y/n)? · yes
To grant access to the server, please log into https://github.com/login/device and use code *******
✔ What would you like to call this machine? · ec2-dev
[2022-12-15 17:20:34] info Creating tunnel with the name: ec2-dev
[2022-12-15 17:22:46] warn Error connecting to relay, will retry: error connecting to tunnel: websocket error: IO error: Operation timed out (os error 110)
[2022-12-15 17:22:46] error Error connecting to tunnel endpoint: error connecting to tunnel: websocket error: IO error: Operation timed out (os error 110)
[2022-12-15 17:25:03] warn Error connecting to relay, will retry: error connecting to tunnel: websocket error: IO error: Operation timed out (os error 110)
The network is connected to the internet through a proxy.
Extension version: 0.23.0 VS Code version: Code 1.74.1 (1ad8d514439d5077d2b0b7ee64d2ce82a9308e5a, 2022-12-14T10:30:51.966Z) OS version: Windows_NT x64 10.0.19044 Modes: Sandboxed: No Remote OS version: Linux x64 5.15.0-1026-aws Remote OS version: Linux x64 5.15.0-1026-aws
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Core™ i5-10310U CPU @ 1.70GHz (8 x 2208) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off |
| Load (avg) | undefined |
| Memory (System) | 7.73GB (1.33GB free) |
| Process Argv | –crash-reporter-id 131ce736-6fa7-46d5-80be-2c46842e3916 --crash-reporter-id 131ce736-6fa7-46d5-80be-2c46842e3916 |
| Screen Reader | no |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | Dev Container: Node.js & TypeScript @ ssh://dev |
| OS | Linux x64 5.15.0-1026-aws |
| CPUs | Intel® Xeon® Platinum 8175M CPU @ 2.50GHz (2 x 2500) |
| Memory (System) | 3.77GB (2.34GB free) |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | Dev Container: Java @ ssh://dev |
| OS | Linux x64 5.15.0-1026-aws |
| CPUs | Intel® Xeon® Platinum 8175M CPU @ 2.50GHz (2 x 2500) |
| Memory (System) | 3.77GB (2.34GB free) |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyonecf:30548226
vscccc:30610679
pyindex848cf:30577861
nodejswelcome1cf:30587006
2e4cg342:30602488
gswce1:30612156
iaj6b796:30613358
89544117:30613380
fim-prod:30623723
vscup:30628656
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 27 (15 by maintainers)
HTTPS_PROXY=localhost:8080and then runcode-insiders tunnel@connor4312 I still have this issue with 1.77.0-insider, behind a corporate proxy.
warn Error connecting to relay, will retry: error connecting to tunnel: proxy connection failed: failed to lookup address information: Name or service not knownUnfortunately, it is not possible to get the name of the software being used for the proxy server due to company policy.