Server 403 on Update using Cursor Nightly

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When trying to update my Cursor Nightly I get a “Server returned 403” error showing up as a notification in the left bottom corner of Cursor IDE.

Steps to Reproduce

Help → Check for update → Notification shows “Server returned 403”.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.8.0-pre.10.patch.0 (user setup)
VSCode Version: 1.99.3
Commit: 9526efe361edb9751e474859e725d1b821e3b159
Date: 2025-09-30T08:11:49.524Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, the server might have been temporarily unavailable, or there may have been issues with your internet connection. Could you confirm if the issue is resolved now?

3

Still showing the same thing .. My internet is working everywhere else …

EDIT: I tried restarting Cursor Nightly and still same thing happens …

image

4

Do you have the option to enable a VPN? Since I’m not getting this error, you might have some internet issues.

5

No VPN enabled … I changed nothing and I was using Cursor Nightly just fine before … nothing changed on my side and one day I open the app and tried to Check for Updates and got that error message … I tried reset my modem , restart the app , restart my PC … nothing works lol .. :person_shrugging:

EDIT: Tried turning AV off too … forgot to mention

1 Like
6

Thanks for the info, we’re looking into it.

1 Like
7

Thanks to you !! Let me know if you need any more informations :wink:

8

@deanrie
Its now fixed. I was able to update my Cursor Nightly now :slight_smile: Thank you !!!

1 Like
9

@deanrie
Dang it the issue is back again … this is my Cursor Nightly version below … it was fixed but its now back and doing exactly the same 403 server error …

Version: 1.9.0-pre.2.patch.0 (user setup)
VSCode Version: 1.99.3
Commit: 2c68a0136322d6944de6f75556127ae683790869
Date: 2025-10-21T08:17:00.544Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26200

10

Thanks for the update! Since this was previously resolved and has now regressed, I’ve flagged this for the team to investigate further.

1 Like