[Bug]: OMADA BETA 6.3.0.36 BUG IN DEVICE ->MANAGED DEVICE->SWITCH->NETWORK VIEW->ROUTING TABLE SECTION IS BLANK COMPLETELY

[Kunalb963]

Controller Version

6.3.0.36

Describe the Bug

[Bug]: OMADA BETA 6.3.0.36 BUG IN DEVICE ->MANAGED DEVICE->SWITCH->NETWORK VIEW->ROUTING TABLE SECTION IS BLANK COMPLETELY. ON ALL SWITCHES MISSING. BUT WORKING FINE ON WINDOWS BETA 6.3.0.36.
EVEN AFTER SEVERAL FRESH INSTALL ITS BLANK NO ROUTING TABLE. SO I SHIFTED TO WINDOWS BETA VERSION. DUE TO THIS FACEING INTERNET ISSUE, TOPOLOGY ISSUE AND WHILE CLICKING ON ANY CLIENT IT SHOWS "CLIENT DOES NOT EXIST".

Expected Behavior

ALL IMAGES HERE ARE FROM WINDOWS OMADA BETA 6.3.0.36.

ABOVE SECTION IS BLANK COMPLETELY.

ABOVE SECTION AT RIGHT MOST SIDE: CLIENT/DEVICE DOES NOT EXIST. IN PLACE OF SINGLE DEVICE DETAIL.

Steps to Reproduce

NA

omada-controller.html

How You're Launching the Container

version: "3.1"
services:
   mongodb:
    container_name: mongodb
    image: mongo:4.4.6
    restart: always
    #ports:
      #- 27017:27017
    environment:
      - MONGO_INITDB_ROOT_USERNAME=admin
      - MONGO_INITDB_ROOT_PASSWORD=0m4d4
      - MONGO_INITDB_DATABASE=omada
    volumes:
      - /volume1/docker/omada/mongodb/config:/data/configdb
      - /volume1/docker/omada/mongodb/data:/data/db
    networks:
      #lancache:
        #ipv4_address: 192.168.0.160
      omada-bridge: 
        ipv4_address: 172.19.0.6

   omada-controller:
    container_name: omada-controller
    image: mbentley/omada-controller:beta-6.3
    mem_limit: 2g
    memswap_limit: 3g
    cpu_shares: 2048
    restart: always
    ulimits:
      nofile:
        soft: 4096
        hard: 8192
    stop_grace_period: 60s
    networks:
      omada-bridge: 
        ipv4_address: 172.19.0.2        # PRIMARY → GUI + Reverse Proxy
      lancache:         # SECONDARY → LAN discovery
        ipv4_address: 192.168.0.149
    ports:
      - 8088:8088
      - 8043:8043
      - 8843:8843
      - 19810:19810/udp
      - 27001:27001/udp
      - 29810:29810/udp
      - 29811-29817:29811-29817
    environment:
      - PUID=1026
      - PGID=100
      - JAVA_MAX_HEAP_SIZE=1024m
      - JAVA_MIN_HEAP_SIZE=128m
      - MONGOD_EXTRA_ARGS=--wiredTigerCacheSizeGB 0.50
      - MONGO_EXTERNAL=true

      # ✅ ADDED — Correct full MongoDB URI (your old one was incomplete)
      - EAP_MONGOD_URI=mongodb://admin:0m4d4@172.19.0.6:27017/omada?authSource=admin

      - MANAGE_HTTP_PORT=8088
      - MANAGE_HTTPS_PORT=8043
      - PORTAL_HTTP_PORT=8088
      - PORTAL_HTTPS_PORT=8843
      - UPGRADE_HTTPS_PORT=8043
      - PORT_APP_DISCOVERY=27001
      - PORT_DISCOVERY=29810
      - PORT_MANAGER_V1=29811
      - PORT_ADOPT_V1=29812
      - PORT_UPGRADE_V1=29813
      - PORT_MANAGER_V2=29814
      - PORT_TRANSFER_V2=29815
      - PORT_RTTY=29816
      - PORT_DEVICE_MONITOR=29817
      - WEB_CONFIG_OVERRIDE=true
      - SHOW_SERVER_LOGS=true
      - SHOW_MONGODB_LOGS=false
      - SSL_CERT_NAME=tls.crt
      - SSL_KEY_NAME=tls.key
      - TZ=Asia/Kolkata

      # ✅ ADDED — Spring Boot tuning (APPLICATION_PROPERTIES)
      #- APPLICATION_PROPERTIES=|
         # server.tomcat.threads.max=50
         # server.tomcat.threads.min-spare=5
         # spring.task.execution.pool.core-size=5
         # spring.task.execution.pool.max-size=20
         # spring.task.execution.pool.queue-capacity=100
        #  spring.task.scheduling.pool.size=2
         # logging.level.root=WARN
         # logging.level.com.tplink=INFO

    volumes:
      - /volume1/docker/omada/data:/opt/tplink/EAPController/data
      - /volume1/docker/omada/logs:/opt/tplink/EAPController/logs
      #- /volume3/docker/omada/properties:/opt/tplink/EAPController/properties

