Grokbot Can’t Reach your Computer - Reset requested

Support Bug Reports
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Grokbot Can’t Reach your Computer

Recovery failed
Grok Bot could not reach the computer, so Grok Bot might not be able to work.
some error like this

Steps to Reproduce

After some update, I am not able to use Grokbot at all.

Screenshots / Screen Recordings

Screenshot 2026-09-02 at 2.51.41 PM.png
Screenshot 2026-09-02 at 2.51.41 PM.png2110×1568 230 KB

Operating System

MacOS
iOS

Version Information

Version: 0.30.0
Release Track: stable
OS: darwin

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

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

Good news first: your Grok Bot computer is healthy on our side, and the Recover you ran this morning did complete successfully. The issue is that your network’s DNS is failing to resolve the address the app uses to reach that computer. Because the lookup happens on your network, Reset and Recover can’t fix it. It also started before the app updated, so the update isn’t the cause.

Two things to try:

  1. Point your Mac at a public DNS resolver, then restart Grok Bot. Open System Settings > Network, select your active connection (Wi-Fi or Ethernet), click Details, choose DNS in the sidebar, then click + under DNS Servers and add 1.1.1.1, add 8.8.8.8, and click OK. Fully quit Grok Bot (Cmd+Q) and reopen it.

  2. As a quick test, connect your Mac to a phone hotspot on a different mobile carrier and open Grok Bot. If it works there, that confirms the DNS on your regular network is the culprit. The same test applies to the iPhone app if it’s on the same Wi-Fi.

If neither helps, please open Terminal while on the same network, run these three commands, and paste the full output here:

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

If the google.com lookup returns addresses but the first two fail, that tells us lookups for our servers are being blocked or altered inside your network.

FYI, this looks like the Mac version of the issue reported here (on Windows):

7

this worked
thanks