Connection failed for all new chats

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I don’t understand why this has happened in every chat I’ve created.

Request ID: e27be065-bbc5-4bfe-8877-9469833301a9
ConnectError: [internal] 1254133031424:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40

at isu.$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:6513)

Steps to Reproduce

IDK

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.48 (Universal)
VSCode Version: 1.105.1
Commit: ce371ffbf5e240ca47f4b5f3f20efed084991120
Date: 2025-12-04T19:26:27.263Z
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

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like
Connection Error - wow not fixed
ASK and AGENT modes are not working with "Connection failed. If the problem persists, please check your internet connection or VPN" erron
2

Hey, thanks for the report.

This looks like the known TLS issue over HTTP/2. Please try:

  • Settings → type “HTTP/2” → enable “Disable HTTP/2” → restart Cursor and test in a new chat
  • Settings → Network → Run Diagnostics → send a screenshot
  • Are you using a VPN/proxy/corporate network/SSL inspection (e.g., Zscaler)? Test without it or on another network
  • Launch without extensions: in a terminal run cursor --disable-extensions and test a new chat
  • Send 2–3 new Request IDs from failed attempts, plus errors from Help → Toggle Developer Tools → Console

Similar cases and a confirmed fix with Disable HTTP/2:

Let me know if disabling HTTP/2 helps. If it does, keep it enabled while we investigate.

5 Likes
3

Oh wow! This actually helped! I tried this before in Cursor’s settings and it didn’t help, but changing it in the VSCode settings instead seems to have done the trick… at least for now! Thank you! –Matt

4

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After updating from 2.0 to 2.1 in MacOS all LLM calls failed with
Request ID: fd4a9f10-74b2-4eae-a783-5b5af4c4ea21
ConnectError: [internal] 1185413685760: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)

I was lucky to find 2.0 installer in my downloads (btw - is it not worth keeping users the option to download previous releases? ) - and with 2.0 everything worked as should!

Steps to Reproduce

Update to 2.1 in mac - make any agent call )

Expected Behavior

All LLM calls fails

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.69 (Universal)
VSCode Version: 1.99.3
Commit: 63fcac100bd5d5749f2a98aa47d65f6eca61db30
Date: 2025-11-07T18:21:29.650Z
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?

For AI issues: add Request ID with privacy disabled

Request ID: fd4a9f10-74b2-4eae-a783-5b5af4c4ea21
ConnectError: [internal] 1185413685760: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)

Additional Information

the info is from version that works. 2.1 is failing

Does this stop you from using Cursor

Yes - Cursor is unusable