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

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

CRITICAL: Omada Captive Portal Fails to Open on Android Devices ('Not Secure' Page Loop)
CRITICAL: Omada Captive Portal Fails to Open on Android Devices ('Not Secure' Page Loop)
2025-11-01 00:41:46 - last edited Tuesday
Tags: #Portal #SDN Controller
Hardware Version:
Firmware Version:

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.

  0      
  0      
#1
Options
3 Reply
Re:CRITICAL: Omada Captive Portal Fails to Open on Android Devices ('Not Secure' Page Loop)
2025-11-03 08:08:31 - last edited Tuesday

Hi  @Henke10k 

 

Thanks for posting here. 

This is likely related to the device’s browser.

To better understand the situation, please give us the following info:

1. A screenshot of your controller's Device page, which will help us identify the specific hardware and firmware versions of the SDN devices you are using;

2.What's the type of controller(hardware or software) you are using and its firmware version.

3. If possible, please also share a video showing the Android connecting failed progress.

4. Is this issue consistently reproducible on Android devices, or is there a chance that authentication can still succeed? If yes, how often?

5. Will this affect all Android devices? 

6. This never happen with IOS devices?

 

 

  0  
  0  
#2
Options
Re:CRITICAL: Omada Captive Portal Fails to Open on Android Devices ('Not Secure' Page Loop)
Tuesday

  @Henke10k 

 

We are very concerned about your feedback. Has the issue been resolved? 
 

  0  
  0  
#3
Options
Re:CRITICAL: Omada Captive Portal Fails to Open on Android Devices ('Not Secure' Page Loop)
23 hours ago - last edited 23 hours ago

I am able to reproduce something similar.  Not sure if its the exact same situation as the OP but ......

Portal - Custom URL triggers "This Page is not Secure" when portal loads if HTTP>HTTPS portal redirect is enabled

 

After having finally figured out the best approach to setting a custom portal URL (this is not well documented at all) and realizing the controller has to be rebooted after changing any portal Port/URL settings (or the change doesn't take effect) i have noticed the following

 

If "HTTP to HTTPS Redirect" for the portal is turned on in Global > System Settings, the portal page always triggers a "This Page is Not Secure" warning on Chrome/Edge/Firefox/Safari on Windows, Android and Mac (havent tested iphone so far)

 

If the portal url is not customized and its just the controller IP, this does not occur

 

The two methods i have set custom portal URL to mask the controller IP from the URL

- LAN DNS entry for controller IP and using that as the portal URL (eg, portal.local)

- Internet DNS "A" record to create a portal-dot-ourwebsite entry that matches our website but resolves the internal controller IP and setting that as portal url

 

Both methods produce the "This page is not secure" issue when portal HTTP>HTTPS redirect is enabled

 

Support indicated this is due to a SSL certificate mismatch so a certificate matching the portal url (if modified) need to be imported to the controller

-ST

  0  
  0  
#4
Options