[Help]: Cant connect controller to the cloud

[goossensk]

Controller Version

v5.14.26.1

Describe Your Issue or Question

Did a site backup of a hardware controller and restored that into the docker software controller.
When now trying to connect this software controller to the omada cloud its showing "General error"

Expected Behavior

Connect the docker cloud controller to the omada cloud.

Steps to Reproduce

1. backup hardware controller with site migration
2. Restore site migration to the docker software controller
3. Try to connect the docker software controller to the omada cloud

How You're Launching the Container

Synology nas with portainer and the following docker compose file:

version: "3.1"

services:
  omadacontroller:
    container_name: omadacontroller
    image: mbentley/omada-controller
    restart: unless-stopped
    ulimits:
      nofile:
        soft: 4096
        hard: 8192
    stop_grace_period: 60s
    network_mode: host
    environment:
      - PUID=1026
      - PGID=100
      - MANAGE_HTTP_PORT=8088
      - MANAGE_HTTPS_PORT=8043
      - PORTAL_HTTP_PORT=8088
      - PORTAL_HTTPS_PORT=8843
      - PORT_APP_DISCOVERY=27001
      - PORT_ADOPT_V1=29812
      - PORT_UPGRADE_V1=29813
      - PORT_MANAGER_V1=29811
      - PORT_MANAGER_V2=29814
      - PORT_DISCOVERY=29810
      - PORT_TRANSFER_V2=29815
      - PORT_RTTY=29816
      - SHOW_SERVER_LOGS=true
      - SHOW_MONGODB_LOGS=false
      - TZ=Europe/Brussels
    volumes:
      - /volume2/docker/omada/data:/opt/tplink/EAPController/data
      - /volume2/docker/omada/logs:/opt/tplink/EAPController/logs

Container Logs

09-03-2024 21:17:23.032 INFO [Thread-6] [] c.t.e.c.c.q(): set connection status: CONNECTING
09-03-2024 21:17:23.239 WARN [http-nio-8088-exec-52] [] c.t.e.c.h.ApiHttpClient(): Failed to validate device.
09-03-2024 21:17:23.041 ERROR [http-nio-8088-exec-52] [] c.t.e.c.h.ApiHttpClient(): Device information from deviceMgmt is illegal.
09-03-2024 21:17:23.239 WARN [http-nio-8088-exec-52] [] c.t.s.o.c.p.b.d(): Request: checkDeviceBindStatus, cloud errorCode: -20104, msg: Parameter doesn't exist
09-03-2024 21:17:23.239 WARN [http-nio-8088-exec-52] [] c.t.s.o.c.a.b.a(): Unexpected cloud error: -20104
09-03-2024 21:17:23.239 WARN [http-nio-8088-exec-52] [] c.t.s.o.i.a.b.b.a(): Unexpected error when binding owner.
09-03-2024 21:17:23.255 WARN [Thread-6] [] c.t.e.c.c.e(): Request params from delegate is in invalid format.
09-03-2024 21:17:23.292 INFO [Thread-623] [] c.t.e.c.c.q(): 'recvThread' exception:java.net.SocketException: There is no more data because the end of the stream has been reached.
09-03-2024 21:17:23.292 INFO [Thread-623] [] c.t.e.c.c.q(): Thread 'recvThread' is stopped
09-03-2024 21:17:28.264 INFO [Thread-6] [] c.t.e.c.c.q(): set connection status: DISCONNECTED_NORMAL

MongoDB Logs

No response

Additional Context

No response

[mbentley]

I get a similar sort of error and have since November 2023:

09-03-2024 16:00:56.821 INFO [Thread-7] [] c.t.e.c.c.q(): set connection status: CONNECTING
09-03-2024 16:00:56.828 ERROR [https-jsse-nio-443-exec-3] [] c.t.e.c.h.ApiHttpClient(): Device information from deviceMgmt is illegal.
09-03-2024 16:00:56.874 WARN [https-jsse-nio-443-exec-3] [] c.t.e.c.h.ApiHttpClient(): Failed to validate device.
09-03-2024 16:00:56.874 WARN [https-jsse-nio-443-exec-3] [] c.t.s.o.c.p.b.d(): Request: checkDeviceBindStatus, cloud errorCode: -20104, msg: Parameter doesn't exist
09-03-2024 16:00:56.874 WARN [https-jsse-nio-443-exec-3] [] c.t.s.o.c.a.b.a(): Unexpected cloud error: -20104
09-03-2024 16:00:56.874 WARN [https-jsse-nio-443-exec-3] [] c.t.s.o.i.a.b.b.a(): Unexpected error when binding owner.
09-03-2024 16:00:57.010 WARN [Thread-7] [] c.t.e.c.c.e(): Request params from delegate is in invalid format.
09-03-2024 16:00:57.046 INFO [Thread-1777] [] c.t.e.c.c.q(): 'recvThread' exception:java.net.SocketException: There is no more data because the end of the stream has been reached.
09-03-2024 16:00:57.046 INFO [Thread-1777] [] c.t.e.c.c.q(): Thread 'recvThread' is stopped

I feel like it has something to do with some malformed or missing data, maybe something that was a part of a database migration at some point.

I created an issue on the TP-Link forums but it hasn't gone anywhere.