volumes:
   omada-mongo-config: null
   omada-mongo-data: null
   omada-init-scripts: null
   omada-data: null
   omada-logs: null

networks:
  omada-bridge:
    external: true
  lancache:
    external: true

Container Logs

UPLOADED FILE ABOVE.[omada-controller.html](https://github.com/user-attachments/files/30620404/omada-controller.html)

MongoDB Logs

Additional Context

No response

[mbentley]

I would be surprised if this is an issue with the container packaging. When you try to load those pages, do you get an errors in the browser developer tools? For example, any script errors or anything? It would be interesting to compare against what you see in the Windows version. Regardless, this is probably something that TP-Link needs to look into and address so I'd report it on the beta forums thread or through support (links to those). I don't run the beta version on my home network so there is limited testing I can do and I currently don't have my test set up deployed to do any checks (plus my test network only has a few old APs - I don't have any managed switches to actually do testing).

[Kunalb963]

I would be surprised if this is an issue with the container packaging. When you try to load those pages, do you get an errors in the browser developer tools? For example, any script errors or anything? It would be interesting to compare against what you see in the Windows version. Regardless, this is probably something that TP-Link needs to look into and address so I'd report it on the beta forums thread or through support (links to those). I don't run the beta version on my home network so there is limited testing I can do and I currently don't have my test set up deployed to do any checks (plus my test network only has a few old APs - I don't have any managed switches to actually do testing).

totally blank and shows: "client does not exist"

blank shows no routing tables.

[Kunalb963]

i will shift all my switches to docker version in synology and i will send the screenshots. below

[Kunalb963]

ok i will try most probably tomorrow(3rd aug) i will shift all my switches to docker version in synology and i will send the screenshots. need some time may take atleast 2days

I would be surprised if this is an issue with the container packaging. When you try to load those pages, do you get an errors in the browser developer tools? For example, any script errors or anything? It would be interesting to compare against what you see in the Windows version. Regardless, this is probably something that TP-Link needs to look into and address so I'd report it on the beta forums thread or through support (links to those). I don't run the beta version on my home network so there is limited testing I can do and I currently don't have my test set up deployed to do any checks (plus my test network only has a few old APs - I don't have any managed switches to actually do testing).

totally blank and shows: "client does not exist"

blank shows no routing tables.

issue occured in these 3 switches. "sg2218& both 2210p''

[Kunalb963]

topology all clients blank.

but in client section showing all clients.on selecting single client shows this:below image

[Kunalb963]

below all images from windows beta 6.3.0.36 software.(SWITCHES used:SG2218, 2- SG2210P AND ROUTER: ER605)

belows images in docker clients missing verify from above docker images

[Kunalb963]

Controller Version

6.3.0.36

Describe the Bug

[Bug]: OMADA BETA 6.3.0.36 BUG IN DEVICE ->MANAGED DEVICE->SWITCH->NETWORK VIEW->ROUTING TABLE SECTION IS BLANK COMPLETELY. ON ALL SWITCHES MISSING. BUT WORKING FINE ON WINDOWS BETA 6.3.0.36. EVEN AFTER SEVERAL FRESH INSTALL ITS BLANK NO ROUTING TABLE. SO I SHIFTED TO WINDOWS BETA VERSION. DUE TO THIS FACEING INTERNET ISSUE, TOPOLOGY ISSUE AND WHILE CLICKING ON ANY CLIENT IT SHOWS "CLIENT DOES NOT EXIST".

Expected Behavior

ALL IMAGES HERE ARE FROM WINDOWS OMADA BETA 6.3.0.36. ABOVE SECTION IS BLANK COMPLETELY. ABOVE SECTION AT RIGHT MOST SIDE: CLIENT/DEVICE DOES NOT EXIST. IN PLACE OF SINGLE DEVICE DETAIL.

