Connection failed. If the problem persists, please check your internet connection or VPN. @RandomUser-64026 Guys from Cursor team, please address this issue as a priority since it happens to me and all my friends that use Cursor IDE. I get it, app is not perfect and still in development. But currently you are charging for a promt that didn’t even finished. Sometimes it says Error, not charged but in most cases (~70% it still charges)
I’m still hitting the same issue. Typically happens right after we hit the 25 call limit that requires confirmation. Super disappointing to the fact that it’s almost unusable.
yeah. i also noticed if you switch to a different model in same chat and ask it something, then go back to original model that you had issues with, sometimes it will start working again. But not always…
I am on a mac. But, the issue came up when I was assigned a client for work. The client required me to install a VPN. Installing the vpn was an easy process. Nothing out of the oridinary.
I went back into work on some code for something unrelated and was getting errors with chats. I then tried to make a request to my backend on the ui I am building with React, and the request was always timing out. My backend showed no hits/usage. So, I tried a ping google.com command in Cursor’s terminal and I got more timeout errors along with a 100% packet loss rate. Then, I ran the ping test on my normal terminal and could see successful pings.
So, if you want to figure out if this will help you, please try both of those things. Open Cursor, open terminal, run ping google.com. Then, close Cursor and open your terminal “Command + Space” → type “Terminal” hit enter. Type in ping google.com. If the results dont match (not the ms times but one succeeds and one does not) continue.
The problem is that your vpn rewrote your network settings and is causing Cursor to fail on every request. To fix this you can try to uninstall and reinstall. If that does not work then run the below code at your own discretion.
killall "Cursor"
Open your main terminal
sudo dscacheutil -flushcache sudo killall -HUP mDNSResponder networksetup -setdnsservers Wi-Fi 1.1.1.1 8.8.8.8 networksetup -setwebproxystate Wi-Fi off networksetup -setsocksfirewallproxystate Wi-Fi off
Finally run env -i PATH="$PATH" /Applications/Cursor.app/Contents/MacOS/Cursor
That fixed the issue. Cursor devs, please, on restart, pull the latest network configs. Or set a default and switch if requests are failing. You are an AI company, act like it.