Hey, thanks for the detailed log. This isn’t a Cursor bug. It’s a certificate verification failure on the network side. unable to verify the first certificate means the TLS connection to Cursor servers is being intercepted via SSL inspection, or your system trust store is missing the required root CA. The handshake fails on your side, so the request never reaches our servers. There’s nothing we can fix on our end. This is solved by adjusting your environment. Since you’re on a university network (.edu, Windows), this is a very common corporate or university SSL inspection setup.
What to try:
- Quick test: connect via your personal hotspot or off the university network. If it works, the issue is SSL inspection on that network.
- Install the corporate or university root CA into the Windows certificate trust store. Cursor uses system certificates by default.
- In Cursor Settings (JSON) add:
"http.experimental.systemCertificatesV2": true"cursor.general.disableHttp2": true
- Temporarily disable HTTPS or SSL scanning in your antivirus (Kaspersky, ESET, etc.) to test.
- If your machine or network is managed by IT, ask them to allowlist
*.cursor.shto bypass SSL inspection, or provide the required CA.
Similar thread with the same case: Unable to verify first certificate
Your account is fine. This is a network configuration issue. Let me know if any of the steps above helped.