Unable to get local issuer certificate after update

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Internal error ocuuring when trying to use agents.
Ran network diagnostics, it drew up [internal] unable to get local issuer certificate(API, Ping, Chat, Agent).
I am already doing on HTTP/1.1 (since I had problems on 2.0 from the start)

Steps to Reproduce

Whenever I try to use the agents(even after relaunching or reboot computer)

Operating System

Windows 10/11

Version Information

Version: 3.9.16 (user setup)
VS Code Extension API: 1.105.1
Commit: 042b3c1a4c53f2c3808067f519fbfc67b72cad80
Date: 2026-06-27T06:41:01.941Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

The error started occuring after updating to this cursor version.

Additional Information

Request ID: c41646d9-ac54-4ac3-9a84-f37e890a1960
[internal] unable to get local issuer certificate
RetriableError: [internal] unable to get local issuer certificate
at uAS (vscode-file://vscode-app/c:/Users/PCH-01/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12056:27795)
at EMc (vscode-file://vscode-app/c:/Users/PCH-01/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12056:26530)
at Fny (vscode-file://vscode-app/c:/Users/PCH-01/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12057:11929)
at Object.classify (vscode-file://vscode-app/c:/Users/PCH-01/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12057:16434)
at hAS (vscode-file://vscode-app/c:/Users/PCH-01/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12057:5824)
at async Oqm.runWithSharedTurnRunner (vscode-file://vscode-app/c:/Users/PCH-01/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12057:15786)
at async iH.runAgentLoop (vscode-file://vscode-app/c:/Users/PCH-01/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24486:3041)
at async Lkh.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/PCH-01/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24505:13862)
at async Lkh.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/PCH-01/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24505:22888)
at async IRe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/PCH-01/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12142:2399)

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, this is the classic corporate SSL/TLS inspection issue. A proxy or antivirus on your network is re signing HTTPS with its own root certificate that Cursor doesn’t trust, so the TLS handshake fails before the request even reaches us. That’s why HTTP/1.1 doesn’t help here. It’s not about the transport, it’s about certificate trust.

The same case on 3.9.16 was fixed like this. Try:

  • Open VS Code Settings (not Cursor Settings), find http.experimental.systemCertificatesV2, and turn it on.
  • Keep http.systemCertificates enabled.
  • Fully restart Cursor. Not Reload Window. Close it and open it again.

If it doesn’t help:

  • Make sure your corporate root CA is installed in Windows under Trusted Root Certification Authorities, not only in the personal store. Check via certmgr.msc.
  • Alternatively, ask IT to bypass SSL inspection for *.cursor.sh, *.cursor.com, and api2.cursor.sh.

Let me know if enabling systemCertificatesV2 fixed it.

6

It was fixed smoothly! Thank you a lot for you rapid response