Add Authorized Certificates to Cursor

Feature Requests
1

We need an option to install custom certificates of authorities in Cursor.
This week the company that i work use an crap traffic monitor called Netskope.
Netskope replace the requests with his own certificate to see what we are doing and it breaks the cursor, we need a way to pass the certificate to the cursor so it stops breaking.
see the logs while i was executing cursor in my Ubuntu 22.04.5 LTS:

./cursor.AppImage                                                           ⏎
c [FetchError]: request to https://api2.cursor.sh/aiserver.v1.AuthService/DownloadUpdate failed, reason: self signed certificate in certificate chain
    at ClientRequest.<anonymous> (/tmp/.mount_cursory0d9Jk/resources/app/out/main.js:1:313656)
    at ClientRequest.emit (node:events:514:28)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:514:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'SELF_SIGNED_CERT_IN_CHAIN',
  code: 'SELF_SIGNED_CERT_IN_CHAIN'
}
2

After making this post, i did the change from https/2 to http/1.1 and restarted everything and it worked well for this case, will let it opened just in case someone is struggling with the same problem and google should index.

2 Likes
3

Well, some months passed by and Cursor added the Agents feature, which, doesnt run with the ■■■■ netskope, so please, Add the option so we can use this ■■■■ ssl and the good feature of agent.

Maybe it can be caused from the problem with puppeteer

4

Want to bump this thread. Haven’t been able to use Cursor over Netskope in consistent matter since .46 was released and I’ve tred almost all the troubleshooting steps available including the two that supposedly should fix the issue but do not:

  1. Disabled http/2
  2. Installed win-ca extension

Is there something coming out to address this?

1 Like
5

Agent should now work behind Netskope, using 0.50.x and http/2 disabled.

1 Like
6

Hi, I have the same issue, my version is as blow:
Version: 0.50.7 (user setup)
VSCode Version: 1.96.2
Commit: 02270c8441bdc4b2fdbc30e6f470a589ec78d600
Date: 2025-05-24T18:32:30.918Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631