CRITICAL: Omada Captive Portal Fails to Open on Android Devices ('Not Secure' Page Loop) - Need Official Fix

Dear Omada Team and Community,

I am writing to report a highly frustrating and persistent issue regarding the Captive Portal functionality in the Omada SDN solution, specifically affecting Android devices. I have made a substantial investment in the Omada ecosystem, and this bug is severely impacting the user experience.

The Problem:

1. Android Failure: When an Android device connects to the open guest Wi-Fi network, the system-level pop-up (captive portal detection) is redirected to the controller's IP Address. The page correctly displays the "Connection is not secure" warning (due to the IP/Self-Signed Certificate). However, even when the user selects the option to "Continue/Proceed anyway," the login portal page fails to load or open. The client remains completely stuck and cannot authenticate.

2. iOS/iPhone Success: In stark contrast, when an iPhone connects, it is also redirected to the same IP and shows the same "not secure" warning, but after clicking "Continue/Done," the login portal loads and functions perfectly.

3. Persistence: This issue has been ongoing for a long time, and unfortunately, recent updates to the Omada SDN Controller have not resolved this critical functionality gap.

My Network Setup (Current Omada Hardware Investment):

• Gateway: ER605

• Access Points: EAP110-Outdoor, 2x EAP225-Outdoor, EAP653, EAP650, EAP235-Wall

I understand the "Not Secure" warning is a separate matter (related to the IP address/certificate). However, the complete failure of the portal to load after the warning is acknowledged, exclusively on Android, indicates a severe bug in the Omada platform's handling of the Android captive portal mechanism.

I am extremely frustrated, as this basic failure makes the Captive Portal unusable for a large segment of users. I am now seriously considering migrating to a competitor solution like UniFi or utilizing an expensive third-party cloud hotspot service, purely because the core functionality I need is broken.

I urgently request an official response and a commitment to release a fix for this Android-specific Captive Portal issue in the next SDN update. Please advise on any known workarounds or required settings to resolve this critical flaw.

Thank you for your immediate attention to this matter.