Web fetch still restricted after removing a custom connector in dot?
Users are reporting an issue where dot's web fetch remains restricted even after removing a custom connector. This problem prevents dot from opening URLs that regular ChatGPT can access, suggesting a potential bug where a connector-related safety restriction persists post-removal. Some users describe their dot's web reader as "corrupted," indicating that web fetch might be automatically disabled and not properly re-enabled for dots.
时间与来源
时间显示为 UTC
显示时区：UTC
本地时区尚不可用，暂时显示 UTC。
发布当时偏移：UTC+02026年10月25日 04:03 UTC
收录当时偏移：UTC+02026年10月25日 06:00 UTC
- 发布
- 2026年10月25日 04:03
- 收录
- 2026年10月25日 06:00
- 来源类型
- 开发者社区
- 档位
- 社区
- 信源状态
- 正常
档位是按信源手工设定的编辑判断，不是逐条打分。
Anyone else seeing this? After installing and then removing a custom connector, dot’s web fetch still seems restricted. Could a connector-related safety restriction be sticking around after removal? Regular ChatGPT can open the same URLs, but dot can’t.
This seems like a safety measurement bug ... that web fetch is automatically disabled. But then they forgot to remove it for Dots. now my Dots web reader is corrupted.