Grok bot not working for more than 24 hrs

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Stuck on reconnecting your computer

Steps to Reproduce

Whenever I open the app it shows reconnecting your computer

Screenshots / Screen Recordings

Screenshot 2026-09-03 133308.png
Screenshot 2026-09-03 133308.png1919×1026 5.14 KB

Operating System

Windows 10/11

Version Information

Version 0.36.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

Hey, thanks for the report. First, the good news: your Grok computer on our side is fully healthy. It wakes up as soon as you open the app and stays ready. The issue is somewhere else: your PC can’t resolve the address that the app uses to reach that computer. This DNS lookup happens on your network, so reinstalling, resetting, or updating won’t change anything. It’s not something in your app settings.

Let’s try this step by step:

  1. Switch DNS to a public resolver, and do it for both protocols. On JioFiber, changing only IPv4 often doesn’t work because Windows keeps using the router’s IPv6 DNS.
    • Settings > Network and internet > select your active connection Wi-Fi or Ethernet > its properties
    • Next to DNS server assignment click Edit > Manual
    • Turn on IPv4: Preferred 1.1.1.1, Alternate 8.8.8.8
    • Turn on IPv6: Preferred 2606:4700:4700::1111, Alternate 2001:4860:4860::8888
    • Save
  2. Open Command Prompt Windows key > type cmd > Enter and run:
    ipconfig /flushdns
nslookup test.us10.cursorvm.com
    In the output, the Server line should show 1.1.1.1 or one.one.one.one, not reliance.reliance, and the lookup should return IP addresses.
  3. Fully quit Grok Bot right click the tray icon > Quit, don’t just close the window. Then open it again and wait about 2 minutes.

If it still won’t connect after that, connect your PC to your phone hotspot on a different carrier not Jio, restart Grok Bot, and wait a couple of minutes. If it works there, that confirms it’s a DNS issue on your normal network.

Also, please paste the full output of these commands from your normal network:

nslookup test.us10.cursorvm.com 1.1.1.1
nslookup test.us10.cursorvm.com
nslookup google.com 1.1.1.1

If google.com resolves but test.us10.cursorvm.com fails via your default resolver, it’ll be clear the lookups are being blocked or spoofed inside your network, and we’ll suggest the next step. Let me know how it goes.