The agent computer never becomes reachable. Banner reads “Can’t reach your computer.” Recover and Reset both fail server-side at the identical stage — “Starting Grok Bot’s computer,” then error out. Reset wipes data before failing, so retrying is destructive with no chance of success.
Steps to Reproduce
Launch Grok Bot, Pro account. Banner: “Can’t reach your computer.”
Run Recover → stalls at “Starting Grok Bot’s computer,” 50% → “Recovery couldn’t finish.”
Run Reset → wipes data, creates computer, stalls at same step, 50% → “Reset couldn’t finish. Computer may be in a partial state.”
Expected Behavior
Recover or Reset provisions a working agent computer the app can reach.
Hey, thanks for the detailed report and the screenshots.
Good news first. The Grok Bot computer on our side is working fine. Each Recover and Reset did create a new computer, and it came up in about a minute. The problem is that your Mac’s network can’t resolve the address the app uses to connect to it. This lookup happens on your side, so Recover and Reset won’t fix it. For now, it’s best not to press Reset again.
Try switching your Mac to public DNS:
System Settings → Network.
Select your active connection (Wi-Fi or Ethernet) → Details.
DNS tab.
Under DNS Servers, click + and add 1.1.1.1, then click + again and add 8.8.8.8.
OK.
Fully quit Grok Bot (menu bar icon → Quit, or Cmd+Q). Just closing the window isn’t enough.
Open Grok Bot again and wait about 2 minutes.
If you want to test the lookup directly, open Terminal and run:
If the first command fails but the second returns an address, that confirms it’s a DNS issue.
If you can’t change DNS, switching to a different ISP can help. A hotspot from the same provider usually won’t help. After switching networks, fully quit and reopen the app again.
Let me know if the Can’t reach your computer banner disappears after step 7. If not, please send the output of both commands.
I have the same issue. After I added the DNS, the app appears to retry several times (a couple of minutes) and then just goes to this page where Retry doesn’t appear to do anything.
Hey, thanks for the details and screenshots. One important note: your case is different from the original one in this thread.
In your nslookup output, both commands resolve successfully, both via the default resolver you have set to 1.1.1.1 and explicitly via 1.1.1.1. The IPs look normal. So DNS on your machine is working and the DNS step is no longer the issue. If the name resolves but the app still can’t reach the computer, the block is happening at the connection level, not at name resolution.
Usually something like this is intercepting or blocking traffic to the box:
VPN or a corporate network or proxy
Antivirus or firewall
DNS filter or ad blocker like AdGuard, Pi-hole, and similar. Even if resolving works, it can still drop the connection
To narrow it down:
If you have a VPN, ad blocker like AdGuard or Pi-hole, or antivirus with network filtering, temporarily disable them completely. Then fully quit Grok Bot, menu bar icon > Quit, or Cmd+Q. Just closing the window isn’t enough. Open it again and wait about 2 minutes.
If that doesn’t help, try a completely different network, a different ISP, for example a mobile hotspot from another provider. This is the fastest way to check if your current network is blocking the connection.
Also, to help me narrow it down:
Your OS and Grok Bot version
Whether this is a home or corporate network, and if you use VPN or a proxy
Whether you have any ad blocker, antivirus, or firewall installed
Let me know what you get after steps 1 and 2, then we can decide what to check next.
