Grok Bot 0.72.1 on macOS. Sign-in shows “Sign-in did not finish. Try again.” Safari reaches Auth | Cursor - The best way to code with AI (“All set”) every time, four tabs of it, and the app stays signed out. A fresh relaunch failed in under a minute. Cursor itself is signed in. Not a timeout.
Luckily my phone’s app is working, but I use the Mac’s Desktop app wayyy more frequently and easily. Very annoying
Steps to Reproduce
Just trying to sign in
Operating System
MacOS
Version Information
Grok Bot 0.72.1 (stable)
macOS 27.0.1 (26A434), Apple silicon
The browser part of sign-in is finishing fine. The step that fails comes after it: the Grok Bot app on your Mac has to check in with our servers to pick up that sign-in, and right now the app’s own connections from your Mac to our servers are timing out. After a few failed tries it gives up with “Sign-in did not finish.” Safari, Cursor and the phone app reach us through your Mac’s normal network settings, which is why they still work.
The usual cause is a proxy, VPN, or firewall or network filter on the Mac that browsers follow but the Grok Bot app currently doesn’t. A few things to try:
Open System Settings → Network → your connection → Details → Proxies. If any proxy or automatic proxy configuration is turned on, quit Grok Bot, run this in Terminal, then reopen Grok Bot and sign in again. This should make the app use your Mac’s proxy settings: defaults write com.anysphere.sand SystemProxy -bool true
(To undo it later: defaults delete com.anysphere.sand SystemProxy)
If you use a VPN, or a firewall or filtering app (for example Little Snitch, LuLu or a DNS filter), check that it isn’t blocking Grok Bot, or briefly turn it off and try signing in.
As a quick test, join a different network (a phone hotspot works) and sign in there.
Before you retry, close the older “All set” tabs. Each Sign in click starts a fresh attempt, so only the newest tab counts.
If none of that helps, let us know which of these your Mac has (proxy, VPN, firewall or filter app) and whether the hotspot test worked!
I found the root cause of this issue on macOS (Grok Bot 0.72.1, Apple Silicon) in Taiwan.
The browser login succeeds, but the app fails to complete sign-in because api2.cursor.sh resolves to AWS IP addresses (3.92.129.183, 34.225.159.174, 52.21.130.202) that time out on TCP port 443.
I tested both my LAN and iPhone hotspot, with the same results. No system proxy or active VPN.
Working workaround:
Add this entry to /etc/hosts:
104.18.18.125 api2.cursor.sh
After flushing the DNS cache and restarting Grok Bot, sign-in completed successfully.
The Cloudflare IP responds correctly, while the AWS direct endpoints are unreachable from both tested networks in Taiwan.
Suggestion: Please investigate regional DNS routing for api2.cursor.sh and consider adding a fallback to reachable Cloudflare endpoints when the direct AWS connection times out.
This appears to be a network routing/reachability issue rather than an authentication issue.
Note: The hosts-file workaround is temporary, as Cloudflare IP addresses may change.
The addresses api2.cursor.sh resolves to (3.92.129.183, 34.225.159.174, 52.21.130.202) are the normal ones for most regions, Taiwan included, and we’re not seeing a wider problem reaching them from Taiwan or anywhere else today. The timeouts look specific to individual Macs and come in short bursts, often right after the app starts, rather than a regional outage.
@Luke_Lin, the 104.18.18.125 address you pinned is another route to the same service, so it works, but it isn’t a route we support for the app. It can change without notice, and the hosts entry overrides DNS for Cursor too. Once you’re signed in, please remove it:
Delete the 104.18.18.125 api2.cursor.sh line from /etc/hosts.
In Terminal, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
Quit and reopen Grok Bot.
The app should stay signed in. If sign-in or connections start timing out again, please reply with the time it happened (with your time zone), whether it was right after launching the app, and which network you were on. If you can get into Settings → System, the Network Debugger results would help too.
@TeamVMM, please try signing in again now. If it still fails, let us know the time it happened and whether any of the steps from my earlier reply (proxy setting, VPN or filter app, hotspot test) changed anything.