Couldn't Reach Grok Bot's Computer

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

“Can’t reach your computer error” is visible and gives the popup “Couldn’t Reach Grok Bot’s Computer”. I have used only 4% of my weekly usage and the computer is accessible when using through my android phone.

Steps to Reproduce

Has been happening on my windows machine since 0.47.x everytime I open it.

Expected Behavior

No popup raising this error and being able to connect to Bot’s VM through my laptop

Operating System

Windows 10/11

Version Information

Version: 0.56.1
Built: 2026-09-17T18:33:31.407Z
Release Track: stable
OS: win32

Additional Information

I tried deleting the data from program files, %appdata%, logging out, uninstalling and installing. Nothing has resolved this. Attempting to click the “Recover Grok Bot’s Computer” does go through the flow of resetting the computer and reattempting connection but it never succeeds after 75%.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

7

Hey @Armorr, thanks for the report, and sorry for the trouble.

Good news first: your Grok Bot computer is healthy on our side, and your Bots, files, and logins are safe. The app on your laptop is reaching our servers fine, but the DNS lookup for the address it uses to talk to your computer is failing on your laptop’s network. That lookup happens on your network, which is why the popup appears every time you open the app and why reinstalling, clearing data, and Reset have not helped. It also explains why your phone works: it is on a different network. Please hold off on pressing Reset or Recover, they will not change this.

Two things to try:

  1. Switch your Windows DNS to a public resolver. Open Windows Settings, go to Network and internet, select your active connection (Wi-Fi or Ethernet), click Edit next to DNS server assignment, choose Manual, turn on IPv4, and enter 1.1.1.1 as preferred and 8.8.8.8 as alternate. If IPv6 is on for that connection, set it too: 2606:4700:4700::1111 preferred and 2001:4860:4860::8888 alternate. Save, then fully quit Grok Bot (right click the tray icon and choose Quit), relaunch it, and give it about two minutes.

  2. As a quick test, connect the laptop to your phone’s hotspot, fully quit and relaunch Grok Bot, and wait two minutes. If it connects there, that confirms the DNS on your regular network is the culprit.

If neither helps, please open Command Prompt (Windows key, type cmd, Enter), run these three commands, and paste the full output here:

nslookup test.us11.cursorvm.com
nslookup test.us11.cursorvm.com 1.1.1.1
nslookup google.com

Separately, there was a short service disruption on our side tonight between about 3:20 AM and 3:45 AM IST that may have added errors while you were writing this. That one is resolved.