Why can't my Grok Bot connect to SSH, MySQL or email servers?
Last checked October 28, 2026 · Grok Bot changes often
Since a change around October 1, 2026, some Grok Bot computers could only make outbound HTTPS connections on port 443, so SSH, database, IMAP/SMTP, FTP and plain HTTP connections timed out. Staff said this was not intended and was being tracked. Until it is fixed for your computer, use HTTPS-based APIs, clone git repositories over HTTPS, and do not reset your computer — it will not help.
Symptoms
ssh,git@github.com:clones, MySQL or Postgres connections time out.- Sending mail over SMTP or reading over IMAP from scripts fails.
- HTTPS websites and APIs keep working.
The official forum thread on this collected more than 50 replies in October 2026.
What staff said
Some Grok Bot computers can only make outbound HTTPS connections on port 443 … The team is aware and is tracking it. There's no reliable workaround on the computer itself yet.
They also noted that "Route traffic through this computer" does not help, because it only covers the browser, and that there is no need to reset your computer.
Workarounds
- Git: clone and push over HTTPS with a token instead of SSH.
- Databases: use the provider's HTTPS API or a serverless HTTP driver where one exists.
- Email: use the Gmail or Outlook plugin instead of SMTP/IMAP from a script.
- Your own services: expose an HTTPS endpoint on port 443.
Check whether it still applies
This is a dated platform issue. Test with a simple non-HTTPS connection from the Bot's terminal before redesigning a workflow around it, and check the forum thread for a fix.