Issue connecting to the server

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

First time trying cursor and I get the following error:

Request ID: ae5080c1-d2c6-4660-be7b-4c4758a2a1b2
[internal] unable to get issuer certificate
mie: [internal] unable to get issuer certificate
at P5A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34267:23755)
at B5A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34267:22658)
at $5A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34268:6285)
at Wou.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34268:10400)
at async $Oa.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46832:10024)
at async n5u.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46886:9277)
at async n5u.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46886:13663)
at async bMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34329:17597)

Steps to Reproduce

I have it all the time

Expected Behavior

Cursor should start the agent correctly

Operating System

MacOS

Version Information

Version: 2.6.19 (Universal)
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

Yes - Cursor is unusable

4

Hi @Nicolas_Bonnet , thank you for the detailed report and stack trace. Based on the error message, this looks like a network or certificate configuration issue in your environment rather than a Cursor application bug.

From the error [internal] unable to get issuer certificate, the most likely cause is that traffic to Cursor is being intercepted by a corporate proxy or firewall that performs SSL inspection, which breaks the normal certificate chain validation on your macOS system. This pattern matches several existing reports from users on corporate networks or with tools like ZScaler.

Here are some steps that often resolve this class of issues:

  1. Open Cursor, go to Settings → Network, and run the built in network diagnostic to see if any connectivity or certificate checks fail.
  2. Confirm whether you are on a corporate or secured network (VPN, proxy, SSL inspection, or similar security stack managed by IT).
  3. In Cursor settings, try enabling http.systemCertificates and http.experimental.systemCertificatesV2, then fully restart Cursor and test again.
  4. If you are behind a corporate proxy or SSL inspection appliance, please ask your IT team to either:
    • add Cursor domains (such as https://api.cursor.sh and related endpoints) to the SSL inspection bypass / allowlist, or
    • install your corporate root CA certificate into the macOS system keychain so that the intercepted certificates validate correctly.
  5. If you are not on a corporate network, try a different network (for example, a mobile hotspot) and reboot your router to rule out a local network or DNS issue.

You can also review our networking troubleshooting guide here for more detailed instructions and required domains and ports:

If you have a moment, could you confirm whether you are on a corporate managed device or network with a proxy or SSL inspection in place?

5

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.