getcursor / cursor

The AI Code Editor
https://cursor.com
24.94k stars 1.55k forks source link

Missing cli-win32-x64.tar.gz File Causes Remote SSH Connection Failure in Cursor (404 Error) #2335

Open nmgvv opened 3 days ago

nmgvv commented 3 days ago

NOTE: We will try our best to check Github Issues, but forum.cursor.com is our main site for bug reports / user feedback. We'd recommend you post there for the fastest response.[ https://cursor.blob.core.windows.net/remote-releases/b1e87884330fc271d5eb589e368c35f14e76dec0/cli-win32-x64.tar.gz Issue Summary:

When attempting to establish a Remote SSH connection using Cursor, the process fails due to the unavailability of the cli-win32-x64.tar.gz file on the specified server. This issue results in a 404 error during the download attempt, preventing successful remote connections.

Steps to Reproduce:

Initiate a Remote SSH connection via Cursor. Observe the download attempt for cli-win32-x64.tar.gz. Encounter a 404 error indicating the file is not found on the server. Expected Behavior:

Cursor should successfully download the necessary cli-win32-x64.tar.gz file from the server, facilitating a seamless Remote SSH connection.

Actual Behavior:

The download attempt for cli-win32-x64.tar.gz results in a 404 error, indicating the file is missing from the server, thereby obstructing the Remote SSH connection process.

Additional Context:

This issue has been reported by multiple users in the Cursor GitHub repository, suggesting a recurring problem with the availability of required files for Remote SSH functionality. For instance, a similar issue was documented in Issue #858, where users experienced failures in establishing SSH connections due to missing server files.

Request for Resolution:

Please investigate the server hosting the cli-win32-x64.tar.gz file to ensure its availability and accessibility. Providing the necessary files will enable users to utilize the Remote SSH feature in Cursor without encountering download errors.

frederick-wang commented 1 day ago

‌‌I encountered the same problem:

[14:09:38.149] Got request to download on client for {"artifact":"cli-win32-x64","destPath":"C:\Users\frederick\.cursor-server/vscode-cli-b1e87884330fc271d5eb589e368c35f14e76dec0.zip"} [14:09:38.150] server download URL: https://cursor.blob.core.windows.net/remote-releases/b1e87884330fc271d5eb589e368c35f14e76dec0/cli-win32-x64.tar.gz [14:09:38.150] Downloading VS Code server locally... [14:09:38.439] Terminating local server [14:09:38.440] Exec server for ssh-remote+fred-server failed: Error: Failed to download VS Code Server (Server returned 404) [14:09:38.440] Error opening exec server for ssh-remote+fred-server: Error: Failed to download VS Code Server (Server returned 404) [14:09:38.445] Local server exit: 15

In fact, "https://cursor.blob.core.windows.net/remote-releases/b1e87884330fc271d5eb589e368c35f14e76dec0/cli-win32-x64.tar.gz" is a non-existent file:

image