I’m trying to go back to using my Grok Bot account. I opened it today and the latest messages were from 2:21 AM GMT-3. It hangs on “Setting up…” or Trying to reconnect. Both on MacOS (latest stable release, M5 Max) and on my iPhone 16 Max. I tried to logout and login again but then it just says gives me an error screen saying “Can’t Reach Grok Bot’s Computer”. Now and then it goes after that screen but just shows me an empty UI and a message saying “Reconnecting to your computer”. Now and then it goes after that screen but just shows me an empty UI and a message saying “Reconnecting to your computer”
Update: Tried to enter from different machines/networks/everything and nothing fixed it. The only thing i can think of is that this is an issue from grok bot’s side and not mine.
Hey, thanks for the detailed report. You’re right in your guess, this isn’t about your Mac, iPhone, or network, so you can ignore the firewall or VPN tip on that screen. This shouldn’t happen, and it’s not something in your setup. It’s on the service side, and we’re looking into it.
One important thing. Please don’t press Reset, Update, or Recover again, and don’t reinstall the app or sign out. In your case those buttons won’t help. The recovery needs to be finished manually on our side, and that’s what we’re doing.
Your Bots, files, and logins are safe. Everything was saved up to the moment your computer stopped responding, so in the worst case only the last couple of minutes of work right before that are at risk.
We’ll reply here as soon as recovery is complete and you can sign in again.
One question that’ll help for the future. Do you remember which Bot and which task were running roughly between 2:00 and 2:30 AM your time? Once you’re back in your account, we’ll tell you how to run that kind of task so it doesn’t lead to this again.
I was told the system bugged and created 2 computers instead of 1 and the system didn’t know how to behave. I’ve got some issues where my account would switch between those giving me weird results.
Afaik it’s solved now. At least for the past hour.