Steps to Reproduce

NA

omada-controller.html

How You're Launching the Container

version: "3.1"
services:
   mongodb:
    container_name: mongodb
    image: mongo:4.4.6
    restart: always
    #ports:
      #- 27017:27017
    environment:
      - MONGO_INITDB_ROOT_USERNAME=admin
      - MONGO_INITDB_ROOT_PASSWORD=0m4d4
      - MONGO_INITDB_DATABASE=omada
    volumes:
      - /volume1/docker/omada/mongodb/config:/data/configdb
      - /volume1/docker/omada/mongodb/data:/data/db
    networks:
      #lancache:
        #ipv4_address: 192.168.0.160
      omada-bridge: 
        ipv4_address: 172.19.0.6

   omada-controller:
    container_name: omada-controller
    image: mbentley/omada-controller:beta-6.3
    mem_limit: 2g
    memswap_limit: 3g
    cpu_shares: 2048
    restart: always
    ulimits:
      nofile:
        soft: 4096
        hard: 8192
    stop_grace_period: 60s
    networks:
      omada-bridge: 
        ipv4_address: 172.19.0.2        # PRIMARY → GUI + Reverse Proxy
      lancache:         # SECONDARY → LAN discovery
        ipv4_address: 192.168.0.149
    ports:
      - 8088:8088
      - 8043:8043
      - 8843:8843
      - 19810:19810/udp
      - 27001:27001/udp
      - 29810:29810/udp
      - 29811-29817:29811-29817
    environment:
      - PUID=1026
      - PGID=100
      - JAVA_MAX_HEAP_SIZE=1024m
      - JAVA_MIN_HEAP_SIZE=128m
      - MONGOD_EXTRA_ARGS=--wiredTigerCacheSizeGB 0.50
      - MONGO_EXTERNAL=true

      # ✅ ADDED — Correct full MongoDB URI (your old one was incomplete)
      - EAP_MONGOD_URI=mongodb://admin:0m4d4@172.19.0.6:27017/omada?authSource=admin

      - MANAGE_HTTP_PORT=8088
      - MANAGE_HTTPS_PORT=8043
      - PORTAL_HTTP_PORT=8088
      - PORTAL_HTTPS_PORT=8843
      - UPGRADE_HTTPS_PORT=8043
      - PORT_APP_DISCOVERY=27001
      - PORT_DISCOVERY=29810
      - PORT_MANAGER_V1=29811
      - PORT_ADOPT_V1=29812
      - PORT_UPGRADE_V1=29813
      - PORT_MANAGER_V2=29814
      - PORT_TRANSFER_V2=29815
      - PORT_RTTY=29816
      - PORT_DEVICE_MONITOR=29817
      - WEB_CONFIG_OVERRIDE=true
      - SHOW_SERVER_LOGS=true
      - SHOW_MONGODB_LOGS=false
      - SSL_CERT_NAME=tls.crt
      - SSL_KEY_NAME=tls.key
      - TZ=Asia/Kolkata

      # ✅ ADDED — Spring Boot tuning (APPLICATION_PROPERTIES)
      #- APPLICATION_PROPERTIES=|
         # server.tomcat.threads.max=50
         # server.tomcat.threads.min-spare=5
         # spring.task.execution.pool.core-size=5
         # spring.task.execution.pool.max-size=20
         # spring.task.execution.pool.queue-capacity=100
        #  spring.task.scheduling.pool.size=2
         # logging.level.root=WARN
         # logging.level.com.tplink=INFO

    volumes:
      - /volume1/docker/omada/data:/opt/tplink/EAPController/data
      - /volume1/docker/omada/logs:/opt/tplink/EAPController/logs
      #- /volume3/docker/omada/properties:/opt/tplink/EAPController/properties

volumes:
   omada-mongo-config: null
   omada-mongo-data: null
   omada-init-scripts: null
   omada-data: null
   omada-logs: null

networks:
  omada-bridge:
    external: true
  lancache:
    external: true

Container Logs

UPLOADED FILE ABOVE.[omada-controller.html](https://github.com/user-attachments/files/30620404/omada-controller.html)

MongoDB Logs

Additional Context

No response

for now in beta 6.3.0.42. this issue has been solved but upload speed rate not showing correctly or frquently.

[mbentley]

I've migrated this to a discussion since it's an upstream issue and nothing where action can be taken on the image.