EAP245 adopting for 30 minutes
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Team,
Just tried to upgrade two EAP245 from 5.0.3 to 5.0.4.
This suggestion popped up after the controller was upgraded to 5.0.30.
After the upgrade, the EAP245 is still on the adopting status. The version still says 5.0.3.
The log says that the upgrade failed. But it doesn't return to normal operations.
Based on the connected wifi devices the EAP's are still in a mode where they allow wifi connections.
I can logon to the webui. When doing so it asks me to reset for bypassing the controller.
Any suggestions how to move from here?
Kind regards - Will
The controller is local. Version 5.0.30 (Linux Debian) to be exact.
Disconnecting the power didn't help.
Then tried a reset to factory defaults => no improvement => still remains adopting.
After 2 minutes the error "adoption failed" popped up (see attached image) => tried with "retry" => no luck
I then gave the UFW-firewall config of the controller a closer look and found out that port 29814 wasn't in the accepted list.
Once added, the upgrade works - no problem.
Thank you for your time and patience.
Cheers - Will
.
The controller is local. Version 5.0.30 (Linux Debian) to be exact.
Disconnecting the power didn't help.
Then tried a reset to factory defaults => no improvement => still remains adopting.
After 2 minutes the error "adoption failed" popped up (see attached image) => tried with "retry" => no luck
I then gave the UFW-firewall config of the controller a closer look and found out that port 29814 wasn't in the accepted list.
Once added, the upgrade works - no problem.
Thank you for your time and patience.
Cheers - Will
.
