HTTP2 dont work at all HTTP1.1 lagging

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In 2.1.47-48 HTTP2 stopped working and resorted to 1.1 which is slow but stable. 2.1.49 - HTTP2 worked again and 2.1.50 - HTTP2 does not work again and HTTP1.1 chokes often. I tried different connections and it did not help.

Steps to Reproduce

Hard to say

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50 (Universal)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

For AI issues: which model did you use?

all models behaves the same for this isue

For AI issues: add Request ID with privacy disabled

Request ID: 954552f8-622a-4915-9450-46c355b58386
ConnectError: [internal] 1185413486912:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40

at nsu.$streamAiConnect (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6409:406134)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:565:80832
at async Object.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6477:42602)
at async o (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2815:1269)
at async Promise.allSettled (index 0)
at async fHr.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2815:6519)

Does this stop you from using Cursor

Yes - Cursor is unusable

3 Likes

This is the same issue I’m having. I assume something happened specifically for Ukraine because a couple of my friends are facing the same issue. Please help, http1 is really slow and has a bad experience compared to http2

2 Likes

I am also working from Ukraine and local internet issue was my first suspect but .49 update fixed the issue. I suppose Cursor can help from their end.

Hey, thanks for the report. Looks like the same issue as here: SSLV3_ALERT_HANDSHAKE_FAILURE when creating new chat. Most users fix it temporarily by disabling HTTP/2:

  • Settings → search for HTTP/2 → enable Disable HTTP/2 or in Network set HTTP Compatibility Mode to HTTP/1.1, then restart Cursor

We’re investigating it as a regression in 2.1.50. I’ll update you once there’s a fix.

3 Likes

(duplicate my message for better visibility):

My observation

I’m also from Ukraine and have the same issue.

Working with HTTP/1.1 seems to be slower and produces worse quality of code.

2 Likes

Thanks for getting back! HTTP1.1 does not work, it breaks in the middle so Cursor literally out of order. I just wanted to make it clear.

1 Like

Same issue here, i build my own VMs and i thought this has something to do with firewall or it’s a dns problem, AI chat features is not working when connected via ssh, and it was working a few hours ago, is there someone else in north Africa have same issue?

No mate, it is not about geography. I also enjoyed working SSH all day until it stopped working again at night. Cursor can fix it. Based in Ukraine.

Have you found any solution to this issue? Yesterday everything was working like clockwork for me, but today, after updating Cursor to the current version (2.2.20), I started having HTTP/2 problems. Switching to HTTP/1.1 isn’t working either.

No, it is going back and forth. 1.1 backup works nearly always though.

Check my last post. I found a solution.

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.