Why does Cursor always report errors in the corporate network? The answer has been written in the official Common Issues: Cursor's AI features rely on HTTP/2, and if the network, VPN, or proxy does not support it, it may cause indexing failures, abnormal AI functions, or unstable connections. The official recommendation is to go to 'Cursor Settings'> 'Network' and click 'Run Diagnostics', and if you confirm that it is an HTTP/2 compatibility issue, then go to the application settings and turn on 'Disable HTTP/2'. The official document is Cursor Common Issues.
Why this switch is so critical
Because many enterprise networks, Zscalers, VPNs, or special proxies block streaming requests, Cursor relies on HTTP/2 for streaming responses. What you see is not "login failed", but the AI request link behind it does not work.
More stable investigation sequence
- Run the network diagnosis first to see if even the Cursor service is unstable.
- If you are on a corporate network or under a proxy, test Disable HTTP/2 again.
- If necessary, switch to a cleaner network environment for retesting.
This kind of problem is most afraid of suspicion of the account at the beginning, but in many cases, it is just that the network layer does not support the transmission method of Cursor.
