i’m unable to use the Cursor Tab feature due to what looks like an ssl certificate signature failure. i have a self-signed cert in my corporate network’s keychain which seems to prevent calls being made to the API. other features like Chat and Composer work fine.
i’m running:
- windows 11 enterprise build 26100.2605
- wsl 2.2.4.0 running ubuntu 22.04
- cursor 0.44.11 with vscode 1.93.1
here is a screenshot of the Cursor Tab output
edit: it doesn’t stop me using cursor since i can still use chat and composer, but drastically reduces in-code editing experience
has anyone else experienced something similar?
Hey, are you using a VPN, Zscaler, a firewall, or any software that alters network settings?
hey, yes, my corporate network uses Netskope that has a self-signed certificate in the chain
You can ask the network admin to whitelist these addresses so everything works properly.
i won’t be able to ask them to bypass the self-signed certificate for these domains. the solution for other services has been to point them to a certificate bundle on my local filesystem, so that the netskope self-signed cert is included in the chain.
is cursor tab using its own certificate bundle? can i configure it to point to my own?
Hey, unfortunately, we don’t have anything to offer here to help with this.
I don’t believe we currently have a way around using self-signed certificates in the chain!
ah that’s a pity - could you put this on your backlog please? the other features work, like chat and composer, but not cursor tab. in the meantime i’ve installed github copilot to get tab completion, but this is not ideal.
netskope is one of many network protection tools used in corporate networks, so i doubt i’m the only one facing this issue.
i’m happy to help provide more diagnostics if that helps get to the bottom of this issue.
Totally unofficial, and at your own risk if you try this, but there may be a workaround to get Cursor to accept the self-signed certificate, like so:
Found it on a StackOverflow thread, but your mileage may vary!
Will log it down on our internal backlog, as this is likely something other’s will want in the future
1 Like
thank you Dan, i’ll give this a try!
Maybe also try disabling HTTP/2 and seeing if that helps, as that can be stricter on policies like this!
1 Like
will do sir, and will report my findings here - thank you!
Thank you! For mac user there’s a similar one Mac CA VSCode - Visual Studio Marketplace.
I can confirm that this fixed the certificate issue for my case. Like you said, there’s indeed risk in accepting all local certificates, so hopefully official support is in place soon.
