microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
164.54k stars 29.4k forks source link

Stuck in Downloading VS Code Server for Remote SSH Connection #224279

Closed etkaar closed 6 days ago

etkaar commented 3 months ago
VS Code Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:08:12.169Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Linux x64 6.5.0-45-generic

Remote - SSH Extension Version: v0.112.0

The issue #192564 with the Remote - SSH extension unfortunately is still present. Once I want to connect to a Linux SSH server (in my case Debian 12 Bookworm) I get stuck with the message "Setting up SSH Host: [Hostname] Downloading VS Code Server":

image

I then connected to the server and looked what happens there actually. It is this line:

wget --tries=1 --connect-timeout=7 --dns-timeout=7 -nv -O vscode-server.tar.gz https://update.code.visualstudio.com/commit:f1e16e1e6214d7c44d078b1f0607b2388f29d729/server-linux-legacy-x64/stable

When I tried to download it manually, it also gets stuck. It stays at Connecting ... connected. forever:

wget https://update.code.visualstudio.com/commit:f1e16e1e6214d7c44d078b1f0607b2388f29d729/server-linux-legacy-x64/stable
--2024-07-30 09:44:44--  https://update.code.visualstudio.com/commit:f1e16e1e6214d7c44d078b1f0607b2388f29d729/server-linux-legacy-x64/stable
Resolving update.code.visualstudio.com (update.code.visualstudio.com)... 13.107.246.45, 2620:1ec:bdf::45
Connecting to update.code.visualstudio.com (update.code.visualstudio.com)|13.107.246.45|:443... connected.

On my local Linux server at home though it works:

wget https://update.code.visualstudio.com/commit:f1e16e1e6214d7c44d078b1f0607b2388f29d729/server-linux-legacy-x64/stable
--2024-07-30 11:46:17--  https://update.code.visualstudio.com/commit:f1e16e1e6214d7c44d078b1f0607b2388f29d729/server-linux-legacy-x64/stable
Resolving update.code.visualstudio.com (update.code.visualstudio.com)... 13.107.246.45, 2620:1ec:bdf::45
Connecting to update.code.visualstudio.com (update.code.visualstudio.com)|13.107.246.45|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://vscode.download.prss.microsoft.com/dbazure/download/stable/f1e16e1e6214d7c44d078b1f0607b2388f29d729/vscode-server-linux-legacy-x64.tar.gz [following]
--2024-07-30 11:46:17--  https://vscode.download.prss.microsoft.com/dbazure/download/stable/f1e16e1e6214d7c44d078b1f0607b2388f29d729/vscode-server-linux-legacy-x64.tar.gz
Resolving vscode.download.prss.microsoft.com (vscode.download.prss.microsoft.com)... 152.199.21.175, 2606:2800:233:1cb7:261b:1f9c:2074:3c
Connecting to vscode.download.prss.microsoft.com (vscode.download.prss.microsoft.com)|152.199.21.175|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 57745503 (55M) [application/octet-stream]
Saving to: ‘stable’

stable                                                      100%[=========================================================================================================================================>]  55,07M  27,9MB/s    in 2,0s    

2024-07-30 11:46:19 (27,9 MB/s) - ‘stable’ saved [57745503/57745503]

wget seems also to ignore the timeout, so something really awkward is going on as the connection seems not to be refused or aborted, but it hangs for unknown reason.

travis-r6s commented 3 months ago

Guessing there is a bigger issue, as when I just try visiting the insiders.vscode.dev site it either times out, or shows the below: image

Edit: Just seen https://azure.status.microsoft/status

roblourens commented 3 months ago

Still an issue @etkaar? Maybe you can try wget with the -v flag

etkaar commented 3 months ago

Yes, still present. wget with -v flag doesn't change anything:

wget -v https://update.code.visualstudio.com/commit:f1e16e1e6214d7c44d078b1f0607b2388f29d729/server-linux-legacy-x64/stable
--2024-07-31 00:24:20--  https://update.code.visualstudio.com/commit:f1e16e1e6214d7c44d078b1f0607b2388f29d729/server-linux-legacy-x64/stable
Resolving update.code.visualstudio.com (update.code.visualstudio.com)... 13.107.246.45, 2620:1ec:bdf::45
Connecting to update.code.visualstudio.com (update.code.visualstudio.com)|13.107.246.45|:443... connected.
etkaar commented 3 months ago

Unfortunately this issue is still present, it's loading forever:

image

pluveto commented 2 months ago

Same issue since 9/11 update

HoseynHeydari commented 2 weeks ago

Unfortunately this issue is still present, it's loading forever:

image

VS Code Version: 1.95.1 Commit: 65edc4939843c90c34d61f4ce11704f09d3e5cb6 Date: 2024-10-31T05:14:54.222Z Electron: 32.2.1 ElectronBuildId: 10427718 Chromium: 128.0.6613.186 Node.js: 20.18.0 V8: 12.8.374.38-electron.0 OS: Windows_NT x64 10.0.19041

Remote - SSH Extension Version: v0.115.0

I have this issue for the Xenial server and no problem for the Jammy server.

Edited: I'm using LOLINTERNETZ/vscodeoffline and this pull request solved my problem.

roblourens commented 2 weeks ago

And do you all see the same thing if you run the wget command manually? What is your network configuration like, are you behind a corporate proxy or something else that could mess with things?

joshspicer commented 2 weeks ago

If you get a chance to run the wget command manually, could you also try with and without the --read-timeout flag? If that helps we can look into incorporating it. On my machine that flag has a 900 seconds default timeout

vs-code-engineering[bot] commented 6 days ago

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

etkaar commented 6 days ago

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

Excuse me?

HoseynHeydari commented 4 days ago

@etkaar While using the vscodeoffline project this happens to me. Then I downloaded vscode-server for xenial and manually uploaded it to vscarts folder. Remote-ssh extension used it and the problem was solved. Are you trying remote-ssh connecting to the internet?

etkaar commented 4 days ago

Yes, it was pointing to public IPv4 addresses, no local servers. I now use Geany instead in conjunction with SFTP.