Cant reach grok bot computer

Support Help
,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

cant reach Grok BOt , *.cursorvm.com, both on Mobile and on system and tried all the thing mentioned and it is still not working

Steps to Reproduce

you will see it when you try to login

Expected Behavior

nothing is happening after that

Screenshots / Screen Recordings

error.png
error.png1061×842 19.1 KB

Operating System

Windows 10/11

Version Information

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the report and the screenshot. I can see the “Can’t reach your computer” screen mentioning firewall, VPN, proxy, and *.cursorvm.com.

This isn’t about a reset or reinstall, which is why those don’t help. The error you’re seeing is a failed DNS lookup for *.cursorvm.com, and that DNS resolve happens on your network or ISP side, not ours. This can happen with some ISPs, including your current one Reliance Jio. Please don’t reset or reinstall again, it won’t help here.

Try these in order:

  1. On Windows, switch to a public DNS: Settings > Network & internet > Wi-Fi (or Ethernet) > your connection > Hardware properties > DNS server assignment > Edit > Manual > turn on IPv4 > Preferred DNS 1.1.1.1, Alternate DNS 8.8.8.8 > Save. If you’re on Windows 11, also set DNS over HTTPS to On (automatic template) for both. Then fully quit Grok Bot right click the tray icon > Quit and reopen it.

  2. On Android: Settings > Network & internet > Private DNS > Private DNS provider hostname > enter one.one.one.one > Save, then reopen the Grok Bot app.

If it still won’t connect, open Command Prompt on your PC Windows key, type cmd, press Enter, run these three commands, and paste the full output here:

nslookup test.us8.cursorvm.com
nslookup test.us8.cursorvm.com 1.1.1.1
nslookup google.com

Another quick test is to connect via a hotspot from a different carrier not Jio, like Airtel or Vi. If it works right away there, it’s definitely the network.

One more note in case you’re behind a corporate DNS filter or a custom resolver. Your allowlist needs both patterns *.cursorvm.com and *.*.cursorvm.com hosted computers use nested subdomains, and a single wildcard won’t cover them. This doesn’t matter for most home connections, but if the DNS steps above don’t help, it’s worth checking.

Let me know how it goes.