Troubleshooting HTTPS Port Not Accessible Error and Causing Omada Firmware Upgrade Failure

Troubleshooting HTTPS Port Not Accessible Error and Causing Omada Firmware Upgrade Failure

Troubleshooting HTTPS Port Not Accessible Error and Causing Omada Firmware Upgrade Failure
Troubleshooting HTTPS Port Not Accessible Error and Causing Omada Firmware Upgrade Failure
2025-06-05 02:06:44

The topic was originally posted by Clive_A in Troubleshooting HTTPS Port Not Accessible Error and Causing Omada Firmware Upgrade Failure

This Article Applies to:

 

Omada devices.

 

Issue Description:

 

Failed to upgrade the Omada devices.

Error message: [Failed]Failed to upgrade ER605 ROUTER to firmware version 2.X.X online. Please check your network configuration and make sure the device can access the Controller's HTTPS management port.

 

Troubleshooting:

 

1. Export the Device Info and log to locate the reason.

In this log, you can see the process of the upgrade.

(The original information was removed or replaced for privacy.)

 

05-08-2025 22:27:16.924 INFO [comm-pool-15] [] c.t.s.o.m.d.d.m.u.c.f(): Start rolling upgrade devices /abcdefg = in OmadacId(EXAMPLE_OMADAC_ID) SiteId(EXAMPLE_SITE_ID)
05-08-2025 22:27:16.928 INFO [comm-pool-15] [] c.t.s.o.m.d.d.m.u.c.f(): Start download and batch upgrade devices OmadacId(EXAMPLE_OMADAC_ID) /abcdefg.
05-08-2025 22:27:16.930 INFO [comm-pool-15] [] c.t.s.o.m.d.d.m.u.c.f(): firmware info FirmwareBasicInfo(md5=80f99fff2e7c6667ebad2a4f3b45de9f, url=null, version=ER605_un_2.3.0_20250410-rel38015_common_v2_up_2025-04-10_10.36.02.bin, online=false) for BatchUpgradeRequestDTO(omadacId=OmadacId(EXAMPLE_OMADAC_ID), site=SiteId(EXAMPLE_SITE_ID), deviceTypeEnum=gateway, macs=[EXAMPLE_MAC_ADDRESS], compoundModel=ER605 v2.0, version=2.2.6, oemId=v2#oFzblYGwsX2example., role=, operator=, single=false, operatorIp=, resource=0, targetVersion=ER605_un_2.3.0_20250410-rel38015_common_v2_up_2025-04-10_10.36.02.bin) when checkFirmWareAndUpgrade
05-08-2025 22:27:16.984 INFO [comm-pool-15] [] c.t.s.o.m.d.a.u.UpgradeDeviceApplicationService(): start device upgrade in OmadacId(EXAMPLE_OMADAC_ID) SiteId(EXAMPLE_SITE_ID), upgradeId[EXAMPLE_UPGRADE_ID], devices [DeviceMac(EXAMPLE_DEVICE_ID)]
05-08-2025 22:27:17.077 INFO [upgrade-send-req-group-0] [] c.t.s.o.m.d.d.m.u.c.c(): OmadacId(EXAMPLE_OMADAC_ID)  upgradeId[EXAMPLE_UPGRADE_ID] DeviceMac(EXAMPLE_DEVICE_ID) upgrade status change from[UPGRADE_READY] to [REQUEST_SEND_START]
05-08-2025 22:37:22.006 INFO [comm-pool-2] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(): v2 device macEXAMPLE_MAC_ADDRESS of omadacIdEXAMPLE_OMADAC_ID upgradeIdEXAMPLE_UPGRADE_ID finished upgrade process in STAGE_DOWNVAL_TIMEOUT

 

Omada upgrade would take 10 minutes to determine if the upgrade is successful or not.

If it cannot download the firmware from the controller, it will generate a log with a reason.

When you are trying to self-debug this, you can pay attention to this and learn about the reason.

 

2. Check your ports if the firmware upgrade port is accessible.

Commonly, the error you would receive is that the HTTPS port is not available.

Which ports do Omada SDN Controller and Omada Discovery Utility use? (above Controller 5.0.15)

 

 

HTTPS is required to be accessible from the devices you are trying to upgrade. If your device that is trying to be upgraded cannot access the HTTPS port on the controller, this will cause the firmware to be downloaded from the controller to fail.

Once you hit the Upgrade in the controller page, manual or online upgrade, the firmware will be sent from the controller to the router.

 

 

If you are doing an online upgrade, the local controller HTTPS should still be accessible.

The controller sends the command and permits it to download to the controller.

Then the router will get the file from the controller. See the process below:

 

 

 

3. Check your diagram and how you adopt and manage the devices.

If your network is like this or you use this guide to manage, please note that your adopted devices are thinking your controller IP is a public IP address.

In this case, the port forwarding is inevitable. When you port forward your controller's HTTPS page to the public Internet, you should always use a strong password for management.

How to Manage Omada Devices at Different Sites Using Omada SDN Controller via Port Forwarding (Controller 5.0 or Above)

 

 

Update Log:

 

May 14th, 2025:

Release of the article.

 

Recommended Threads:

 

Which ports do Omada SDN Controller and Omada Discovery Utility use? (above Controller 5.0.15)

Old - Failed to update Omada devices by Omada Controller Online

How to Manage Omada Devices at Different Sites Using Omada SDN Controller via Port Forwarding (Controller 5.0 or Above)

 

Feedback:

 

  • If this was helpful, welcome to give us Kudos by clicking the upward triangle below.
  • If there is anything unclear in this solution post, please feel free to comment below.
  • If you encounter such an issue, please follow the troubleshooting steps above to check your settings. Besides, ensure your Omada Controller and Gateway are running with the latest firmware.
  • If the issue still exists after you try the suggestion above, please feel free to comment below or contact our support team with a detailed description of your issue and the steps you have tried.

 

Thank you in advance for your valuable feedback!

 

------------------------------------------------------------------------------------------------

Have other off-topic issues to report? 

Welcome to > Start a New Thread < and elaborate on the issue for assistance.

 

  0      
  0      
#1
Options
6 Reply
Re:Troubleshooting HTTPS Port Not Accessible Error and Causing Omada Firmware Upgrade Failure
a week ago - last edited Monday

  @Clive_A I'm running into this issue trying to upgrade my EAP783 from 1.1.4 to 1.1.5 from my software controller (6.1.0.19) and it's not clear to me how to handle it from this example.

I had no issue upgrading FW from the controller before upgrading to v6. I can confirm the HTTPS upgrade port is set to 8043. What's not clear to me is where the breakdown actually is. My ACL permits full access within the VLAN containing both the controller and the EAP783. I've tried port forwarding all of the controller ports from WAN/Gateway to the controller (which is what the example above seems to suggest), but that didn't help. Another confusing matter is that the log error refers to "HTTPS management port", which is different from the "HTTPS port for upgrade" in the system settings, so it's not clear which port is the problem.

Do I need to make specific forwarding rules for each device? Where in controller v6 do I find the settings I need to modify?

Thank you!

  0  
  0  
#2
Options
Re:Troubleshooting HTTPS Port Not Accessible Error and Causing Omada Firmware Upgrade Failure
Monday

  @Vincent-TP can you please help with the above?

  0  
  0  
#3
Options
Re:Troubleshooting HTTPS Port Not Accessible Error and Causing Omada Firmware Upgrade Failure
Tuesday

Hi  @underpickled 

 

Please check the port on this page, and make sure the corresponding port is opened.

  0  
  0  
#4
Options
Re:Troubleshooting HTTPS Port Not Accessible Error and Causing Omada Firmware Upgrade Failure
Tuesday - last edited Tuesday

  @Vincent-TP I have tried forwarding that port from the gateway to the controller's IP, if that's what you mean, but it did not solve the issue. Can you be more specific about what you mean by "open"?

 

EDIT: I've tried port forwarding and adding explicit ACLs to permit traffic on those ports between the primary VLAN and the internet. I still get the same error.

  0  
  0  
#5
Options
Re:Troubleshooting HTTPS Port Not Accessible Error and Causing Omada Firmware Upgrade Failure
Wednesday

Hi  @underpickled 

 

Yes, that's what I mean by open.

Are you trying to update firmware via remote access?

It's possible that your Internet service provider blocked that port. You may change the port and test again.

 

If possible, please update the firmware via local access. 

 

Please start a new thread with your network topology and screenshots of the relevant configuration pages for further analysis. 

  0  
  0  
#6
Options
Re:Troubleshooting HTTPS Port Not Accessible Error and Causing Omada Firmware Upgrade Failure
Wednesday

  @Vincent-TP thanks, Vincent! I started a new thread here.

  0  
  0  
#7
Options