Grok Bot desktop is stuck on Cannot reach your computer / Retrying. The app is signed in on Cursor Pro. Privacy Mode is Active (not Legacy). Dashboard onboarding was completed with Share Data OFF (You are all set). Retry and full app restart do not connect.
This is not a local network or DNS failure. Direct HTTPS to the official Agent Computer hosts works (HTTP 404 from the load balancer as expected). Local logs show ConnectError.Internal on entitlement-read, privacy-mode, and profile-fetch, plus ControlPortCallError. base_url_kind is unknown, so the client never receives the Agent Computer hostname.
Please re-provision or re-attach Grok Bot entitlement and the Agent Computer for this Cursor Pro account on the backend. I have not used Recover or Reset.
Steps to Reproduce
Sign in to Grok Bot 0.44.0 on Windows with a Cursor Pro account.
Confirm Privacy Mode Active on the Cursor dashboard Settings page (not Legacy).
Complete Grok Bot onboarding with Share Data left OFF until You are all set.
Fully quit and reopen Grok Bot.
The app stays on Cannot reach your computer / Retrying. Retry does not connect.
Expected Behavior
Grok Bot should receive entitlement and the Agent Computer hostname, then load Bots. Pro includes Grok Bot access. Retry should not loop forever with ConnectError.Internal.
Operating System
Windows 10/11
Version Information
Grok Bot 0.44.0 (Windows x64)
OS: Windows 11 (10.0.26200)
Cursor IDE: 3.20.10
Plan: Cursor Pro (individual, not Teams)
Additional Information
Timezone: Asia/Tokyo. Observed 2026-09-11.
No VPN. WinHTTP and IE proxy off.
Direct HTTPS to the official Agent Computer test hostnames returns HTTP 404 Server awselb/2.0 as expected.
The Cursor API is reachable.
Dashboard Members is Upgrade to Teams only. No individual Enable Grok Bot switch.
Logs: entitlement-read and privacy-mode return ConnectError.Internal. box_reachability is ControlPortCallError. base_url_kind is unknown.
Please re-provision entitlement and attach or create the Agent Computer on the backend. I have not clicked Recover or Reset.
Hey, thanks for the detailed report. Here’s the key point up front: nothing needs to be re-provisioned on our side. Your account is entitled, your Agent Computer is up and healthy, and entitlement and privacy checks for your account are responding today without errors from Cursor and from cursor.com. So there’s no need to use Reset or Recover, they won’t help here.
What we’re seeing: the Grok Bot app on your PC connected normally during the day on September 10, and after that not a single request from the app reached our servers. The ConnectError.Internal entries are what the app logs when the secure connection is getting cut off on the PC itself, before the request is even sent. Most often, the cause is something on the PC or network inspecting HTTPS traffic using its own certificate. Cursor and your browser trust the Windows system certificate store, so they work. The Grok Bot app currently trusts only public certificate authorities, so it fails. This also explains why your direct HTTPS tests to the Agent Computer hosts succeed.
Try these in order:
In Edge or Chrome, open https://api2.cursor.sh, click the lock icon, then Connection is secure, then the certificate icon, and check the Issued by field. It should say Amazon Amazon RSA 2048 M01. If it shows something else (an antivirus, a security product, or something from your university or organization), that’s the cause.
Check whether any security software is scanning HTTPS traffic. It’s usually called Encrypted connections scanning, SSL/TLS filtering, HTTPS scanning, or Web protection in products like Kaspersky, ESET, Avast or AVG, Bitdefender, Norton, Trend Micro, Sophos, and similar. If it’s enabled, turn it off or add Grok Bot to exclusions. Then fully quit Grok Bot from the system tray and relaunch it.
If nothing changes, connect your PC to your phone hotspot (turn off Wi-Fi), then fully quit Grok Bot again, relaunch it, and wait a couple of minutes.
Then tell us what you saw in step 1, whether step 2 or 3 helped it connect, and the name of the security software on the PC. If it still doesn’t work, attach this file: %APPDATA%\Grok Bot\desktop-structured-log-spill.v1.json.
One more thing: the app downloaded 0.47.0 on September 10, but you’re still on 0.44.0. Once you’re connected again, install the latest version from Cursor · Download Grok Bot.
Thank you very much, Dean. Your diagnosis was exactly right, and Grok Bot is working again.
Step 1: Issued by was Kaspersky Anti-Virus Personal Root Certificate, not Amazon.
Security software: Kaspersky Plus 21.26. Encrypted connections scanning was on (scan upon request from protection components).
I changed it to Do not scan encrypted connections. After that, the Cursor API certificate showed Issued by Amazon RSA 2048 M01. I fully quit Grok Bot and relaunched it. It connected. I did not use Recover or Reset.
Thank you again for the clear steps and for checking the account on your side.
Great, glad it’s working, and thanks for coming back with the details, that really helps.
So this confirms it: Kaspersky with Encrypted connections scanning enabled was swapping the certificate issuer to Kaspersky Anti-Virus Personal Root Certificate instead of Amazon. Because of that, Grok Bot couldn’t establish a secure connection. As soon as scanning was turned off and the issuer was Amazon RSA 2048 M01 again, everything started working.
A couple notes for next time:
If you turn Encrypted connections scanning back on in Kaspersky, the issue will come back. In that case, you don’t have to disable scanning entirely, you can add Grok Bot to the exceptions list.
Once you’re reliably online, update the app to the latest version from Cursor · Download Grok Bot. You were on 0.44.0 and there’s a newer one available.