After update agents don't work

[rkx]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After update any of agent don’t work, always “An unexpected error occurred on our servers. Please try again, or contact support if the issue persists.”

Request ID: 35480b56-4b17-4c93-9297-0a16a625597b
RTe: [internal] 1185412571648:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40

at xhf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9094:38337)
at khf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9094:37240)
at qhf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:4395)
at Nfa.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:8170)
at async Myt.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34199:57047)
at async vpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34248:7695)
at async vpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34248:8436)
at async LTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9168:76988)
at async Hi (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:33000:3808)

Steps to Reproduce

Try any request on any model in chat

Operating System

MacOS

Version Information

After update on 2.4.4 this begin
Try to fix with 2.4.9 but don’t help

For AI issues: which model did you use?

Opus 4.5, GPT 5.2

For AI issues: add Request ID with privacy disabled

Request ID: 35480b56-4b17-4c93-9297-0a16a625597b
RTe: [internal] 1185412571648:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40

at xhf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9094:38337)
at khf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9094:37240)
at qhf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:4395)
at Nfa.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:8170)
at async Myt.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34199:57047)
at async vpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34248:7695)
at async vpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34248:8436)
at async LTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9168:76988)
at async Hi (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:33000:3808)

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the report. This is a known issue: an SSL handshake failure when using HTTP/2. Details and discussion are here: [Known Issue] HTTP/2 Connection Failures with SSLV3_ALERT_HANDSHAKE_FAILURE

Try this workaround:

• Open Cursor Settings CMD+,
• Search for “HTTP/2”
• Switch HTTP Compatibility Mode to HTTP/1.1
• Restart Cursor

This issue seems to affect users from certain regions more often, especially Ukraine, and it looks related to Cloudflare CDN routing. The team is aware, but there’s no fix yet.

If it doesn’t help, please reply in the main thread. There are already 60+ users sharing details and other workarounds, like changing DNS.