I’m seriously considering canceling my Pro+ subscription, mainly because Cursor has been consistently unusable for me.
On the same network, Codex and Claude Code both work perfectly fine
But with Cursor, I keep running into network-related issues during debugging
At this point, I’m just tired of dealing with it. I think I’ll cancel my subscription and switch over to Claude Code instead.
Cursor relies heavily on HTTP/2 for its AI features (streaming responses, Agent, Ping, API calls). Something between you and Cursor’s servers is terminating the TLS handshake before it completes — typically a proxy, VPN, firewall, or SSL inspection layer that doesn’t handle HTTP/2 well. Claude Code runs in your terminal and inherits system-level proxy/cert settings differently than Electron-based Cursor does, so it sidesteps the issue entirely.
Fix it in 60 seconds:
Open Cursor Settings
Search for http2
Enable “Disable HTTP/2” (forces fallback to HTTP/1.1)
This is the official fix from Cursor’s docs — it forces HTTP/1.1 usage and resolves the issue for corporate networks, VPNs, and proxies like Zscaler that block HTTP/2. Cursor
Alternatively, you can add this directly to your settings.json:
“cursor.general.disableHttp2”: true
If that doesn’t fix it, you’re likely behind SSL inspection (common in enterprise environments) and need to add your network’s root CA cert. Self-signed corporate certs in your network’s keychain can prevent API calls from completing the TLS handshake. In that case, set the NODE_EXTRA_CA_CERTS env variable pointing to your corp cert bundle before launching Cursor.
Source: Cursor Tab not working: certificate signature failure
@Colin This issue is actually very serious, and it has really disappointed me in Cursor… Maybe I’m just a small customer.
I changed my plan from the $60 Pro+ plan to the $20 Pro plan because of this issue.
What I want to emphasize is that the reason I’m downgrading is not the model pricing, but simply the usability of the software.
On the same network, Codex and Claude Code work completely fine, while Cursor keeps running into inexplicable problems. I had actually already made the changes you suggested, and the issue still persists.
A lot of the time with client software, many users run into problems that engineers may not even want to believe are real, but for the people using it, the experience is extremely frustrating. I hope you will take this seriously.
Alright. I canceled my Cursor subscription.
