Bug Report: 404 Error Downloading Server Component on WSL with Cursor.ai

Bug Reports
1

Description:

After updating Cursor.ai, I’m unable to remote into WSL. The process fails during the server component download. The error log indicates that the file vscode-reh-linux-legacy-x64.tar.gz cannot be found (HTTP 404 error) when attempting to download it from the URL:

https://cursor.blob.core.windows.net/remote-releases/531f7615b0fcf0592a15769d11b37e13eeb85cd0/vscode-reh-linux-legacy-x64.tar.gz

This prevents the proper installation and update of the VS Code Server component required for remote development.

How to Reproduce:

  1. Update Cursor.ai to the latest version.

  2. Open VS Code and try to connect to a WSL environment using the Remote WSL extension.

  3. The process attempts to download the VS Code Server for Linux (legacy-x64) and fails with a 404 error.

  4. See the relevant log snippet below:

    [2025-02-21 16:10:04.378] Probing result: legacy-x86_64
[2025-02-21 16:10:04.378] No server install found in WSL, needs linux-legacy-x64
...
[2025-02-21 16:10:05.404] 404 The specified blob does not exist.

Operating System & Cursor Version:

  • Operating System: Windows 10 host with Ubuntu running under WSL2 (Kernel: 5.15.167.4-microsoft-standard-WSL2)
  • Cursor.ai Version: 0.45.15

Impact:

This issue stops me from successfully using Cursor.ai for remote development in WSL, which significantly disrupts my workflow.

Additional Information:

  • I have checked the forum and did not find an existing report for this issue.
  • I have attached screenshots of the error logs and the VS Code interface where the error appears.

Please let me know if any further details or logs are required to help diagnose this issue.

Updating VS Code Server to version 531f7615b0fcf0592a15769d11b37e13eeb85cd0
Removing previous installation...
Installing VS Code Server for Linux legacy-x64 (531f7615b0fcf0592a15769d11b37e13eeb85cd0)
Downloading: 100%
Failed
--2025-02-21 09:03:54--  https://cursor.blob.core.windows.net/remote-releases/531f7615b0fcf0592a15769d11b37e13eeb85cd0/vscode-reh-linux-legacy-x64.tar.gz
Resolving cursor.blob.core.windows.net (cursor.blob.core.windows.net)... 20.209.35.129
Connecting to cursor.blob.core.windows.net (cursor.blob.core.windows.net)|20.209.35.129|:443... connected.
HTTP request sent, awaiting response... 404 The specified blob does not exist.
2025-02-21 09:03:54 ERROR 404: The specified blob does not exist..

ERROR: Failed to download https://cursor.blob.core.windows.net/remote-releases/531f7615b0fcf0592a15769d11b37e13eeb85cd0/vscode-reh-linux-legacy-x64.tar.gz to /home/andrew/.cursor-server/bin/531f7615b0fcf0592a15769d11b37e13eeb85cd0-1740157434.tar.gz

Thank you,
Andrew

2

I’m having the same issue with remote host connection on this latest update

3

I had to rollback to version 0.44.11, then delete the ~/.cursor-server/ folder and it all works, I will wait till the next version comes out to update.

4

Workaround for Cursor.ai WSL Remote Server 404 Error & Stuck State After Reboots

If you are experiencing the 404 error when attempting to download the VS Code Server component after updating Cursor.ai and find that rolling back to an older version causes your setup to get stuck in a broken state after reboots, follow these steps to resolve the issue.

Steps to Apply the Workaround:

  1. Open a WSL Terminal and navigate to the Cursor server directory:

    cd ~/.cursor-server/bin/

  2. Create a Backup of the Existing Server Component:

    cp -r f5f18731406b73244e0558ee7716d77c8096d150/ f5f18731406b73244e0558ee7716d77c8096d150-backup

  3. Update Cursor.ai to the Latest Version
    You can update Cursor using:

    cursor update

  4. Restore the Previous Server Component for Compatibility:
    Since the new update may introduce a version mismatch, copy the backed-up component to match the expected version:

    cp -r f5f18731406b73244e0558ee7716d77c8096d150-backup/ 906121b8c0bdf041c14a15dac228e66ab5505260

  5. Ensure All References Are Updated:
    Find and replace references to the old server component (f5f18731406b73244e0558ee7716d77c8096d150) with the new version (906121b8c0bdf041c14a15dac228e66ab5505260):

    find ~/.cursor-server/bin/906121b8c0bdf041c14a15dac228e66ab5505260 -type f -exec sed -i 's/f5f18731406b73244e0558ee7716d77c8096d150/906121b8c0bdf041c14a15dac228e66ab5505260/g' {} +

Expected Outcome:

After performing these steps, you should be able to successfully use Cursor.ai for remote development in WSL without getting stuck in a broken state after reboots.

This workaround helps to deal with Cursor’s updates and missing dependencies until an official fix is released.

5

I had to do this again for this latest release.

The steps in the above post still work, but you need to replace with 906121b8c0bdf041c14a15dac228e66ab5505260 ae378be9dc2f5f1a6a1a220c6e25f9f03c8d4e10

Not sure how this got broken for a second time.

:face_exhaling:

And no responses

:face_exhaling:

Not typical for a paid service.