I’ve been using Cursor with a VPN without any problems for a long time, but I haven’t been coding for a while. When I opened it, I received an update notification from Cursor, so I obviously updated it. Now, I am getting a “Connection failed” error.
This is my last request ID: b8e9f38d-ada8-4107-921d-bf9015573af6.
Cursor version: 0.46.8
Reopened cursor multiple times, reindexed my codebase, tested on smaller codebases, didn’t make any changes.
Also tried to disable HTTP2 from settings, but then I got this error:
Chat mode is not supported when HTTP2 is disabled in the latest version of Cursor. If HTTP2 must be disabled (e.g. to work around particular proxy issues), you can install the previous version of Cursor available at Downloads | Cursor - The AI Code Editor. We are working on support for HTTP/1.1 in a patch release for version 0.46.x.
Note: downgraded to v0.45.17 and it’s working perfectly, even with http2 being enabled.
2 Likes
Hey, with the changes to Chat and Composer now being unified into one panel, this does mean than in certain later releases, users may face connection issues if within a high-security network that doesnt support HTTP/2.
The good news is we have a fix that we are testing internally, but should allow all Cursor features to work, even inside networks where HTTP/2 is not supported!
We are finalising the update at the moment, but I would expect this to be available within the next 48 hours (hopefully sooner!)
Hey Dan, Thanks for the update, I’ll be posting the result here then
How about cursor tab? Will it also be allowed to go through HTTP/1.1? That’s the only feature I can’t get to work even on 0.45.x because zscaler blocking HTTP2. Also, list of models are not updating and I’m stuck with just sonnet 3.5 (for 0.46) and 3-5 initial models (for 0.45). Make me wonder if API to refresh list of models is also using HTTP2 and that is in scope to be fixed too. I’m pro subscriber btw.
I believe so, but let me confirm with the team!
1 Like
no luck with 0.46.10. hope 0.46.11 includes the fix
I can confirm that issue is currently fixed in v0.46.10.
Thanks.