[Help]: Router/Gateway (ER605) statistics timeout after v6 upgrade

[jehe79]

Controller Version

v6.1.0.19

Describe Your Issue or Question

After upgrading to v6 (MongoDB Upgrade Container way) controller is up and running and network is working as expected.
When trying to open the gateway settings (Site > Devices > Gateway) sidebar opens but an error message is shown. Switch and AP sidebars working fine.

I've tried:

• Restarting container
• Restarting gateway/router
• Removing and re-deploying container
• Upgrade firmware on router
• Setting up new volumes and deploying a fresh Controller restoring v.5.15 backup

No success.

Running docker image in Ubuntu 24.04 over Proxmox (with type=host for avx instr)

Not tried yet:

• Factory reset on router

Expected Behavior

Expected is a populated sidebar with ability to read statistics and change settings for the router/gateway.

Steps to Reproduce

Not sure if its reproduceable for anyone else since I don't know why it's happening.

How You're Launching the Container

docker run -d   --name omada-controller-clean   --restart unless-stopped   --ulimit nofile=4096:8192   -p 8088:8088   -p 8043:8043   -p 8843:8843   -p 27001:27001/udp   -p 29810:29810/udp   -p 29811-29816:29811-29816   -p 29817:29817   -e MANAGE_HTTP_PORT=8088   -e MANAGE_HTTPS_PORT=8043   -e PGID="508"   -e PORTAL_HTTP_PORT=8088   -e PORTAL_HTTPS_PORT=8843   -e PORT_ADOPT_V1=29812   -e PORT_APP_DISCOVERY=27001   -e PORT_DISCOVERY=29810   -e PORT_MANAGER_V1=29811   -e PORT_MANAGER_V2=29814   -e PORT_TRANSFER_V2=29815   -e PORT_RTTY=29816   -e PORT_UPGRADE_V1=29813   -e PUID="508"   -e SHOW_SERVER_LOGS=true   -e SHOW_MONGODB_LOGS=false   -e SSL_CERT_NAME="tls.crt"   -e SSL_KEY_NAME="tls.key"   -e TZ=Europe/Stockholm   -v omada-data-clean:/opt/tplink/EAPController/data   -v omada-logs-clean:/opt/tplink/EAPController/logs   mbentley/omada-controller:6.1

Container Logs

xxx

MongoDB Logs

No response

Additional Context

No response

[jehe79]

Seems like ER605 V2.0 is not supported by v6. Only V2.2.

Rolled back to v5 and it started working again. :(