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.

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.
Controller self hosted: adopt failed
Controller self hosted: adopt failed
2023-10-05 17:04:16 - last edited 2023-11-30 06:53:28
Tags: #Installation #controller
Model: EAP245  
Hardware Version: V4
Firmware Version: 1.1.3 Build 20230224 Rel. 48254(4555)

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!

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:Controller self hosted: adopt failed-Solution
2023-11-29 09:49:32 - last edited 2023-11-30 06:53:28

I've found the problem: I was using the login credential created in the controller and not the ones of the AP.

But what the hell TP-Link, how is it possible to throw just the error "adopt failed" and not write "wrong credential"??? COME ON!!!

Recommended Solution
  0  
  0  
#6
Options
7 Reply
Re:Controller self hosted: adopt failed
2023-10-08 06:57:26

  @Preus Try resetting it and then adopting again?

  0  
  0  
#2
Options
Re:Controller self hosted: adopt failed
2023-10-08 07:20:33

  @dulu Thanks for the idea.

I've already did that numerous times, but the result is the same :(

  0  
  0  
#3
Options
Re:Controller self hosted: adopt failed
2023-10-08 08:43:14

  @Preus It seems that the firmware version of your EAP is not the latest. The latest firmware version is 1.2.0 Build 20230417. It is recommended to try again after updating the firmware version. I found two useful firmwares, the links are as follows:

https://community.tp-link.com/business/forum/topic/624076
https://www.tp-link.com/support/download/eap245/#Firmware

  0  
  0  
#4
Options
Re:Controller self hosted: adopt failed
2023-10-08 09:24:21 - last edited 2023-10-09 05:01:09

The problem with the latest firmware is that "Recommended Controller Software Version: Omada Controller v5.7 or above" while the latest docker container is 5.12.7 .

By the way, that couldn't be the problem since I've successfully paired 3 AP, one of which is the one that now doesn't want to pair again.

  0  
  0  
#5
Options
Re:Controller self hosted: adopt failed-Solution
2023-11-29 09:49:32 - last edited 2023-11-30 06:53:28

I've found the problem: I was using the login credential created in the controller and not the ones of the AP.

But what the hell TP-Link, how is it possible to throw just the error "adopt failed" and not write "wrong credential"??? COME ON!!!

Recommended Solution
  0  
  0  
#6
Options
Re:Controller self hosted: adopt failed
2023-11-30 06:53:10

  @Preus 

 

It's weird, it usually shows "Failed to adopt the EAP. The username or password is incorrect." on the controller. Maybe the error message is ignored by you.

Just striving to develop myself while helping others.
  0  
  0  
#7
Options
Re:Controller self hosted: adopt failed
2023-11-30 07:08:28 - last edited 2023-11-30 07:08:51

  @Virgo Negative. As I said and quoted, I just read "Adopt failed", NOTHING else.

  0  
  0  
#8
Options