The console errors tell us exactly what’s happening. The repeated certificate signature failure errors mean your corporate network is intercepting Cursor’s HTTPS connections and re-signing the certificates (SSL inspection). Cursor doesn’t trust the re-signed certificate, so every backend API call fails — this is why @Docs, the marketplace, authentication, and team features all break.
This is almost certainly related to your company’s network security setup.
To fix this, your IT team needs to do one of the following:
-
Add Cursor’s domains to the SSL inspection bypass/exemption list (recommended). The domains that need to be bypassed: you can find the full list in Cursor Settings > Network > “Copy Domains”
-
Install the corporate root CA certificate in the system trust store so that macOS (and therefore Cursor) trusts the re-signed certificates. If your IT team has a corporate CA bundle, adding it to Keychain Access as a trusted certificate should resolve it.
As an immediate workaround while coordinating with IT, try switching to HTTP/1.1 mode: open Cursor Settings (gear icon), search for http2, and set cursor.general.disableHttp2 to true, then restart Cursor. This won’t fully fix the certificate issue but may help with some connection modes.
Also, the elementor.cursor-usage-monitor extension is separately failing (getting HTML instead of JSON when fetching its policy) — that may be the same proxy issue or a configuration problem with the extension itself. Worth flagging to whoever manages that extension internally.