If the cause is on the network level its likely not going to help if you uninstall.
However you can try it. Make sure to copy the config folders as a backup so you dont have to lose settings.
Please try with the folders mentioned in here.
If the cause is on the network level its likely not going to help if you uninstall.
However you can try it. Make sure to copy the config folders as a backup so you dont have to lose settings.
Please try with the folders mentioned in here.
Cursor IDE
Cursor don’t work few days. I reinstalled Cursor but that did not help.
Cursor updated succesfully to the last version - 2.3.35
Windows 11 Home, 24H2
Request ID: bfe11e41-9b60-4fde-8baa-858b7cbc1e66
Any request from any model don’t work.
Windows 10/11
Version: 2.3.35 (user setup)
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120
Date: 2026-01-13T07:39:18.564Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100
Yes - Cursor is unusable
Hey @vitaliy-dushepa!
No sign of that Request ID on our side, which typically means the request didn’t make it to our servers.
Can you try running Cursor’s network diagnostics and let us know the results?
1). I have made diagnostics in Cursor AI:
- DNS, HTTP/2, SSL, Marketplace work,
- for API, Ping, Chat, Agent I have an error message:
“ConnectError: [internal] 311168:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:..\..\third_party\boringssl\src\ssl\tls_record.cc:486:SSL alert number 40”
2). I asked advise from LLM, it proposed to change “http/2“ on “http/1.1“ in Cursor settings.
It helped, now it works.
Do I need (in future) return to “http/2“ or just use “http/1.1“?
Broken HTTP/2.0 is a widespread issue that exists from like 2.1.50 Cursor version.
Cursor team doesn’t mind it, so do I by using Codex instead of Cursor agent lol
Cursor IDE
Chat with any models doesnt work
314368:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:....\third_party\boringssl\src\ssl\tls_record.cc:486:SSL alert number 40
[internal]
Connection failed. If the problem persists, please check your internet connection or VPN
just start ide, and chants not working
neew usual working behavior
Windows 10/11
Version: 2.3.35 (system setup)
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120
Date: 2026-01-13T07:39:18.564Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19044
all models
Request ID: 3daeec33-0b3d-4ff0-8c71-dcb5db783e1e
Request ID: 2f67a257-aa4c-4d44-9874-b2a0e560563f
how fix this?
Yes - Cursor is unusable
Hey, thanks for the report. This is a known issue with HTTP/2 and the SSL handshake.
Try this:
Ctrl+, → search for “HTTP/2” → enable “Disable HTTP/2” → restart CursorIf it didn’t help, or if you want to dig deeper:
Related thread: SSLV3_ALERT_HANDSHAKE_FAILURE
Let me know if disabling HTTP/2 helped.
The 1, 2 helped, it works, thank you
Cursor IDE
No answer from Agent. That is second day the same.
An unexpected error occurred on our servers. Please try again, or contact support if the issue persists.Request ID: 87fffb6f-41a2-4900-b2aa-3232cbad47c4
[internal] 28673202505920:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40
LTe: [internal] 28673202505920:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40
at kmf (vscode-file://vscode-app/tmp/.mount_CursorRmlOJ6/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9095:38337)
at Cmf (vscode-file://vscode-app/tmp/.mount_CursorRmlOJ6/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9095:37240)
at $mf (vscode-file://vscode-app/tmp/.mount_CursorRmlOJ6/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4395)
at ova.run (vscode-file://vscode-app/tmp/.mount_CursorRmlOJ6/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)
at async qyt.runAgentLoop (vscode-file://vscode-app/tmp/.mount_CursorRmlOJ6/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34190:57047)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/tmp/.mount_CursorRmlOJ6/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34239:7695)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/tmp/.mount_CursorRmlOJ6/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34239:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/tmp/.mount_CursorRmlOJ6/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
Write any request to Agent.
Recive answer
Linux
Version: 2.4.21
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Linux x64 6.8.0-90-generic
All
I from Ukraine and now is trouble with energy. So I use mobile internet. But there is no problem before 22.01.2026.
Yes - Cursor is unusable
Cursor IDE
An unexpected error occurred on our servers. Please try again, or contact support if the issue persists.
Request ID: 897aff0f-669d-495d-85b1-6d9f64c7dded
[internal] 279040:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:....\third_party\boringssl\src\ssl\tls_record.cc:486:SSL alert number 40
LTe: [internal] 279040:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:....\third_party\boringssl\src\ssl\tls_record.cc:486:SSL alert number 40
at kmf (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9095:38337)
at Cmf (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9095:37240)
at $mf (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4395)
at ova.run (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)
at async qyt.runAgentLoop (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34190:57047)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34239:7695)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34239:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
Windows 10/11
Version: 2.4.21 (user setup)
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26100
Request ID: 897aff0f-669d-495d-85b1-6d9f64c7dded
[internal] 279040:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:....\third_party\boringssl\src\ssl\tls_record.cc:486:SSL alert number 40
LTe: [internal] 279040:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:....\third_party\boringssl\src\ssl\tls_record.cc:486:SSL alert number 40
at kmf (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9095:38337)
at Cmf (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9095:37240)
at $mf (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4395)
at ova.run (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)
at async qyt.runAgentLoop (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34190:57047)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34239:7695)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34239:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
Yes - Cursor is unusable
I have the same problem.
The same issue for me started to appear for me again. Before in December I managed to resolve it by reinstalling the cursor with clearing all the local data.
If I disable HTTP/2 it helps, but would appreciate the real fix so Ukrainian users can use http/2. Thanks.
Request ID: 801b9cc1-f411-481c-b2e2-8f9c9c1d43f7
{“error”:57,“details”:{“title”:“Provider Error”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“isRetryable”:true,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
[resource_exhausted] Error
LTe: [resource_exhausted] Error
at kmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:38337)
at Cmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:37240)
at $mf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4395)
at ova.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)
at async qyt.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34190:57047)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:7695)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
i dont know.
MacOS
Version: 2.4.21 (Universal)
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z (1 天前)
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 24.5.0
Yes - Cursor is unusable
I have the same issue
Request ID: f6ffeced-1b31-49bd-a4ff-607c10d3e46c
[internal] 1322851775168:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40
LTe: [internal] 1322851775168:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40
at kmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:38337)
at Cmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:37240)
at $mf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4395)
at ova.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)
at async qyt.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34190:57047)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:7695)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
at async Oi (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32991:3808)
MacOS
Version: 2.4.21 (Universal)
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0
This is different issue
Request ID: 298715cd-145e-49d7-9636-dad6aa3c963f
[internal] 1322851775168:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40
LTe: [internal] 1322851775168:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40
at kmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:38337)
at Cmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:37240)
at $mf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4395)
at ova.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)
at async qyt.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34190:57047)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:7695)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
at async Oi (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32991:3808)
A post was split to a new topic: Que faire face à cette erreur récurrente?
HTTP/2 not working more than month I guess…
using HTTP/1.1
Devs, please do something
Request ID: d994c526-2f13-4a2a-a826-0695d9e7e3be
[internal] 277760:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:....\third_party\boringssl\src\ssl\tls_record.cc:486:SSL alert number 40
LTe: [internal] 277760:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:....\third_party\boringssl\src\ssl\tls_record.cc:486:SSL alert number 40
at kmf (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9095:38337)
at Cmf (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9095:37240)
at $mf (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4395)
at ova.run (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)
at async qyt.runAgentLoop (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34190:57047)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34239:7695)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34239:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
Hello Cursor Team,
I am experiencing a persistent issue with the AI Chat (Ctrl+L) and Cursor Tab features immediately after the latest update today. Before the update, everything was working perfectly.
The Issue:
Every request to the AI results in a “Connection Error”.
Error: SSLV3_ALERT_HANDSHAKE_FAILURE (SSL alert number 40).
Request ID: c433530c-1583-4318-aa13-f4809475e477 (and others).
My Environment:
Troubleshooting Steps Performed (None worked):
NODE_TLS_REJECT_UNAUTHORIZED=0.Critical Diagnostic Findings:
I ran a Python diagnostic script (net_check.py) using ssl and socket libraries on the SAME machine.
google.com via TLS 1.3 successfully.Logs / Stack Trace:
[internal] 263040:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:....\third_party\boringssl\src\ssl\tls_record.cc:486:SSL alert number 40
at kmf (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9095:38337)
at Cmf (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9095:37240)
Additional Info:
I also noticed that sometimes the integrated terminal crashes with PowerShell Exit Code: -1073741819 (0xC0000005 Access Violation), which might be related to how the new version handles network hooks on my specific hardware configuration.
Please investigate. The editor is currently unusable for AI tasks.
Windows 10/11
Version: 2.4.21 (system setup)
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200
Yes - Cursor is unusable
Hello I am from Belgium and experience the same issue.
I just subscribed yesterday and use the paid Pro-subscription. My version of Cursor is 2.4.21.
After the download, I have been working with Cursor successfully for a couple of hours. Then I stopped for lunch and afterwards, I got the error “Connection failed”.
I have disabled HTTP/2 for all requests and indicated HTTP/1.1. However the message “Connection failed” in the chat remains.
I am working with a Windows 11 laptop.
When I run Diagnostic, the result is:
DNS is fine
SSL - read ECONNRESET
API - [aborted] read ECONNRESET
Ping - [aborted] read ECONNRESET
Chat - [aborted] read ECONNRESET
Agent - [aborted] read ECONNRESET
Marketplace - Failed to fetch
This is very disappointing because as developer, you have to be able to rely on your platform.
Are you seeing SSLV3_ALERT_HANDSHAKE_FAILURE? If not, it’s likely a different error.