When the Grok Bot computer blocks non-HTTPS outbound traffic
When you finish this page, you will know which outbound connections still work on an affected computer, what not to reset, and how to file a useful support note. This is a known issue, not a plan limit. Checked Oct 5, 2026.
Cursor staff (Colin, Community Support Engineer) said on the forum on Oct 2, 2026 that since a recent change, some Grok Bot cloud computers can only make outbound HTTPS connections on port 443. Database, mail, SSH, FTP, plain HTTP, and apps that need other ports, such as Viber, time out. Staff said this is not a restriction on your plan or account, and it is not intended. The team is aware and is tracking it. As of Oct 5, 2026 there was no official fix, changelog entry, or status note.
The documented baseline disagrees with that live behavior. Grok Bot security says Network Controls is Enterprise only, and teams without a policy default to allow-all. It also says hosted computers reach the internet through shared static egress IP addresses by default, and that current ranges are available from your account team. Staff confirm the HTTPS-only behavior is what some computers are doing anyway. This page names both sides and does not pick one.
What still works
- Use HTTPS-based APIs on port 443. Staff said HTTPS-based endpoints still work.
- Clone git repositories over HTTPS instead of SSH. Staff said that path still works.
- Leave the computer as it is. Staff said there is no reliable workaround on the computer itself yet, and there is no need to reset or reinstall.
The route-through-desktop setting will not help. Docs.x.ai and the Bot changelog call it Route egress through this desktop under Settings → Computer. Staff and some help pages call it Route traffic through this computer. Staff said it only covers the computer's web traffic (the browser), so it does not open database, mail, SSH, FTP, or Viber ports.
When to contact support
If you are still blocked after using HTTPS on 443 and git over HTTPS, contact support with the details in Troubleshooting under "Before contacting support". Cursor's get-help page asks for the account email, version and platform, what you were doing, a screenshot, steps you already tried, and the request ID. Email is hi@cursor.com.
This is not resolved for everyone. One user reported Viber working again on Oct 2; staff said afterwards that it was not fully resolved, and that some computers can still only make standard HTTPS connections on port 443.
Related
- All how-tos: How-to index.
- Turn the desktop route on when you actually need it: Route Grok Bot egress through your desktop.
- When hostname HTTPS fails after that route is on: When the route-through-desktop relay breaks hostname HTTPS.
- Recovery order when the computer is unreachable for other reasons: Update or recover the Grok Bot computer.
- More Grok Bot jobs live on the Grok Bot hub.
Pitfalls
- Treating this as an Enterprise Network Controls policy or a plan cap. Staff said it is neither.
- Turning on the route-through-desktop setting, or running Update or Reset, as a fix. Staff said those do not help here.
- Expecting published shared egress IP ranges on the public docs. Official docs say current ranges are available from your account team.