Remotte-SSH : can't install the Cursor server

Support Bug Reports
,
9

Thanks for the detailed logs, they really help.

One important thing up front. This is not the 1.0.51 regression where it fails with Could not resolve hostname 7b22..., so downgrading wouldn’t help. Your SSH tunnel comes up fine, the install script starts on the server, it kills old servers, then it fails exactly at the step where it should download cursor-server. noexec and disk space look fine, so workaround A or B isn’t relevant here.

Key point. cursor-server is downloaded from cursor.blob.core.windows.net, while VS Code downloads its server from a different CDN from Microsoft. So VS Code can work even if the server can’t reach our download host due to firewall or egress rules, or if the artifact returns 404.

First, grab the exact URL from the log. Open Output → Remote-SSH in Cursor. When it tries to connect, you should see a line like server download URL: https://cursor.blob.core.windows.net/remote-releases/.... Copy it exactly so we don’t have to guess the artifact name format.

Then, from the server, as the same user you connect with, run:

curl -IL --max-time 20 https://cursor.blob.core.windows.net/
curl -IL --max-time 20 "<paste the server download URL from the log here>"

If you can’t find the download URL line in the log, use an approximate path for the second curl. The HTTP status code will still tell us what’s going on:

curl -IL --max-time 20 "https://cursor.blob.core.windows.net/remote-releases/3.5.33-aac81804b986d739acab348ed96b8bea6e83cc50/vscode-reh-linux-x64.tar.gz"

How to read the result:

  • It hangs, Connection refused, or times out. Outbound traffic to cursor.blob.core.windows.net is blocked on the server. You’ll need to allow that domain in your firewall, or install the server manually offline. Guide: How to download cursor remote-ssh server manually？
  • It returns 404. The artifact for that build is missing or the path is wrong. Send the output and we’ll dig in.
  • It returns 200 or 206. Network looks fine, so we should look elsewhere. Do a clean reinstall and send the full log:
    • Ctrl+Shift+P → Remote-SSH: Kill VS Code Server on Host...
    • On the server: rm -rf ~/.cursor-server
    • Reconnect and paste the full Output → Remote-SSH log from start to the error, and a bit after.

Send the curl results first. That will tell us right away where to look next.