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.
Time & source
Times shown in UTC
Display time zone: UTC
Local time zone unavailable; showing UTC.
PublishedOffset at this time: UTC+0Oct 25, 2026, 04:03 UTC
IngestedOffset at this time: UTC+0Oct 25, 2026, 06:00 UTC
- Published
- Oct 25, 2026, 04:03
- Ingested
- Oct 25, 2026, 06:00
- Source type
- Dev community
- Tier
- Community
- Source status
- Healthy
Tier is a per-source editorial setting, not a per-item score.
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.