Desktop App Login Failing: Persistent 404 on /auth/poll Endpoint

[A_A2 (A A)]

Describe the Bug

The “Sign In”/“Log in” button in the Cursor desktop application does nothing when clicked. No browser window opens for authentication. Checking the console reveals a persistent 404 (Not Found) error when the application tries to call the /auth/poll endpoint during the login process.

Steps to Reproduce

Install a fresh version of the Cursor desktop application (tested on 1.6.45 and 1.4.2).

Upon startup, click the “Sign In”/“Log in” button.

Observe: Nothing happens. No browser window appears.

Click “Skip” to proceed to the app interface.

Go to Help > Toggle Developer Tools to open the console.

Navigate to Settings and click “Sign In” again.

Observe the error: The console shows a 404 error for the https://api2.cursor.sh/auth/poll endpoint.

Expected Behavior

Clicking the “Sign In” button should open a browser window to authenticate with a provider (e.g., GitHub). After successful authentication in the browser, the desktop app should log in automatically.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.45 (system setup)
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z
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

Additional Information

Web Login Works: I can log in without any problems on the Cursor website, which confirms my account is valid.

Server Connectivity: The main API server is accessible. Visiting https://api2.cursor.sh/ directly in a browser shows a “Welcome to Cursor” message, and pinging the server works perfectly. This indicates the problem is specific to the login sequence in the desktop app.

No Network Restrictions: The issue occurs on a direct connection without proxies or VPNs.

Troubleshooting Performed: I have tried multiple reinstalls, clearing the %appdata%\cursor folder, and resetting network settings. The problem persists.

Does this stop you from using Cursor

Yes - Cursor is unusable

[sanjeed5 (Sanjeed)]

Thanks for the report, sorry about the issue you are facing.

Can you please share network diagnostics? Go to Cursor Settings > Network and click Run Diagnostics.

[A_A2 (A A)]

Yes, sure

[sanjeed5 (Sanjeed)]

Thanks for the detailed network diagnostics.

Please try these:

• Retry on a different network if possible.
• Run as Administrator: Right-click Cursor and “Run as administrator”
• Check security software: Please check if Windows Defender or other antivirus might be blocking the requests