[Help]: sudden disconnected Router and WAN ports

[kimbo1st]

Controller Version

5.15.24.19

Describe Your Issue or Question

Since 8th of August I'm getting issues that my internet is stalled/disconnected.
When I check in the controller my ER605 seems to be disconnected. Physical check indicates that it is up and running. Can login to the device itself and seems to be fine.

In the controller it shows disconnected state on 8/aug at

• 0:34 - I was asleep started to check in the morning
• 9:02 - some analysis done and restarted the router
• 16:23 - back down, new analysis and reboot
• 19:06 - again down - saw old version of the controller and no idea why I didnt get the new image (tag was none so should be latest). Downloaded en reinstalled new container and it used the existing settings and db.

On 11/aug today it went again down, controller was hard to log in and I was required to reboot it. Before I checked the NAS resources and these were fine. So after the reboot the router was connected, but WAN port and USB 4G were both disconnected. No errors in the controller, only showing ROUTER was disconnected around 14:16.
I was was able to manually reconnect the WAN port and internet came backup up. The 4G backup want to connect, no error or so.

Wonder what the issue can be and hope someone can help me to figure this out and solve. I work a lot from home and rely on my internet connection. Thanks

Expected Behavior

Stay stable or recover

Steps to Reproduce

Cannot be reproduced, it just happens suddenly.

How You're Launching the Container

docker run -d --name=omada-controller-main \
-e PUID=1026 \
-e PGID=100 \
-e TZ=Europe/Bucharest \
-e MANAGE_HTTP_PORT=8088 \
-e MANAGE_HTTPS_PORT=8043 \
-e PORTAL_HTTP_PORT=8088 \
-e PORTAL_HTTPS_PORT=8043 \
-e SHOW_SERVER_LOGS=true \
-e SHOW_MONGODB_LOGS=false \
-e SSL_CERT_NAME="tls.crt" \
-e SSL_KEY_NAME="tls.key" \
-v /volume1/docker/omada/data:/opt/tplink/EAPController/data \
-v /volume1/docker/omada/logs:/opt/tplink/EAPController/logs \
-v /volume1/docker/omada/work:/opt/tplink/EAPController/work \
--net host \
--restart always \
mbentley/omada-controller:latest

Container Logs

date	stream	content
2025/08/11 19:20:23	stdout	08-11-2025 20:20:23.595 INFO [https-jsse-nio-8043-exec-5] [] c.t.s.o.m.t.b.a.e(): device rtty not connected, send terminal setting to: ANZzLDVrFUbVaMDuav10rxOlgqP4b0bVa+N0FpT+96Q=, TerminalSetting(enable=true, token=e42c290bae1e433dbdfae256728e70e3, port=29816, heartbeatFrequency=10, ssl=SSL(enable=true))
2025/08/11 14:13:44	stdout	08-11-2025 15:13:44.986 INFO [Thread-15] [] c.t.e.c.c.q(): Thread 'heartBeatThread' is stopped
2025/08/11 14:13:44	stdout	08-11-2025 15:13:44.971 INFO [Thread-15] [] c.t.e.c.c.q(): unsuccessful heartbeat response: {"error_code":-20002}
2025/08/11 14:13:34	stdout	08-11-2025 15:13:34.959 WARN [Thread-15] [] c.t.e.c.c.q(): send heartbeat getting timeout response: {"error_code":-20002}
2025/08/11 14:13:24	stdout	08-11-2025 15:13:24.948 WARN [Thread-15] [] c.t.e.c.c.q(): send heartbeat getting timeout response: {"error_code":-20002}
2025/08/11 14:12:41	stdout	08-11-2025 15:12:41.855 INFO [device-timeout-workgroup-2] [] c.t.s.o.m.d.d.m.j.b(): Device DeviceMac(ANZzLDVrFUbVaMDuav10rxOlgqP4b0bVa+N0FpT+96Q=) omadacId OmadacId(4aab22f9e76a3f4cfc810f4fb526def6) status change from Connected to Heartbeat Missed
2025/08/09 20:04:55	stdout	08-09-2025 21:04:55.253 INFO [device-timeout-workgroup-1] [] c.t.s.o.m.d.d.m.j.b(): Device DeviceMac(ANZzLDVrFUbVaMDuav10rxOlgqP4b0bVa+N0FpT+96Q=) omadacId OmadacId(4aab22f9e76a3f4cfc810f4fb526def6) status change from Connected to Heartbeat Missed
2025/08/09 08:04:54	stdout	08-09-2025 09:04:54.389 INFO [device-timeout-workgroup-0] [] c.t.s.o.m.d.d.m.j.b(): Device DeviceMac(ANZzLDVrFUbVaMDuav10rxOlgqP4b0bVa+N0FpT+96Q=) omadacId OmadacId(4aab22f9e76a3f4cfc810f4fb526def6) status change from Connected to Heartbeat Missed

