Controller self hosted: adopt failed
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi all,
I've setup the Omada Controller on my VPS (with Docker) and I've successfully adopted 4 AP about a year ago.
I'm now trying to adopt a new one, but damn it I can't!
I see the device in the discovery utility, it show it as "Pending". I insert the IP of my server (where all the ports are open: 8088, 8043, 8843, 29810/UDP, 29811, 29812, 29813, 29814), the username and password of the admin user; after about 5 seconds after I click on "Apply", it says "adopt failed" and in the controller log I don't see anything at all, it seems that the AP doesn't reach the controller.
There are not firewall problem, I can reach the controller to all the ports from the same network where the AP is.
The server hasn't been changed since I've installed and adopted the other AP, I've only updated it (now it's 5.12.7).
What's wrong? Am I forgetting something I should do?
Thanks!
