抄作业 / 做成了什么 / Grok Bot
Windows Kaspersky HTTPS scan → ConnectError.Internal / Can’t reach computer
标题与摘要为原文，未翻译。
- 做了什么
- Staff (deanrie, 2026-09-11): Grok Bot trusts public CAs only—Kaspersky Encrypted connections scanning swaps the api2.cursor.sh issuer to Kaspersky Anti-Virus Personal Root Certificate and the app never reaches the Agent Computer (ConnectError.Internal). Turn scanning off or exception Grok Bot; do not Reset/Recover; confirm the cert issuer is Amazon RSA again, then quit/reopen and update past 0.44.
- 场景
- 写代码上线
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体来源未提供
- 步骤 / 章节来源未提供
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出，本站不补写。
- 来源原文摘录
Where does the bug appear (feature/product)? Grok Bot Describe the Bug Grok Bot desktop is stuck on Cannot reach your computer / Retrying. The app is signed in on Cursor Pro. Privacy Mode is Active (not Legacy). Dashboard onboarding was completed with Share Data OFF (You are all set). Retry and full app restart do not connect. This is not a local network or DNS failure. Direct HTTPS to the official Agent Computer hosts works (HTTP 404 from the load balancer as expected). Local logs show ConnectError.Internal on entitlement-read, privacy-mode, and profile-fetch, plus ControlPortCallError.
展开全文
base_url_kind is unknown, so the client never receives the Agent Computer hostname. Please re-provision or re-attach Grok Bot entitlement and the Agent Computer for this Cursor Pro account on the backend. I have not used Recover or Reset. Steps to Reproduce …RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自论坛首帖，照录原文，未翻译。
- 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 读原文：forum.cursor.com ↗
- 把原文里的步骤/提示词整理成一条消息交给 Bot
- 先手动跑一次，再决定频率
- 风险与限制
- 作者的结果不保证能复现，以原帖为准
- 用量预估
- 用金属计算器估一下