Persistent Connection Error despite successful Diagnostics and network changes

[gurdlek_yun]

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Hello,

I am continuously receiving a “Connection Error” when attempting to use any AI function in Cursor.

My troubleshooting steps so far:

Confirmed the issue persists across different computers and different internet connections (networks).

The error persists even after changing the HTTP Compatibility Mode from HTTP/2 to HTTP/1.1.

I have tried logging out and logging back in (re-authentication).

Crucially, the Network Diagnostics test passes successfully for all checks (API, Ping, Chat, Agent, etc.). This indicates the basic network route is fine, but the actual AI request is failing at a higher level (e.g., specific session failure or account-level lock).

Please check the following Request IDs from the error messages:

b6bb6216-697c-4494-84c7-90dc32967590 (from a previous attempt)

9817b860-6d49-4681-bc9e-237724a2cdb3 (from one of the recent errors)

eab2efd5-… (from another recent error - the beginning part is fine)

I have attached screenshots of the successful Network Diagnostics for reference. Please advise.

Thank you

Steps to Reproduce

Open the Cursor editor and navigate to the Chat panel.

Select an AI model (e.g., GPT-4o or Claude-3.5 Sonnet).

Enter a simple prompt (e.g., “Write a simple ‘Hello World’ function in Python”).

Press Enter to submit the request.

Expected Result: The AI model should stream the response and generate the code.

Actual Result: Immediately receive the “Connection Error: Connection failed…” message.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Cursor 2.1.0 (VSCode 1.105.1)

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, thanks for the clarification. If the issue persists across different computers and networks with HTTP/1.1 disabled, it points to an account or session problem, not a network one.

Thanks for the Request IDs - I’ll pass them to the engineers. The fact that it reproduces everywhere is critical for diagnosis.

This looks like one of these:

• Account session token is invalid or blocked on the backend
• Account got blacklisted by the anti-fraud system
• API authorization issue (even if login works)

Try this:

1. Log out completely and log in via Google or GitHub OAuth (not email/password)
2. If that helps, it means your account token is the issue
3. If not, your account might be on the anti-fraud blacklist

If switching to OAuth works, reply here. It’ll give us a clear direction for investigation. If not, it’s more serious and needs direct engineer intervention for accounts.

I’ll pass this info with high priority.