Hey @ALEKS1, thanks for the report and for attaching the DevTools log, that pinpoints it.
The browser part of the login is completing fine on our side, and “Return to Cursor” is reaching the app as expected. The step that fails is the app itself contacting our server (api2.cursor.sh) to pick up the session. It times out, which means something on this PC or network is blocking Cursor’s connection while still allowing your browser through.
It should print 404. If it hangs or shows an error instead, apps other than your browser are being blocked from reaching our servers.
If you are on a VPN, or your laptop runs a corporate security or proxy client (for example Zscaler, Netskope, or a firewall agent), temporarily disconnect it if your company allows that, then click Log In in Cursor again.
If step 3 or 4 fails, your IT team will need to allow Cursor and our domains through the proxy or firewall. This page lists what they need: Network Configuration | Cursor Docs
Let me know what you see at steps 2 and 4, and whether logging in works with the VPN or security client off.
So it looks like api endpoint is reachable via our proxy.
Please tell me if you need also reports about running test commands from the network documentation you’ve attached in your reply - but it is pretty similar to the above output from 2 point.
When i’m disabling VPN i’m start seeing errors about proxy connection in Developer Toggle Tools output, so it’s not the issue i suppose.
One thing in the curl output: curl asks your proxy to open a connection to api2.cursor.sh (the CONNECT api2.cursor.sh:443 line), but the proxy never answers, so the request just hangs. A working connection would show HTTP/1.1 200 Connection established right after that line and print 404 at the end. So the proxy set in your https_proxy variable is not letting the connection through.
That matters because Cursor uses that same https_proxy variable, while your browser uses the Windows proxy settings instead. That would explain why the browser login works but Cursor times out, and why Cursor shows proxy errors when the VPN is off.
Could you try this test?
Fully quit Cursor (File > Exit), then check Task Manager that no Cursor.exe is still running.
Connect the VPN.
Open PowerShell and run: Remove-Item Env:https_proxy, Env:http_proxy -ErrorAction SilentlyContinue
In the same PowerShell window, run: & "C:\Program Files\cursor\Cursor.exe"
Click Log In, finish the browser step, and click Return to Cursor.
This only affects that one launch, nothing is changed permanently.
If you’re logged in after step 5, your IT team has two permanent options: allow api2.cursor.sh and the domains on the network configuration page through the proxy in https_proxy, or tell you which proxy Cursor should use. You can then set that proxy as "http.proxy" in %APPDATA%\Cursor\User\settings.json.
