Help me！help me! help me!

Support Help
,
1

Request ID: d49eee5e-2a86-4205-bbc4-f92fc99ce0e2
An unexpected error occurred.
[internal] certificate signature failure
RetriableError: [internal] certificate signature failure
at _Ob (vscode-file://vscode-app/d:/app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9323:6865)
at mBr (vscode-file://vscode-app/d:/app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9323:5417)
at ZHm (vscode-file://vscode-app/d:/app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9324:12870)
at Object.classify (vscode-file://vscode-app/d:/app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9324:17485)
at AOb (vscode-file://vscode-app/d:/app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9324:5856)
at async Kel.runWithSharedTurnRunner (vscode-file://vscode-app/d:/app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9324:16837)
at async YG.runAgentLoop (vscode-file://vscode-app/d:/app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:12036:52450)
at async LWl.streamFromAgentBackend (vscode-file://vscode-app/d:/app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:17886:15130)
at async LWl.getAgentStreamResponse (vscode-file://vscode-app/d:/app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:17886:24972)
at async P8e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9490:2511)

5

Hey, thanks for the report. The certificate signature failure error means something on your network path like a VPN, a proxy client like Clash or V2Ray, a corporate proxy, or an antivirus with HTTPS scanning like 360 or Huorong is rebuilding the TLS certificate for Cursor servers, and the client correctly rejects that connection. This happens outside Cursor, so the request never reaches our servers.

Try these in order:

  1. Open the regular editor settings Ctrl+, not the separate Cursor Settings panel, search for systemCertificates, and enable http.systemCertificates and http.experimental.systemCertificatesV2. This lets Cursor trust certs from the Windows certificate store, where a proxy or AV may install its root CA. The setting is case sensitive, so it’s safer to find it in the UI and tick the checkbox instead of typing it manually.
  2. Go to Settings > Network, run Run Diagnostics, then switch HTTP Compatibility Mode to HTTP/1.1. HTTP/2 is stricter about cert validation through proxies. The equivalent in settings.json is cursor.general.disableHttp2: true.
  3. Check any TLS interception software. Either disable interception for Cursor domains *.cursor.sh, api2.cursor.sh, *.cursorapi.com, *.cursor-cdn.com, *.gcpp.cursor.sh, or make sure the tool’s root CA is added to Trusted Root Certification Authorities in Windows.
  4. The fastest way to confirm the cause is to try a different network, like a mobile hotspot. If it works there, it’s definitely traffic interception on the original network.

If the UI settings didn’t help, as a fallback you can point to a corporate .crt via the NODE_EXTRA_CA_CERTS environment variable.

Let me know if the error still happens after this.