First, the good news: your Grok Bot computer is fine, and your phone is talking to it normally, so you don’t need to recreate or rebuild anything. That would only reset the working session on your phone.
What this looks like: the Grok Bot app on your Windows PC isn’t reaching our servers at all, while Cursor on the same PC connects fine. That usually means something on the PC is handling the two apps differently, most often a proxy, firewall, or antivirus. The *.cursorvm.com screen is a generic message for any failed connection attempt, so the DNS checks went in the wrong direction.
Can you check these and send back the results?
Fully quit Grok Bot: right click the tray icon bottom right and select Quit.
Windows Settings → Network & Internet → Proxy. Check if Use a proxy server or Use setup script is On. If either is On, Grok Bot doesn’t use that proxy while Cursor does, and that would explain the difference. Temporarily turn it off, or tell me what tool set it up v2ray, Clash, etc.
Windows Security → Firewall & network protection → Allow an app through firewall. Make sure Grok Bot is allowed for Private and Public. If you have a third party antivirus, add Grok Bot to its exceptions.
curl.exe connects directly just like Grok Bot, so this will show whether direct connections are being blocked.
Open Grok Bot again and sign in. If you still see the connection screen, connect your PC to your phone hotspot for a minute and try again.
In your reply, include: the proxy setting from step 2, the command output from step 4, whether the hotspot worked, and your Grok Bot version Settings → Updates. That’s enough to pinpoint where the connection is breaking.
Thanks for the details and screenshots. I can see the curl output and the DNS lookup for cursorvm.com.
Good news: your tests show that your direct network connection is working. curl.exe -sI https://api2.cursor.sh returned HTTP/1.1 200 OK, and curl.exe -sI https://test.us8.cursorvm.com returned 404 Not Found from awselb/2.0. That means the request reached our servers just fine. The 404 on that path is expected. So it doesn’t look like your firewall or DNS is blocking anything.
About one.one.one.one can't find cursorvm.com: Not implemented, that’s normal and not the cause. The cursorvm.com root domain doesn’t have an A record. You can also see that in the second screenshot where it says it has no A records. Grok Bot only uses subdomains like test.us8.cursorvm.com, and those resolve fine for you.
Since the direct network path looks fine, we should look at the app side. Could you please share:
Your Grok Bot version (Settings → Updates).
Does the same account work on your phone or another device right now?
Windows Settings → Network & Internet → Proxy: is Use a proxy server or Use setup script enabled? If yes, which tool set it up (v2ray, Clash, etc.).
Connect your PC to your phone hotspot for a minute and try signing into Grok Bot again. Did it help or not?
With that info, I can narrow down exactly where the connection is failing.
Hey, thanks for coming back with an update, and I’m glad it worked.
@oleje32, the fact that a clean reinstall helped, with no reboot and no network changes, fits the picture. Your network path was fine, so the issue was on the app side or its install state, not firewall or DNS.
@Jaha, same idea for you. Your curl tests showed the direct connection works api2.cursor.sh → 200 OK, test.us8.cursorvm.com → 404 from awselb, which is expected, and cursorvm.com having no A record is normal. Since the network looks clean, try the same steps that worked above:
Fully close Grok Bot right click the tray icon → Quit.
Uninstall the app via Windows Settings → Apps.
Reinstall from x.ai/bot and sign in again.
If the connection screen still hangs after reinstall, reply and also share the Grok Bot version Settings → Updates and the result of the hotspot step connect your PC to your phone’s hotspot for a minute and try signing in. Then we can narrow down exactly where the connection is breaking.
