errord
(error.d)
1
Where does the bug appear (feature/product)?
Somewhere else…
Describe the Bug
The web version of Cursor cannot perform Google OAuth login anymore, showing a 500 error or failing to map the user.
Steps to Reproduce
cursor web login
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.0.60 (user setup)
VSCode Version: 1.99.3
Commit: c6d93c13f57509f77eb65783b28e75a857b74c00
Date: 2025-11-05T00:50:54.645Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19045
Does this stop you from using Cursor
No - Cursor works, but with this issue
deanrie
(Dean Rie)
2
Hey, thanks for the report. To investigate the Google OAuth login issue, please share:
- A screenshot of the exact error message showing the 500 error
- Browser console errors: open Developer Tools (F12) → Console during the login attempt and share any error messages
- Your browser and version
- When this started happening and whether Google OAuth worked before
- Do other sign-in methods (GitHub, email) work?
Meanwhile, try:
- A different browser
- A different network (e.g., mobile hotspot)
- Clear cookies/cache for cursor.com
- An alternative sign-in method if available
I’ll pass this to the team as soon as we have the diagnostics.
system
(system)
Closed
3
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.