[Help]: Omada controller stuck on adopting until i restart docker container. #562
-
Controller Version5.15.20.16 Describe the Bugafter restarting docker it works for a while then all of a sudden it shows all my devices down and in adopting mode. Expected BehaviorThis has never happen before all of my devices are online so i don't know why controller is trying to adopt them. Steps to ReproduceJust let the controller run How You're Launching the ContainerContainer LogsMongoDB LogsAdditional ContextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 33 replies
-
|
Hmm, someone reported something similar in #558. I will have to ask them to see if just a restart fixes it for them to see if maybe they were just misinterpreting the situation. |
Beta Was this translation helpful? Give feedback.
-
|
What device(s) are failing to adopt? What firmware is it currently running? |
Beta Was this translation helpful? Give feedback.
-
|
Im Running EAP660 HD(US) v2.0 EAP772(US) v1.0 SG2210MP v4.20 TL-SG2210MP v3.0 |
Beta Was this translation helpful? Give feedback.
-
|
what exact command should i run? docker inspect needs options i believe? |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
[
{
"ID": "pnbphw6y1askw2fmgzdql1h4u",
"Version": {
"Index": 1153937
},
"CreatedAt": "2025-03-31T18:58:24.670695318Z",
"UpdatedAt": "2025-05-08T08:29:10.599740459Z",
"Spec": {
"Name": "omada_app",
"Labels": {
"com.docker.stack.image": "mbentley/omada-controller:latest",
"com.docker.stack.namespace": "omada"
},
"TaskTemplate": {
"ContainerSpec": {
"Image": "mbentley/omada-controller:latest@sha256:186526049b9de1ac1eb21bb3069b3adba9aecf566148f05c2edd7bd60329cbaf",
"Labels": {
"com.docker.stack.namespace": "omada"
},
"Env": [
"MANAGE_HTTPS_PORT=8043",
"MANAGE_HTTP_PORT=8088",
"PGID=508",
"PORTAL_HTTPS_PORT=8843",
"PORTAL_HTTP_PORT=8088",
"PORT_ADOPT_V1=29812",
"PORT_APP_DISCOVERY=27001",
"PORT_DISCOVERY=29810",
"PORT_MANAGER_V1=29811",
"PORT_MANAGER_V2=29814",
"PORT_RTTY=29816",
"PORT_TRANSFER_V2=29815",
"PORT_UPGRADE_V1=29813",
"PUID=508",
"SHOW_MONGODB_LOGS=false",
"SHOW_SERVER_LOGS=true",
"SSL_CERT_NAME=tls.crt",
"SSL_KEY_NAME=tls.key",
"TZ=America/New_York"
],
"Privileges": {
"CredentialSpec": null,
"SELinuxContext": null,
"NoNewPrivileges": false
},
"Mounts": [
{
"Type": "bind",
"Source": "/etc/localtime",
"Target": "/etc/localtime",
"ReadOnly": true
},
{
"Type": "volume",
"Source": "omada_omada-data",
"Target": "/opt/tplink/EAPController/data",
"VolumeOptions": {
"Labels": {
"com.docker.stack.namespace": "omada"
},
"DriverConfig": {
"Name": "local",
"Options": {
"device": ":/mnt/marsSSD/Docker-Volumes/Omada/omada-data/_data/",
"o": "addr=10.10.1.20,soft,rw",
"type": "nfs"
}
}
}
},
{
"Type": "volume",
"Source": "omada_omada-logs",
"Target": "/opt/tplink/EAPController/logs",
"VolumeOptions": {
"Labels": {
"com.docker.stack.namespace": "omada"
},
"DriverConfig": {
"Name": "local",
"Options": {
"device": ":/mnt/marsSSD/Docker-Volumes/Omada/omada-logs/_data/",
"o": "addr=10.10.1.20,soft,rw",
"type": "nfs"
}
}
}
}
],
"StopGracePeriod": 60000000000,
"DNSConfig": {},
"Isolation": "default",
"Ulimits": [
{
"Name": "nofile",
"Hard": 8192,
"Soft": 4096
}
]
},
"Resources": {},
"RestartPolicy": {
"Condition": "any",
"Delay": 5000000000,
"MaxAttempts": 0
},
"Placement": {
"Constraints": [
"node.labels.netservers == true"
],
"Platforms": [
{
"Architecture": "amd64",
"OS": "linux"
},
{
"Architecture": "arm64",
"OS": "linux"
},
{
"OS": "linux"
}
]
},
"Networks": [
{
"Target": "jpxxeueb3hsirku5uw3xa5513",
"Aliases": [
"app"
]
}
],
"ForceUpdate": 1,
"Runtime": "container"
},
"Mode": {
"Replicated": {
"Replicas": 1
}
},
"UpdateConfig": {
"Parallelism": 1,
"FailureAction": "pause",
"Monitor": 5000000000,
"MaxFailureRatio": 0,
"Order": "stop-first"
},
"RollbackConfig": {
"Parallelism": 1,
"FailureAction": "pause",
"Monitor": 5000000000,
"MaxFailureRatio": 0,
"Order": "stop-first"
},
"EndpointSpec": {
"Mode": "vip",
"Ports": [
{
"Protocol": "tcp",
"TargetPort": 8043,
"PublishedPort": 8043,
"PublishMode": "ingress"
},
{
"Protocol": "tcp",
"TargetPort": 8088,
"PublishedPort": 8088,
"PublishMode": "ingress"
},
{
"Protocol": "tcp",
"TargetPort": 8843,
"PublishedPort": 8843,
"PublishMode": "ingress"
},
{
"Protocol": "udp",
"TargetPort": 27001,
"PublishedPort": 27001,
"PublishMode": "ingress"
},
{
"Protocol": "udp",
"TargetPort": 29810,
"PublishedPort": 29810,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29811,
"PublishedPort": 29811,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29812,
"PublishedPort": 29812,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29813,
"PublishedPort": 29813,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29814,
"PublishedPort": 29814,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29815,
"PublishedPort": 29815,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29816,
"PublishedPort": 29816,
"PublishMode": "host"
}
]
}
},
"PreviousSpec": {
"Name": "omada_app",
"Labels": {
"com.docker.stack.image": "mbentley/omada-controller:latest",
"com.docker.stack.namespace": "omada"
},
"TaskTemplate": {
"ContainerSpec": {
"Image": "mbentley/omada-controller:latest@sha256:6da75b05abdc503998e6616de27205c0a1fbbea72247d64e65756cf4e7dffc0b",
"Labels": {
"com.docker.stack.namespace": "omada"
},
"Env": [
"MANAGE_HTTPS_PORT=8043",
"MANAGE_HTTP_PORT=8088",
"PGID=508",
"PORTAL_HTTPS_PORT=8843",
"PORTAL_HTTP_PORT=8088",
"PORT_ADOPT_V1=29812",
"PORT_APP_DISCOVERY=27001",
"PORT_DISCOVERY=29810",
"PORT_MANAGER_V1=29811",
"PORT_MANAGER_V2=29814",
"PORT_RTTY=29816",
"PORT_TRANSFER_V2=29815",
"PORT_UPGRADE_V1=29813",
"PUID=508",
"SHOW_MONGODB_LOGS=false",
"SHOW_SERVER_LOGS=true",
"SSL_CERT_NAME=tls.crt",
"SSL_KEY_NAME=tls.key",
"TZ=America/New_York"
],
"Privileges": {
"CredentialSpec": null,
"SELinuxContext": null,
"NoNewPrivileges": false
},
"Mounts": [
{
"Type": "bind",
"Source": "/etc/localtime",
"Target": "/etc/localtime",
"ReadOnly": true
},
{
"Type": "volume",
"Source": "omada_omada-data",
"Target": "/opt/tplink/EAPController/data",
"VolumeOptions": {
"Labels": {
"com.docker.stack.namespace": "omada"
},
"DriverConfig": {
"Name": "local",
"Options": {
"device": ":/mnt/marsSSD/Docker-Volumes/Omada/omada-data/_data/",
"o": "addr=10.10.1.20,soft,rw",
"type": "nfs"
}
}
}
},
{
"Type": "volume",
"Source": "omada_omada-logs",
"Target": "/opt/tplink/EAPController/logs",
"VolumeOptions": {
"Labels": {
"com.docker.stack.namespace": "omada"
},
"DriverConfig": {
"Name": "local",
"Options": {
"device": ":/mnt/marsSSD/Docker-Volumes/Omada/omada-logs/_data/",
"o": "addr=10.10.1.20,soft,rw",
"type": "nfs"
}
}
}
}
],
"StopGracePeriod": 60000000000,
"Isolation": "default",
"Ulimits": [
{
"Name": "nofile",
"Hard": 8192,
"Soft": 4096
}
]
},
"Resources": {},
"RestartPolicy": {
"Condition": "any",
"MaxAttempts": 0
},
"Placement": {
"Constraints": [
"node.labels.netservers == true"
],
"Platforms": [
{
"Architecture": "amd64",
"OS": "linux"
},
{
"Architecture": "arm64",
"OS": "linux"
},
{
"OS": "linux"
}
]
},
"Networks": [
{
"Target": "jpxxeueb3hsirku5uw3xa5513",
"Aliases": [
"app"
]
}
],
"ForceUpdate": 1,
"Runtime": "container"
},
"Mode": {
"Replicated": {
"Replicas": 1
}
},
"EndpointSpec": {
"Mode": "vip",
"Ports": [
{
"Protocol": "tcp",
"TargetPort": 8043,
"PublishedPort": 8043,
"PublishMode": "ingress"
},
{
"Protocol": "tcp",
"TargetPort": 8088,
"PublishedPort": 8088,
"PublishMode": "ingress"
},
{
"Protocol": "tcp",
"TargetPort": 8843,
"PublishedPort": 8843,
"PublishMode": "ingress"
},
{
"Protocol": "udp",
"TargetPort": 27001,
"PublishedPort": 27001,
"PublishMode": "ingress"
},
{
"Protocol": "udp",
"TargetPort": 29810,
"PublishedPort": 29810,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29811,
"PublishedPort": 29811,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29812,
"PublishedPort": 29812,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29813,
"PublishedPort": 29813,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29814,
"PublishedPort": 29814,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29815,
"PublishedPort": 29815,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29816,
"PublishedPort": 29816,
"PublishMode": "host"
}
]
}
},
"Endpoint": {
"Spec": {
"Mode": "vip",
"Ports": [
{
"Protocol": "tcp",
"TargetPort": 8043,
"PublishedPort": 8043,
"PublishMode": "ingress"
},
{
"Protocol": "tcp",
"TargetPort": 8088,
"PublishedPort": 8088,
"PublishMode": "ingress"
},
{
"Protocol": "tcp",
"TargetPort": 8843,
"PublishedPort": 8843,
"PublishMode": "ingress"
},
{
"Protocol": "udp",
"TargetPort": 27001,
"PublishedPort": 27001,
"PublishMode": "ingress"
},
{
"Protocol": "udp",
"TargetPort": 29810,
"PublishedPort": 29810,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29811,
"PublishedPort": 29811,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29812,
"PublishedPort": 29812,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29813,
"PublishedPort": 29813,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29814,
"PublishedPort": 29814,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29815,
"PublishedPort": 29815,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29816,
"PublishedPort": 29816,
"PublishMode": "host"
}
]
},
"Ports": [
{
"Protocol": "tcp",
"TargetPort": 8043,
"PublishedPort": 8043,
"PublishMode": "ingress"
},
{
"Protocol": "tcp",
"TargetPort": 8088,
"PublishedPort": 8088,
"PublishMode": "ingress"
},
{
"Protocol": "tcp",
"TargetPort": 8843,
"PublishedPort": 8843,
"PublishMode": "ingress"
},
{
"Protocol": "udp",
"TargetPort": 27001,
"PublishedPort": 27001,
"PublishMode": "ingress"
},
{
"Protocol": "udp",
"TargetPort": 29810,
"PublishedPort": 29810,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29811,
"PublishedPort": 29811,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29812,
"PublishedPort": 29812,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29813,
"PublishedPort": 29813,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29814,
"PublishedPort": 29814,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29815,
"PublishedPort": 29815,
"PublishMode": "host"
},
{
"Protocol": "tcp",
"TargetPort": 29816,
"PublishedPort": 29816,
"PublishMode": "host"
}
],
"VirtualIPs": [
{
"NetworkID": "gp3qj9zjpwr29ew5o9huxiwqz",
"Addr": "10.0.0.122/24"
},
{
"NetworkID": "jpxxeueb3hsirku5uw3xa5513",
"Addr": "10.0.13.2/24"
}
]
},
"UpdateStatus": {
"State": "completed",
"StartedAt": "2025-05-08T08:26:57.441986304Z",
"CompletedAt": "2025-05-08T08:29:10.599582319Z",
"Message": "update completed"
}
}
] |
Beta Was this translation helpful? Give feedback.
-
|
Also, someone was working with support and they said they were told to do the following:
Could you try that and see if that helps the switch? I am not sure if the EAPs have the same capability of being able to manually set the inform URL. |
Beta Was this translation helpful? Give feedback.
-
|
Could you also try to add 19810/udp to your ports to see if that makes a difference? |
Beta Was this translation helpful? Give feedback.
-
|
I updated the README and known issues in #579 with details with that FAQ about needing to set the controller inform URL. Port 19810/udp is definitely required though. |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, Here is my configuration: Device Adoption Issues Next, I changed the device's port to 19810, but the adoption still failed. Below is the second log excerpt showing the new attempt:
|
Beta Was this translation helpful? Give feedback.
-
|
Not sure if this is related but you'll want to update your compose to include additional ports as there have been more ports added related to adoption from 29811 to 29816: |
Beta Was this translation helpful? Give feedback.
-
|
Yes, but tomorrow. :) |
Beta Was this translation helpful? Give feedback.
-
|
So I have been experimenting with this in a lab type environment - in my EAP, the syntax of the controller's inform URL was very odd but I was able to get it working in bridge mode. I will have to grab it because it didn't work when I only specified an IP or hostname - it seemed to need the full thing so I will have to experiment a bit more. In host mode, it's able to determine the IP or hostname of the controller so it works without needing it specified. Basically, you have to follow the https://www.tp-link.com/us/support/faq/3087/ "layer 3" adoption process. |
Beta Was this translation helpful? Give feedback.
-
|
Update: I managed to successfully adopt my EAP device into the Omada controller. Here's what I did: It looks like the container needs to receive UDP broadcast packets (e.g. on port 29810), which the EAP sends during discovery.
|
Beta Was this translation helpful? Give feedback.
-
|
Quick note for anyone testing controller restarts: After successful adoption, provisioning and configuration, EAP devices operate independently. The Omada controller is only required for config pushes, stats/logs collection, and firmware management. Wi-Fi networks remain fully functional even if the controller is offline — clients stay connected, and roaming works as expected. |
Beta Was this translation helpful? Give feedback.
-
|
I assume this only is valid for LAN connected devices. When using MESH and WiFi connected EAP devices such as outdoor, this is not valid. The MESH function relies on the controller. |
Beta Was this translation helpful? Give feedback.
-
|
You're absolutely right — I apologize. Once again, I apologize for the confusion and for providing incorrect information earlier. |
Beta Was this translation helpful? Give feedback.
-
|
I'd like to add to this. So I was having the same issue of Adopting my EAP620HD the first time. What worked: Setting up the IP address of the controller in the EAP Settings page. I was able to get a "Connected" status of the EAP afterwards. Issue now: After a few days, I went back to Omada Controller to update something, now the EAP is back to "Adopting" My question is: Are yours still "Connected" up to now? It seems that it's failing back to "Adopting" even after a successful adopt. What I tried:
EDIT: Here's my compose. I'm not using 'host' network mode, but I'm guessing it's not a factor since I was able to adopt the EAP successfully. |
Beta Was this translation helpful? Give feedback.
-
|
just an update.
Here's the relevant logs. It shows that it gets to Configuring state, then it becomes "CONNECTED_ERROR", this is when it's stuck in "Adopting" state in the controller. in controller, both my EAPs are configured but went back to Adopting: 
Now the current logs just show this multiple times on loop: |
Beta Was this translation helpful? Give feedback.
-
|
I am using docker image in bridge mode and i am also not able to adopt my eaps 245 even if i restart docker or the eaps |
Beta Was this translation helpful? Give feedback.
-
|
is it also stuck in Adopting state? |
Beta Was this translation helpful? Give feedback.
-
|
yes i use the yaml example regarding ports that need to be open in bridge mode without success... after that i went to each eap 245 v3 one by one reset them and after the initial setup (only password and user configuration) go to system controller and changed the controller url from the one that was there 0.0.0.0longstuff to 192.168.1.45longstuff and them i was able to adopt them |
Beta Was this translation helpful? Give feedback.
-
|
Does it stay at CONNECTED state? I was able to adopt too but it went from CONFIGURING to ADOPTING again |
Beta Was this translation helpful? Give feedback.
-
|
Yeah connected even after restart docker or aps. But now if my host machine change ip probably i Will have a problem. This have to me something related with new versions |
Beta Was this translation helpful? Give feedback.
-
|
Yeah it stays |
Beta Was this translation helpful? Give feedback.
Also, someone was working with support and they said they were told to do the following:
Could you try that and see if that helps the switch? I am not sure if the EAPs have the same capability of being able to manually set the inform URL.