Anyone have issues with Captive portal detection? We don’t have any luck with Captive Portal working to shut off warp and allow the portal to load. We are using a Managed Deployment, so WARP is deployed with parameters and there is no parameter for Captive Portal, however I was told if the setting is set inside Cloudflare, it would pull that setting from our Cloudflare profile on the website, and i’ve confirmed it’s set to have Captive portal detection on for the max time of 10 minutes.
Hello,
Did you ever resolve this issue? We are running into captive portal detection on Aruba networks it seems only.
I spent a good amount of time with support on this and it’s not fixed, supposedly they are working a Custom Feature to allow us to configure captive portal ports, but I haven’t heard anything regarding that yet…But long story short it’s going to depend on the Captive Portal Port being used by Aruba Networks. For my case the captive portal was trying to redirect to a server on port 8449. Cloudflare only allow TCP ports 80, 443, and 8080 through the firewall in captive portal mode. The port allow can’t be set dynamically, because the captive portal redirect target is from an untrusted source, meaning an adversary would be able to create a captive portal that would allow data to leak via an arbitrary port.
We see issues with almost every major Hotel and Airport regarding Captive Portals. We have to provide a Key to disable warp and have it re-enable after so long so they can get the Captive Portal.