Grok Bot Windows — fresh profile setup fails with “Can’t reach your computer” after backend fix

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

I am a SuperGrok user on Windows.

My initial Grok Bot setup worked normally before creating my first Bot. Authentication/linking succeeded, my SuperGrok account and usage information were visible, and the UI worked normally.

The problem started only after I created my first Bot and Grok Bot began setting up its Agent Computer.

After that, the app became stuck on a white screen with a black loading dot.

@Colin previously made a backend adjustment for my account in another thread. However, the issue still persists more than 9 hours later.

I have since completely terminated all Grok processes, reinstalled Grok Bot, and renamed the local Grok Bot profile so the app created a fresh profile.

With the fresh profile, onboarding works normally again, but setup now consistently fails at:

“Setting up your Grok Bot…”

followed by:

“Grok Bot could not finish setup. Can’t reach your computer right now.”

I have tested Wi-Fi, mobile hotspot, US VPN and Japan VPN endpoints. DNS resolution works, TCP 443 succeeds, proxy CONNECT and TLS succeed, and the Cursor VM endpoint is reachable through AWS ELB.

Could you please check the provisioning / connection status of the Agent Computer associated with my account?

Since setup never completes, I cannot access Recover, Update Agent Computer, or Reset Agent Computer myself.

I can provide my SuperGrok account email privately if required.

Steps to Reproduce

1.Launch Grok Bot on Windows.
2.Complete the initial onboarding.
3.Create the first Bot and continue to Agent Computer setup.
4.Grok Bot shows “Setting up your Grok Bot…”.
5.After waiting, setup fails with “Can’t reach your computer right now”.
6.Clicking Retry does not solve the issue.
7. also reproduced the issue after creating a completely fresh local Grok Bot profile.

Before resetting the local profile, the app would become stuck on a white screen with only a black loading dot after the first Agent Computer setup attempt.

Expected Behavior

Grok Bot should successfully provision/connect to the Agent Computer, complete the initial setup, and open the normal Bot interface so I can start using the Bot.

Operating System

Windows 10/11

Version Information

Grok Bot 0.30.0 on Windows

Additional Information

@Colin previously made a backend adjustment for my account in another thread and asked me to open a new thread if the issue persisted.
Unfortunately, the issue is still present after more than 9 hours.
I also tested with a completely fresh local Grok Bot profile. The onboarding UI works again, but Agent Computer setup consistently fails with “Can’t reach your computer”.
To clarify: Cursor IDE itself is not affected. Grok Bot is completely unusable because the Agent Computer setup cannot complete.

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the detailed report. I’ve figured out what’s going on.

First, the good news: the Agent Computer we created for your account is up on our side and has been working fine the whole time. The issue isn’t provisioning and it’s not the computer itself. The step that breaks is where your PC tries to connect to it. Recreating the computer isn’t needed and won’t help.

Key point: Grok Bot does not use the Windows system proxy or a local HTTP proxy like 127.0.0.1:7890 to connect to the Agent Computer. It connects directly. That’s why all your checks (DNS, TCP 443, CONNECT, TLS, awselb) pass, they go through the proxy. But the app ignores the proxy and goes direct, and that direct connection gets reset. Your US/Japan VPN in system-proxy mode also isn’t picked up by the app.

One more detail: your computer is in the us10 region (*.us10.cursorvm.com), not us8, so tests against us8 won’t hit the right host.

What you need to do is route the app’s traffic through a tunnel:

    1. Fully close Grok Bot. In Task Manager, kill all Grok Bot processes.
    1. In your VPN or proxy client, switch from system-proxy mode to TUN mode. In different clients this may be called Enhanced mode, Global, or Virtual network adapter or TUN. This mode routes all apps through the tunnel, including apps that ignore proxy settings.
    1. Open PowerShell and run this exact command. It’s meant to bypass the proxy, the same way the app does:
    curl.exe --noproxy "*" -I https://test123.us10.cursorvm.com
    If TUN mode is working, you should quickly get HTTP/1.1 404 Not Found with Server: awselb/2.0. If the command hangs, times out, or shows connection reset, the app will fail the same way. That means TUN isn’t active yet, so double-check the setting.
    1. Once step 3 returns 404, start Grok Bot and let setup run again.

Let me know what step 3 prints and whether setup finishes after step 4. If your client doesn’t have TUN mode, tell me which VPN or proxy app you’re using and I’ll suggest an alternative.

And about the white screen with a black dot on the old profile: that’s a separate display issue in 0.30.0, and one of the next updates fixes it. So creating a fresh profile was the right move.

7

Thanks, this solved it.
After enabling TUN mode properly, curl.exe --noproxy "*" -I https://test123.us10.cursorvm.com returned 404 Not Found / awselb/2.0, and Grok Bot connected successfully immediately afterwards.
The root cause was indeed that Grok Bot’s direct connection was bypassing my system proxy. Thanks for identifying it!