# Grok Bot computer: all outbound non-HTTPS traffic blocked since Oct 1 (MySQL, SSH, IMAP/SMTP, FTP time out) **URL:** \ **Category:** Bug Reports\ **Tags:** networking, grok-bot\ **Created:** [October 1, 2026, 2:17pm UTC](https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504 "2026-10-01T14:17:31Z")\ **Posts on this page:** 1\ **Showing post:** 54
**Author:** ![Marveltools](https://avatars.discourse-cdn.com/v4/letter/m/e19adc/32.png) [@Marveltools](https://forum.cursor.com/u/Marveltools)\ **Post date:** [October 11, 2026, 9:17am UTC](https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504/54 "2026-10-11T09:17:56Z")
Encountered the same issue. Managed to find a workaround though. Not sure if it’s applicable to all issues people are facing here but it might be worth a shot. **Workaround: use DNS-over-HTTPS** The box’s DNS server returns fake `198.18.x.x` addresses, and the gateway behind them only forwards port 443. If you resolve real IPs over DNS-over-HTTPS (which itself runs over 443), connections on other ports go through. **System-wide fix.** Ask your bot to install `dnscrypt-proxy` listening on `127.0.0.1:53`, with DoH upstreams pinned to IPs (Cloudflare `1.1.1.1` and Google `8.8.8.8`), then set `/etc/resolv.conf` to `nameserver 127.0.0.1`. The box has no systemd, so have it start the resolver from a shell profile script so it comes back after a restart. ## Note: changing `/etc/hosts` or `resolv.conf` will trigger an approval prompt. Keep a backup of `/etc/resolv.conf` so you can roll back. --- _[View the full topic](https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504)._