Are you seriously suggesting switching to HTTP/1.1 or deleting the entire history on which you also earned a commission as an intermediary between AI models instead of providing an actual solution?
The forum is flooded with this issue and Cursor team are doing nothing about it.
Hey, @Colin, are there any updates on that? I had to use the HTTP/1.1 solution, and sometimes it’s so slow that it prevents me from productive coding. I really like Cursor, but this issue is forcing me to investigate other IDEs, unfortunately.
We saw reports of this issue all but disappear, so I think we assumed it was a transient issue that went away. If you’re still dealing with it, I’d like to get to the bottom of it once and for all!
I’d like to start by getting really targeted in what you wipe from ~/Library/Application Support/Cursor
Next time this happens, could you try just removing these files, instead of the whole folder?
# Backup network state files for analysis, then remove them
BACKUP_DIR=~/Desktop/cursor-network-state-$(date +%Y%m%d-%H%M%S)
mkdir -p "$BACKUP_DIR"
cp ~/Library/Application\ Support/Cursor/Network\ Persistent\ State "$BACKUP_DIR/" 2>/dev/null
cp ~/Library/Application\ Support/Cursor/TransportSecurity "$BACKUP_DIR/" 2>/dev/null
rm -f ~/Library/Application\ Support/Cursor/Network\ Persistent\ State
rm -f ~/Library/Application\ Support/Cursor/TransportSecurity
echo "Backed up to: $BACKUP_DIR - please restart Cursor"
If this restores functionality (send a new agent message to regenerate those files), then I would want to see the backed up files, and the new files that get generated to compare them and understand why one stopped working, and the other started. If you don’t feel comfortable sharing them here, I can open up a private message with you.
And if it doesn’t restore functionality, let me know and we’ll dig deeper into what else might be cached. There are a few other files (Cookies, Local State, Cache/, Service Worker/) that could play a role. But, if it’s network/SSL related, I think it will be TransportSecurity or Network Persistent State)
Hi @Colin, I followed your instructions, and it worked initially. However, after about a day (presumably after a session reset), the connection error returned.
I have the backed-up files ready, but I am not comfortable sharing them publicly due to potential sensitive information. Could you please send me a private message? I will reply with the files attached so you can analyze the difference between the broken and working states.
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)
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
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)
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
Some chat instances fail with SSL/TLS handshake errors while others work fine in the same workspace.
Error Details:
Request ID: 555b5388-fa66-4037-be09-b9baea90bed2
ConnectError: [internal] 1288492638272: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/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6331:406060)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:565:75277
at async Object.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6399:42465)
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 o7r.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2815:6513)
Symptoms:
Fresh chat windows fail immediately with “Connection Error” on first message
Error: “Connection failed. If the problem persists, please check your internet connection or VPN”
Some chat instances work fine while others consistently fail
Issue persists after clearing cache, reindexing workspace, closing/reopening chats, and restarting Cursor
Environment:
Subscription: Pro
Multiple chat windows in same workspace
Some chats work, others fail with same error
Additional Issue:
Rules are only processed on the first message of a chat. If a chat fails on first message, rules cannot be applied. If a working chat is continued, rules may not be applied to subsequent messages.
Steps to Reproduce
Open Cursor with a workspace
Open a new chat window
Type first message in the new chat
Connection error appears immediately
Some chat windows work fine, others consistently fail with SSL handshake error
Issue persists after clearing cache, reindexing, closing/reopening chats, and restarting Cursor
Expected Behavior
All chat windows in the same workspace should connect successfully. SSL handshake should complete without errors.
Restart Cursor and check in a new chat - done it seems working workaround but it is working on http/2 mostly
Network diagnostics
Settings → Network → Run Diagnostics → send a screenshot/results i don’t have any vpn or proxy
I have optic line and Ubiquiti based local network 10.11.1.0/24
