Unexpected Error Occured

Support Help
1

I’ve had this error since early this morning and it is about 5:45 PM now where I live. Can someone tell me what is going on?

5

Hey, thanks for the report. “Unexpected error occurred” is a generic banner we show for any failed request, most often when the request doesn’t reach our servers at all. In your account it looks like the requests aren’t getting through, which is a typical sign of a client-side network issue like a proxy, firewall, VPN, or SSL/TLS inspection on a corporate network.

A few steps to troubleshoot:

  1. Open a new chat and try again.
  2. Cursor Settings > Network > Run Diagnostics, then send me the result.
  3. If you’re on a corporate network or using a VPN or Zscaler, try temporarily turning it off or switching to another network like a mobile hotspot to test.

To dig deeper, please share:

  • the exact error text and the Request ID (chat menu in the top right > Copy Request ID)
  • your Cursor version
  • your OS

A similar case the same day was fixed by adjusting corporate SSL inspection settings, so you might be seeing the same thing. Let me know what the diagnostics show.

6

Request ID: e496c219-7919-4e4c-917e-d8abacfbb069
An unexpected error occurred.
[internal] unable to verify the first certificate; if the root CA is installed locally, try running Node.js with --use-system-ca
RetriableError: [internal] unable to verify the first certificate; if the root CA is installed locally, try running Node.js with --use-system-ca
at dVv (vscode-file://vscode-app/c:/Users/dansa/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9155:6675)
at EAr (vscode-file://vscode-app/c:/Users/dansa/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9155:5410)
at Lgm (vscode-file://vscode-app/c:/Users/dansa/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9156:11974)
at Object.classify (vscode-file://vscode-app/c:/Users/dansa/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9156:16506)
at mVv (vscode-file://vscode-app/c:/Users/dansa/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9156:5856)
at async t4a.runWithSharedTurnRunner (vscode-file://vscode-app/c:/Users/dansa/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9156:15858)
at async Nq.runAgentLoop (vscode-file://vscode-app/c:/Users/dansa/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:20120:3005)
at async uhl.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/dansa/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:20180:14344)
at async uhl.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/dansa/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:20180:23914)
at async GBe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/dansa/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9326:2476)

image.png
image.png262×298 11.5 KB

Windows 11

7

Thanks, that makes sense now. The unable to verify the first certificate error usually means your HTTPS traffic is being intercepted by a corporate proxy or antivirus or security tool like Zscaler, Netskope, Palo Alto, etc, which re signs the connection using a certificate that Cursor doesn’t trust yet. That’s why the request fails before it’s sent and never reaches our servers.

What to do on Windows:

  1. Open Command Palette Ctrl+Shift+P > Preferences: Open User Settings (JSON) and add:
"http.systemCertificates": true,
"http.experimental.systemCertificatesV2": true,
"cursor.general.disableHttp2": true
  1. Fully close Cursor not just the window, quit the whole process, then open it again.
  2. Make sure your corporate root CA is installed and trusted in the Windows Trusted Root Certification Authorities store. If it’s not there, ask your IT team for the certificate.

If it still doesn’t work:

  • Set the NODE_EXTRA_CA_CERTS environment variable to the path of your corporate certificate, for example NODE_EXTRA_CA_CERTS=C:\path\to\corp-ca.crt, then restart Cursor. This helps when the Node.js inside Cursor doesn’t pick up the system certificate store.
  • Go to Cursor Settings > Network > Run Diagnostics and share what exactly fails.
  • Ask IT to exclude Cursor domains from SSL inspection: *.cursor.sh, *.cursor-cdn.com, *.cursorapi.com details are in the network configuration guide Network Configuration | Cursor Docs

Quick check to confirm this is the cause: connect to a different network without the corporate proxy, for example a mobile hotspot, and try again. If it works there, the issue is SSL inspection on your work network. Let me know what the diagnostics show.