iOS captive portal auto-launch fails on known Wi-Fi

Question

Level 1

0 points

iOS captive portal auto-launch fails on known Wi-Fi

My network advertises a CapPort API via DHCP option 114. The API returns a spec-compliant 200 application/captive+json with "captive": true, "user-portal-url" Cache-Control: no-store etc. and a packet capture confirms the device fetches and receives this response. On first join the portal launches reliably, however on a remembered SSID iOS shows only the 'Open Portal Page' button in SSID settings, not the automatic captive portal like it does on first connect or after forgetting the SSID. So my question is, what determines whether iOS auto-presents the portal on a known network versus only surfacing the button — and is there a recommended API response or network condition to make auto-presentation reliable? I tested this on 3 different iPhones running latest iOS with same results.

Posted on Jun 11, 2026 5:32 AM

Reply

Answer 1

SravanKrA

Level 10

447,160 points

Jun 11, 2026 5:45 AM in response to k4r0l1

iOS often fails to auto-launch captive portals on known Wi-Fi networks due to IPv6 preference, Safari extensions, or cached authorization states. The most reliable fixes are manually forcing the portal via Safari (captive.apple.com), forgetting and rejoining the network. Updating to the latest iOS version also resolves many of these bugs.

IPv6 vs IPv4 preference: iOS prioritizes IPv6 DNS queries, but many captive portals only support IPv4. This mismatch prevents the login page from loading.
Safari extensions/ad blockers: Privacy or script-blocking extensions can block portal redirects.
Cached authorization state: iOS may think you’re already authorized while the Wi-Fi system disagrees, leaving you stuck.

Go to Settings → Wi-Fi → (i) → Forget This Network → Rejoin.

Reply

Answer 2

Jun 11, 2026 5:52 AM in response to k4r0l1

I think this question will go over the heads of the vast majority of users on this user to user only forum. I've been on this forum daily for over 15 years and I certainly can't provide an answer to you. For most of us, we just connect to a Wifi network and as long as the connection is stable, we don't give it much thought.

I think you may have more luck taking this question to a higher level technical support person at Apple directly. If you're in the US, you can call Apple at: 800-MY-APPLE and you'd need to ask for a higher level tech support.

Reply

Answer 3

LotusPilot

Level 10

325,630 points

Jun 11, 2026 6:41 AM in response to k4r0l1

Perhaps this support page will be helpful with troubleshooting:

Use captive Wi-Fi networks on your iPhone, iPad or iPod touch – Apple Support

Apple devices reportedly uses this URL (not an API) to test for a Captive Network:

https://www.apple.com/library/test/success.html

Reply

Answer 4

SravanKrA

Level 10

447,160 points

Jun 11, 2026 5:46 AM in response to k4r0l1

You may get better and prompt responses if you may kindly provide the iPhone Model that you have and the iOS version if it is known to you and re-post.

With the limited information that you have provided, It is hard to even guess the problems faced by you.

You may get faster and better responses to your query by --> Writing an effective Apple Support Commun… - Apple ...

Please re-post with detail so that someone else can help.

Reply

Answer 5

k4r0l1 Author

Level 1

0 points

Jun 11, 2026 6:33 AM in response to lobsterghost1

Thank you. I was targeting other network administrators that have perhaps faced similar issues with their clients, but as suggested will try contacting higher level support.

Reply