Omada Hardware Controller fails to update any device firmware on remote sites
I FIXED IT!
I was no longer able to upgrade firmware on non-omada-router sites as well (or maybe I never did), so I started a port to port comparison of all the related tp-link web page I had ever visited, which I haven't closed for these 7 months.
I fixed the issue just a few days ago. I'm running the latest firmware "1.34.2 Build 20250110 Rel.75707".
All I ended up changing was:
In Global -> System settings, I changed the "HTTPS Port for Controller Management" from 443 to 8043 (and http from 80 to 8088 although it's redirected)
On the controller site, I changed Settings -> Transmittion -> NAT accordingly.
THAT'S IT!
I have been able to bring all my devices firmware on all 4 remote sites up to date (I'm currently connected on a recently created 4th remote site in another country).
I don't remember ever having changed this setting. Then again, I bought this controller back in February 2020 and originally managed only the one local site, so who knows. Maybe they used to have port 443 by default and changed it later? Either that or I changed it to 443 so as to not having to suffix :8043 and remember that port to acces my controller locally (as in 192.168.0.20 versus 192.168.0.20:8043), and forgot all about it.
Either way it shouldn't have been a problem. If the port can be edited, the NAT rules are consistent (I even tried DMZ without success) and devices on remote sites can be adopted, why does only FW update from remote sites not work?
Do you work for TP-Link? Your Member information doesn't say it, but the TP-Link icon next to your avatar makes me thing you do.
I suggest you update https://www.tp-link.com/en/support/faq/3281/ to reflect that a port different than 8043 will make it impossible to upgrade devices FW on remote sites, while this issue is looked into and fixed.
Regards,
Michael K.
I just took a look at my OC300 which only manages its local site, no remote sites.
It's "HTTPS Port for Controller Management" is at port 443, same as yours.
So if port 443 works for @nicolati on OC300 but was the problem on my OC200, that would point to a bug in the OC200 firmware, as it is behaving differently as OC300.
I might try to create a remote site on OC300 when I return from vacation and try this out.
One final notice as I'm closing all browser tabs related to this topic
Snapshot from https://community.tp-link.com/en/business/forum/topic/559150 (Edit: Hank21 I just realized this thread was posted by you)
So default port IS 443, but in order for OC200 to be able to upgrade devices on remote sites the port needs to be changed to 8043.
Go figure.
Be aware that changing that port, while it warns that a controller reboot is needed for it to take effect, it acutally REBOOTS AUTOMATICALLY right after clicking on "save".
EDIT 2:
https://www.tp-link.com/us/support/faq/3281/ ALSO says 443 is for omada HARDWARE controller, while 8043 is for SOFTWARE controller.
