You ask Siri a question that routes to ChatGPT, and instead of an answer you get a flat error: “Unable to connect to ChatGPT. Try again.” You tap retry. Same message. Your subscription is active, the ChatGPT extension is turned on, and Wi-Fi shows full bars. Nothing about your setup looks broken.
Unable to connect to ChatGPT Siri errors usually get blamed on your Apple Account, your subscription, or a buggy iOS update. The actual cause, in a lot of cases, never touches your iPhone at all. It lives on your router or whatever DNS service you’ve set up at home. It breaks the connection in a way that has nothing to do with ChatGPT or OpenAI specifically.
The Network Layer Nobody Checks First
Siri’s ChatGPT requests don’t travel straight from your iPhone to OpenAI’s servers. Apple routes that traffic through its own privacy infrastructure first, using a set of domains that start with “mask,” including mask.icloud.com and mask-h2.icloud.com. Those domains exist to anonymize network requests. They’re the same ones behind iCloud Private Relay.
A thread on Firewalla’s own community forum traces a case where Siri and ChatGPT integration stopped working entirely. The cause turned out to be DNS-over-HTTPS blocking inside the Firewalla device’s Family Protection feature. That feature was quietly blocking those same mask domains. Once the user allow-listed mask.icloud.com, mask-h2.icloud.com, mask-api.icloud.com, and mask.apple-dns.net, while keeping the rest of their DoH blocking in place, Siri could talk to ChatGPT again.
Why “I Don’t Use Private Relay” Doesn’t Rule This Out
This is the part that trips up almost everyone troubleshooting Unable to connect to ChatGPT Siri errors. A separate thread in Firewalla’s own support community describes a user who had Apple Private Relay switched off on their device entirely. Traffic to those same mask domains was still showing up in their blocklist logs anyway. The user put it directly: Apple appears to be “forcing some DNS queries over Apple Private Relay even if I have the feature disabled on [the] device.”
That single detail explains why this cause gets missed so often. Checking your Private Relay toggle and finding it off feels like it should clear your network as a suspect. It doesn’t. Whatever network-level filtering you’re running, whether that’s a Pi-hole box, a Firewalla, or NextDNS, can still intercept the mask-domain traffic Siri’s ChatGPT requests depend on. That holds true no matter what your Private Relay toggle says.
Fix 1: Allow-List the Mask Domains in Your DNS Filter
This is the direct fix for Unable to connect to ChatGPT Siri if you’re running Pi-hole, NextDNS, or a similar DNS-level ad blocker at home.
How to fix:
- Open your DNS filtering tool’s admin dashboard
- Find wherever you manage allow-listed or whitelisted domains
- Add mask.icloud.com, mask-h2.icloud.com, mask-api.icloud.com, and mask.apple-dns.net
- Save the change and try the Siri ChatGPT request again. Most DNS filters apply allow-list changes within a minute or two
Fix 2: Check Your Firewall or Router’s DoH and Family Protection Settings
Firewalla devices, and some mesh routers with built-in parental controls, block DNS-over-HTTPS by default. That’s meant to stop devices from bypassing content filtering. The same blocking catches the mask domains as a side effect.
How to fix:
- Open your router or firewall’s management app
- Look for DoH blocking, Family Protection, or similarly named content-filtering features
- Add an allow-list exception for the mask domains listed in Fix 1, rather than disabling the whole feature
- If your device doesn’t support per-domain exceptions, temporarily disable DoH blocking instead. That will confirm whether this is the cause, even if it isn’t a fix you want to leave in place permanently
Fix 3: Temporarily Switch to a Different DNS Server to Confirm the Cause
Before changing any settings permanently, it’s worth confirming the network is actually the problem rather than guessing.
How to check:
- On your iPhone, go to Settings > Wi-Fi, tap the (i) next to your network
- Scroll to Configure DNS and switch it to Manual
- Add a public DNS server like 1.1.1.1, then try the Siri ChatGPT request again
- If it works immediately on that connection, your home network’s DNS filtering is confirmed as the cause. From there, go back to Fix 1 or Fix 2 to resolve it properly rather than running on manual DNS indefinitely
Fix 4: Try the Request on Cellular Data Instead of Wi-Fi
This isolates the problem instantly, since cellular data doesn’t go through whatever DNS filtering your home network runs.
How to check:
- Turn off Wi-Fi on your iPhone, or step outside your home network’s range
- Confirm you have a cellular signal
- Ask Siri the same ChatGPT-routed question again
- If it works over cellular but fails every time on home Wi-Fi, that’s a strong confirmation this is a network-side block. It isn’t anything wrong with your Apple Account or the ChatGPT extension itself
Fix 5: Rule Out the Non-Network Causes Before Assuming It’s Your Router
Unable to connect to ChatGPT Siri errors do have ordinary causes too. It’s worth ruling those out quickly, especially if Fix 3 or Fix 4 didn’t confirm a network cause.
How to check:
- Go to Settings > Apps > Siri & Intelligence, confirm Extensions is enabled, and that ChatGPT is listed and toggled on under it
- Open the ChatGPT app directly and confirm you can sign in and get a response outside of Siri
- Check Settings > General > Software Update. Apple has shipped several point releases adjusting how Apple Intelligence extensions connect
- If all of the above check out, and cellular data still works fine while Wi-Fi fails, the network-level cause described above is the more likely explanation
Frequently Asked Questions
Why does Apple route Siri’s ChatGPT requests through Private Relay-style domains at all? Apple designed its Apple Intelligence and Siri extension requests to use the same privacy-preserving relay system it built for iCloud Private Relay, which masks the request’s origin. That’s a deliberate privacy choice on Apple’s part, not a bug. It just means any network-level system built to block Private Relay traffic can catch Siri’s ChatGPT requests as unintended collateral.
Does turning off iCloud Private Relay in Settings stop this from happening? Not reliably. Users troubleshooting this on Firewalla’s own community forum found their devices still generating requests to the mask domains with Private Relay turned off in Settings. That toggle isn’t a dependable way to rule out this cause.
Will allow-listing these domains weaken my ad blocking or parental controls elsewhere? It shouldn’t meaningfully. The mask domains are specific to Apple’s relay infrastructure, not general-purpose ad or tracker domains, so allow-listing just them leaves the rest of your filtering rules untouched. One trade-off is worth knowing about, though: it can also re-enable iCloud Private Relay functionality for other apps on that device. That’s worth considering if you specifically rely on DNS filtering to monitor or restrict a shared or managed device.
Is this the same issue as the ChatGPT extension simply not appearing in Siri settings? No. A missing or grayed-out ChatGPT extension under Siri & Intelligence is usually a region, Apple Account, or setup issue. That’s a different problem from Unable to connect to ChatGPT Siri showing up after the extension is already enabled and working, which is the case this article covers.
Should I report this to Apple or to my router or DNS provider? Both, if it’s affecting you regularly. Reporting to Apple through Feedback Assistant helps document how often Siri’s Apple Intelligence requests get caught by common network-level filtering setups. Reporting to your DNS or firewall provider matters too, since Firewalla’s own community is where this specific interaction has been documented so far. It isn’t in any official Apple support material yet. If you’re also chasing down Apple Pay failing specifically in Safari on Mac, that’s another case where the real fix sits on a completely different device than the one showing the symptom.
The Bottom Line
Unable to connect to ChatGPT Siri errors often have nothing to do with your Apple Account, your subscription, or the ChatGPT extension itself. Siri’s requests travel through Apple’s own mask-domain relay infrastructure. Any DNS-level ad blocker or firewall filtering that blocks those domains, or blocks DNS-over-HTTPS generally, breaks the connection with no indication of where the problem actually is. Switching to cellular data or a public DNS server briefly is the fastest way to confirm this is what’s happening to you. Allow-listing the specific mask domains in your filtering tool fixes it for good, without forcing you to give up the rest of your network-level blocking. This sits alongside Reminders’ “Alarms Access is Off” popup as another case where a setting on a completely different layer quietly controls a feature that looks broken on your iPhone.