常驻用量

抄作业 / 做成了什么 / Grok Bot

Forum: Grok Bot computer outbound non-HTTPS blocked since Oct 1

标题与摘要为原文,未翻译。

做了什么
Report that Grok Bot cloud computers block all outbound non-HTTPS (MySQL, SSH, IMAP/SMTP, FTP time out) since Oct 1, with multiple accounts confirming.
场景
周报 / 简报 盯 PR / 仓库
资料完整度
  • 作者与原链接有
  • 做了什么有
  • 来源原文摘录有
  • 截图 / 媒体有
  • 步骤 / 章节来源未提供
  • 提示词 / 配置原文来源未提供
  • 结果 / 数字来源未提供
  • 风险提示有
  • 相关条目有

— 表示来源没有给出,本站不补写。

来源原文摘录
Describe the Bug Titel: Grok Bot computer: all outbound non-HTTPS traffic blocked since Oct 1 (MySQL, SSH, IMAP/SMTP, FTP time out) Since October 1, 2026, around 11:37 CEST, right after a computer restart, my Grok Bot computer can only reach the internet over HTTPS. Every other outbound TCP connection times out. Nothing changed on my side. What I see from the computer’s terminal: • HTTPS on 443: works • Plain HTTP on 80: timeout • MySQL on 3306 (my own server): timeout • IMAP 993 and SMTP 465: timeout • FTP 21 and FTPS 990: timeout • SSH on 22, github[.]com included: timeout • Raw TCP on 443
展开全文 that isn’t TLS/HTTPS (ssh[.]github[.]com:443): no answer either So it looks like all egress now goes through a proxy that only passes HTTPS. Already tried: • The computer is on the latest version. • “Route traffic through this computer” was on and showed 0 routed. …
RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗

摘自论坛首帖,照录原文,未翻译。

效果截图
原帖截图
截图来自原帖
提示词

来源没有给出可直接复制的提示词原文。

怎么复制
  1. 读原文:forum.cursor.com ↗
  2. 把原文里的步骤/提示词整理成一条消息交给 Bot
  3. 先手动跑一次,再决定频率
风险与限制
  • 作者的结果不保证能复现,以原帖为准
用量预估
用金属计算器估一下