Cursor Remote-SSH Connection Issue - Mac/Linux to Windows

Bug Reports
1

Version

  • Cursor v0.45.9 (latest release as of writing)

Issue Description

When attempting to connect from Mac or Linux Cursor clients to Windows-based remote SSH servers, the connection fails. The terminal output indicates a 404 error when trying to download the server executable.

Below is a snippet from the Terminal Output
[11:03:58.206] server download URL: https://cursor.blob.core.windows.net/remote-releases/6ea842450e04c5537da4d83d51823fae13bb30f0/cli-win32-x64.tar.gz
[11:03:58.206] Downloading VS Code server locally…
[11:03:58.268] Terminating local server
[11:03:58.271] Resolver error: Error: Failed to download VS Code Server (Server returned 404)

Reproduction Steps

  1. Launch Cursor v0.45.9 on Mac or Linux
  2. Attempt to connect to a Windows-based remote SSH server
  3. Observe connection failure and 404 error in terminal output

Workaround

A temporary workaround has been identified:

  1. First connect to the Windows server using a Windows-based Cursor client
  2. After this initial connection, Mac and Linux clients can successfully connect

Additional Information

  • The issue affects both Mac and Linux (AppImage) clients identically
  • The problem appears to be related to the URL formula used by non-Windows clients when attempting to download the SSH server executable
  • Once the server executable is installed via a Windows client, all subsequent connections work properly

Environment

  • Client OS: macOS, Linux
  • Server OS: Windows
  • Cursor Version: 0.45.9
2

Just one note, the workaround only fixes the issue for the current release version. After the mac client update’s their Cursor, a windows user will have to remote in with a matching newer version. It just seems like the Mac/Linux clients download path to the server installer formulas are incorrect

3

Thanks for the detailed report. We’re aware of this SSH server download issue between Mac/Linux and Windows machines. Your workaround is correct - having a Windows client connect first will install the server, then Mac/Linux clients can connect successfully

You’re also right that this is a temporary fix per version. When the Mac client updates, you’ll need a Windows user with the matching version to connect first. We’re working on fixing the download path formula for non-Windows clients to resolve this permanently

4

Hello, do you know when the fix is planned ?
In the lastest version (0.45.14) I still can’t download the vscode server.

2 Likes
5

me too

6

Same ever since (0.45.14) My Remote-SSH still works Windows → Linux But not my Rpi Linux-arm64. Regular SSH works fine but cursor will Downloading VS Code Server… forever

7

I don’t believe we currently have a Linux ARM64 server that works for Remote SSH currently, but I believe this is on our workload soon!