Connection error in Cursor when on Ukrainian IP

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Since last week the chat in the Cursor IDE always gives me Connection error:

Request ID: b98b2bda-1ce1-4868-91ad-d2c66300369d
ConnectError: [internal] 4277788264640:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40

at UZc.$streamAiConnect (vscode-file://vscode-app/tmp/.mount_cursor6LiNq3/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6331:406060)
at async vscode-file://vscode-app/tmp/.mount_cursor6LiNq3/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:565:75277
at async Object.run (vscode-file://vscode-app/tmp/.mount_cursor6LiNq3/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6399:42465)
at async o (vscode-file://vscode-app/tmp/.mount_cursor6LiNq3/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:2815:1269)
at async Promise.allSettled (index 0)
at async o7r.run (vscode-file://vscode-app/tmp/.mount_cursor6LiNq3/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:2815:6513)

I’m in Ukraine. And I get the same error if I try to connect using VPN with Ukrainian IP (so it’s not an issue related to my internet provider).
And if I use VPN with, say, German or American IP, everything works fine.

Steps to Reproduce

Connect using Ukrainian IP.

Expected Behavior

I should be able to use Cursor without VPN connections (and it worked fine until last week).

Screenshots / Screen Recordings

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.39
VSCode Version: 1.105.1
Commit: 60d42bed27e5775c43ec0428d8c653c49e58e260
Date: 2025-11-27T02:30:49.286Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.8.0-87-generic

Does this stop you from using Cursor

No - Cursor works, but with this issue

6 Likes

Hey, thanks for the report.

Quick workaround to try:

  • App Settings Ctrl+, → search “HTTP/2” → enable “Disable HTTP/2” → restart Cursor → test chat again.

If it still fails, please share:

  • Settings → Network → Run Diagnostics (screenshot)
  • Your ISP and whether you’re using any firewall/proxy (e.g., Zscaler)

Reference: another user hit the same SSL alert and disabling HTTP/2 fixed it: SSLV3_ALERT_HANDSHAKE_FAILURE when creating new chat

Let me know if the HTTP/2 toggle helps.

5 Likes

Disabling HTTP/2 helped.
Thanks a lot!

3 Likes

Hi, I’m sorry but is there a way to enable http2 in cursor? with http1 it feels like much worse and slower experience.
It stopped working for me for about a week already and for my friends from Ukraine as well?

1 Like

I second this ^

composer-1 was lightning fast for me all the time, and now with HTTP1 (which is the only option) it’s working significantly slower.

1 Like

Same issue and reverting to HTTP/1.1 doesn’t work

The issue is now gone (v2.2.20)

Thanks for resolving it Cursor team!

Sorry for writing back and forth - the issue now happens again. It works with http1 and stops working with http2.

Reinstalling Cursor also didn’t help.

1 Like

Hello, I’m facing the same issue when I try to run a query. I have Cursor Pro subscription

Try change dns server

Same for me, trick with http2 doesnt work

Same issue. When trying to use HTTP2, I’m getting error:
а давай виводити вати без дробних, тоді більше взіле в екран

1116693999424:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40

[internal]

When switching to HTTP 1.1 it throwing error:
We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.

Fixed the issue.

  1. Removed desktop app.
  2. Removed Cursor folder in Application Support (`rm -rf ~/Library/Application\ Support/Cursor/`)
  3. Installed the app.

The issue has gone so far.

The issue is still relevant. Today, Cursor self-upgraded from v2.1.42 to v2.3.35. I did repeat the steps mentioned here; however, it still doesn’t work fully.
v2.1.42 was supposedly the latest version that didn’t have troubles with HTTP2 connection.

At the moment (v2.3.35), the Auto mode works for me, while the others (tested Composer-1 and Gemini 3 Flash) don’t. It’s a bummer - the tool is completely unusable.

request IDs for debug:

  • 66ffcc91-fb8c-4df3-953c-23f4cdaa8b55 (failed)
  • 7610f538-e383-48a7-9ddb-f8397591db99 (failed)
  • 3bf9cbc4-4d82-4b19-ad7f-e5488f23aeb2 (successful)

@deanrie tagging you for visibility

3 Likes