MongoDB Logs

No response

Additional Context

Synology DS720+
Intel Celeron J4125 2 Ghz
RAM 10GB

[mbentley]

Is your ER605 running the latest available firmware? Seems like the TP-Link routers are one of the devices that I see the most people having trouble with when it comes to the controller software and disconnects, especially where they do not fail gracefully when unable to connect to the controller and can take down the WAN.

Do you know when the controller upgraded to 5.15.24.19? Do you have a tool to update your images automatically? I released it on the 2nd but if you had something like watchtower to update the image, it would have likely happened a lot sooner than the 8th. Was just curious if you had upgraded around then or not.

When it comes to problems with the controller itself, there is little I can do to debug since I only control the packaging and containerization of the controller as the maintainer of this repo and image. I would suggest either filing a support case with TP-Link or submitting a forum post.

[kimbo1st]

The version seems to be the latest one one the controller: 2.3.0 Build 20250428 Rel.18967
Now it suddenly wants to adopt the router/gateway again... it is strange and it also changes the password to the one of my main account and then the adoption fails. So wondering why it loses the device?

I already sent a mail to TP Link for support and planning to post also on the forum.

Does the log files indicate something? It has a lot of logs like these;

08-11-2025 22:47:55.333 INFO [client-inform-work-group-1] [] c.t.s.o.c.p.c.k(): com.tplink.smb.omada.client.port.cache.k$b: Lan network does not exist, OmadacId: 4aab22f9e76a3f4cfc810f4fb526def6, SiteId: 6727da3a0edd023cb8a15e27, vid:0 | stdout
11-08-2025 21:47 | 08-11-2025 22:47:25.265 INFO [client-inform-work-group-1] [] c.t.s.o.c.p.c.k(): com.tplink.smb.omada.client.port.cache.k$b: Lan network does not exist, OmadacId: 4aab22f9e76a3f4cfc810f4fb526def6, SiteId: 6727da3a0edd023cb8a15e27, vid:0 | stdout
11-08-2025 21:46 | 08-11-2025 22:46:55.197 INFO [client-inform-work-group-1] [] c.t.s.o.c.p.c.k(): com.tplink.smb.omada.client.port.cache.k$b: Lan network does not exist, OmadacId: 4aab22f9e76a3f4cfc810f4fb526def6, SiteId: 6727da3a0edd023cb8a15e27, vid:0 | stdout
11-08-2025 21:46 | 08-11-2025 22:46:27.047 INFO [device-timeout-workgroup-1] [] c.t.s.o.m.d.a.a.a(): OmadacId OmadacId(4aab22f9e76a3f4cfc810f4fb526def6) Device DeviceMac(ANZzLDVrFUbVaMDuav10rxOlgqP4b0bVa+N0FpT+96Q=) is AdoptSuccessTimeout. | stdout
11-08-2025 21:46 | 08-11-2025 22:46:27.047 INFO [device-timeout-workgroup-1] [] c.t.s.o.m.d.d.m.j.b(): timeoutWiredAdopting ,OmadacId OmadacId(4aab22f9e76a3f4cfc810f4fb526def6) Device DeviceMac(ANZzLDVrFUbVaMDuav10rxOlgqP4b0bVa+N0FpT+96Q=). | stdout
11-08-2025 21:46 | 08-11-2025 22:46:25.138 INFO [client-inform-work-group-0] [] c.t.s.o.c.p.c.k(): com.tplink.smb.omada.client.port.cache.k$b: Lan network does not exist, OmadacId: 4aab22f9e76a3f4cfc810f4fb526def6, SiteId: 6727da3a0edd023cb8a15e27, vid:0 | stdout
11-08-2025 21:45 | 08-11-2025 22:45:55.063 INFO [client-inform-work-group-0] [] c.t.s.o.c.p.c.k(): com.tplink.smb.omada.client.port.cache.k$b: Lan network does not exist, OmadacId: 4aab22f9e76a3f4cfc810f4fb526def6, SiteId: 6727da3a0edd023cb8a15e27, vid:0 | stdout
11-08-2025 21:45 | 08-11-2025 22:45:53.939 INFO [client-inform-work-group-3] [] c.t.s.o.c.d.a.A(): Known wireless client 8B1xjgkCTUaLIADSbUiR96XdYIod3tL0jj6CxWMRmz4= is informed by switch: 2SyEkl8cQW2x7QZO1EwPB9SEuiveI9QfMqkm4yR4DZA=, omadac: 4aab22f9e76a3f4cfc810f4fb526def6, site: 6727da3a0edd023cb8a15e27, handle as wired client now. | stdout
11-08-2025 21:45 | 08-11-2025 22:45:29.180 INFO [comm-pool-15] [] c.t.s.o.m.d.a.u.f.d(): no omadac need handle target firmware upgrade | stdout
11-08-2025 21:45 | 08-11-2025 22:45:29.179 INFO [comm-pool-15] [] c.t.s.o.m.d.a.u.f.d(): Target firmware check task run | stdout
11-08-2025 21:45 | 08-11-2025 22:45:24.762 INFO [client-inform-work-group-0] [] c.t.s.o.c.p.c.k(): com.tplink.smb.omada.client.port.cache.k$b: Lan network does not exist, OmadacId: 4aab22f9e76a3f4cfc810f4fb526def6, SiteId: 6727da3a0edd023cb8a15e27, vid:0 | stdout
11-08-2025 21:45 | 08-11-2025 22:45:17.978 INFO [server-comm-pool-2] [] c.t.s.e.s.c.h.EcspV2DeviceContextHelper(): device of status ADOPTING_PENDING_PRE_ADOPT time out for 60-83-E7-42-3B-56 | stdout
11-08-2025 21:44 | 08-11-2025 22:44:54.696 INFO [client-inform-work-group-0] [] c.t.s.o.c.p.c.k(): com.tplink.smb.omada.client.port.cache.k$b: Lan network does not exist, OmadacId: 4aab22f9e76a3f4cfc810f4fb526def6, SiteId: 6727da3a0edd023cb8a15e27, vid:0 | stdout
11-08-2025 21:44 | 08-11-2025 22:44:33.770 INFO [discovery-work-group-0] [] c.t.s.o.m.d.d.m.e.a(): OmadacId(4aab22f9e76a3f4cfc810f4fb526def6) DeviceMac(ANZzLDVrFUbVaMDuav10rxOlgqP4b0bVa+N0FpT+96Q=) receive discovery when adopting, times[3] reach limit, set adopt fail | stdout
11-08-2025 21:44 | 08-11-2025 22:44:24.626 INFO [client-inform-work-group-0] [] c.t.s.o.c.p.c.k(): com.tplink.smb.omada.client.port.cache.k$b: Lan network does not exist, OmadacId: 4aab22f9e76a3f4cfc810f4fb526def6, SiteId: 6727da3a0edd023cb8a15e27, vid:0 | stdout
11-08-2025 21:43 | 08-11-2025 22:43:54.547 INFO [client-inform-work-group-0] [] c.t.s.o.c.p.c.k(): com.tplink.smb.omada.client.port.cache.k$b: Lan network does not exist, OmadacId: 4aab22f9e76a3f4cfc810f4fb526def6, SiteId: 6727da3a0edd023cb8a15e27, vid:0 | stdout
11-08-2025 21:43 |