Omada Controller 5.0.15 Adopting & Provisioning loop
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello everyone, After the Omada Controller Update to 5.0.15, most of our sites have the following problem: All APs in the site are in an Adopting & Provisioning loop. I don't know how to end it Restarting the controller or the entire server on which the controller is installed did not help. No clients can log in in this state. The problem affects the EAP225 and EAP245.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @DataMeister,
DataMeister wrote
I take it we can't simply downgrade. We either have to reload a backup or do something to the existing database?
Sorry to hear that you suffer from the same issue. I've forwarded your case to the support team who will help to fix the backup file for you.
They will reach you via your registered email address shortly, please pay attention to your email box later for follow-up. Thank you!
- Copy Link
- Report Inappropriate Content
Reporting that the update for the Log4j vulnerability (5.0.27) also has the same adopting loop problem:
https://community.tp-link.com/en/business/forum/topic/514452?replyId=1027326
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Marda236 wrote
Hello WirelessForEver, thanks for the information. It's a shame that the bug was not fixed in this update.
Totally! I need to patch for Log4j but it will break all my sites without sending in my backup file to support. It's not really sustainable for them to have to do it for all the installs needing to update to the latest version that fixes Log4j.
- Copy Link
- Report Inappropriate Content
Dear @WirelessForEver, @Marda236,
Marda236 wrote
Hello WirelessForEver, thanks for the information. It's a shame that the bug was not fixed in this update.
To confirm, did you install the Omada Controller v5.0.27 provided in this post?
- Copy Link
- Report Inappropriate Content
Fae wrote
Dear @WirelessForEver, @Marda236,
Marda236 wrote
Hello WirelessForEver, thanks for the information. It's a shame that the bug was not fixed in this update.
To confirm, did you install the Omada Controller v5.0.27 provided in this post?
Yes, that exact download. I had to roll back via a VM snapshot to 4.4.6. 4.4.6 to 5.0.27 had the same stuck on "ADOPT" behavior as 4.4.6 to 5.0.15.
- Copy Link
- Report Inappropriate Content
Dear @WirelessForEver,
WirelessForEver wrote
Yes, that exact download. I had to roll back via a VM snapshot to 4.4.6. 4.4.6 to 5.0.27 had the same stuck on "ADOPT" behavior as 4.4.6 to 5.0.15.
Thank you for your valued feedback. I'd like to escalate to the TP-Link support team who could help you more effectively.
They will reach you via your registered email address shortly, please pay attention to your email box later.
Thank you for your great cooperation and patience.
- Copy Link
- Report Inappropriate Content
Fae wrote
Dear @WirelessForEver,
WirelessForEver wrote
Yes, that exact download. I had to roll back via a VM snapshot to 4.4.6. 4.4.6 to 5.0.27 had the same stuck on "ADOPT" behavior as 4.4.6 to 5.0.15.
Thank you for your valued feedback. I'd like to escalate to the TP-Link support team who could help you more effectively.
They will reach you via your registered email address shortly, please pay attention to your email box later.
Thank you for your great cooperation and patience.
Thanks! Happy to help fix this bug once and for all (especially with organizations prioritizing the patching of Log4j vulnerabilities).
It also will be great to enable 2FA on 5.x.x!
- Copy Link
- Report Inappropriate Content
Exactly the same issue here, not entirely happy having to play about with the backup file etc, is there a plan to have this fixed as a part of a proper update?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 6506
Replies: 39
Voters 0
No one has voted for it yet.