I consistently and repeatedly get “Connection Error” “Connection failed. If the problem persists, plesae check your internet connection or VPN”.
I do not use a VPN, and I have gigabit fiber that works perfectly. This issue keeps occuring and the only fix is to: Restart Cursor, which allows me 1 prompt before the error appears again, or create a new chat window which gives me 2-3 (sometimes) prompts before it appears.
This product worked perfectly throughout the 7-day free trial, and now that I’m paying this issue is appearing after 30-50 prompts… Like a shadowban/limit of sorts?
Hey, thanks for the report. Since you mentioned that you’ve already tried all the usual steps, the issue might be related to the large context in this chat.
Quick note: 30-50 prompts in a single chat is quite a lot. A long chat history, especially when a lot of code has been changed, can cause performance issues. It’s usually better to start a new chat for a new task to keep things more stable.
Creating a new chat, the issue shows up again after 2-3 messages if it was popping up before
During the 7-day trial I used the heck out of it to vibe code an entire server stack with Docker Compose, a custom API with user auth, a website front-end with some fancy logic… Over 7-8k lines and it was more than happy. Hundreds of messages. As soon as I’m on a paying account this occurs. Likely a coincidence, but annoying nonetheless.
Sure. After a single message in the chat, I see: Request ID: c7a09d67-cccb-4280-b859-a67a5a78c712
It got to step 3/6 of it’s planned steps and gave this error. Neither Resume nor Try again works…
Restarting and using Try Again, then copying gives me this:
Request ID: c7a09d67-cccb-4280-b859-a67a5a78c712
ConnectError: [internal] Serialization error in aiserver.v1.StreamUnifiedChatRequestWithTools
at vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4989:396431
Only writing “continue” and hitting enter gets it to work.
I have been trying to get it to have this issue again but I haven’t been able to cause it again since I was getting it consistently on and on the day before posting this originally.
I haven’t been using Cursor as much as I did in days prior, but I will update if it comes up again