抄作业 / 做成了什么 / Grok Bot
Grok Bot reconnect loop — api2.cursor.sh bad cert host
标题与摘要为原文，未翻译。
- 做了什么
- Grok Bot stuck on “Can’t reach your computer” because api2.cursor.sh resolves to 100.60.17.13 serving a mismatched certificate.
- 场景
- 未归类
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体来源未提供
- 步骤 / 章节来源未提供
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出，本站不补写。
- 来源原文摘录
Where does the bug appear (feature/product)? Grok Bot Describe the Bug Grok Bot stays on “Can’t reach your computer” and keeps reconnecting. Cursor’s updater says the certificate is invalid and the server may be pretending to be api2[.]cursor[.]sh. api2[.]cursor[.]sh CNAMEs to api2geo[.]cursor[.]sh, then api2direct[.]cursor[.]sh. Both 1.1.1.1 and 8.8.8.8 return 100.60.17.13 in that set. Connecting to 100.60.17.13 with that hostname presents a certificate for devapi[.]english[.]com (Pearson PLC / Sectigo), so TLS hostname verification fails. From the same network, 34.235.15.195 in the same DNS
展开全文
set presents the correct certificate (CN=api2[.]cursor[.]sh, issuer Amazon RSA 2048 M01). Mobile hotspot works because it gets a different address list. No local proxy or antivirus HTTPS scanning. Changing DNS to 1.1.1.1 and 8.8.8.8 does not remove 100.60.17.13. Steps to Reproduce …RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自论坛首帖，照录原文，未翻译。
- 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 读原文：forum.cursor.com ↗
- 把原文里的步骤/提示词整理成一条消息交给 Bot
- 先手动跑一次，再决定频率
- 风险与限制
- 作者的结果不保证能复现，以原帖为准
- 用量预估
- 用金属计算器估一下