Unstable EAP225-outdoor after migrating from oc200 to software controller
I have an oc200 running 5.1.7 controller connected to 3 APs; EAP245 v3, a EAP225-outdoor, and a EAP650. All on latest firmware. The EAP245 and EAP650 are connected to a tp-link POE switch and the EAP225-outdoor is plugged into the supplied POE injector connected directly to a ER7208.
I have been running this setup for a long time and its been rock solid. I decided to migrated from the oc200 to the latest software controller (5.3.1) running on the latest Proxmox on a Ubuntu 20 container. I used the tp-link guide with JRE 11 and have no firewall running on the container. I followed the directions to set up the software controller and everything went smoothly.
I used the migration assistant to migrate to a new controller. As soon as I migrated, the eap225-outdoor showed up as disconnected but all the others migrated fine. Then it showed up as "owned by others". I was able to adopt it using the login/password I used on the old controller. Then for 2 days, the eap225-outdoor would show as disconnected on and off, and my nest cam would also go down. I also noticed a weird thing where the first time I would try and access the controller from the omada iOS app, the first time I would attempt to login it would always fail, but tapping try again would connect.
I gave up and migrated back to the oc200 and its been stable again.
Any ideas? Is something wrong with the controller 5.3.1 or was it something with my installation?