[Help]: Can't access Web UI

[jgab76]

Controller Version

v15.3.30.18

Describe Your Issue or Question

Docker container is started per Portainer. See image.

Expected Behavior

Access WebUI

Steps to Reproduce

1. Start Docker container with Portainer
2. Can't access WebUI

How You're Launching the Container

services:
  portainer:
    container_name: portainer
    image: portainer/portainer-ce
    restart: always
    ports:
      - "9000:9000/tcp"
    environment:
      - TZ=Europe/London
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /opt/portainer:/data

  duplicati:
    image: lscr.io/linuxserver/duplicati:latest
    container_name: duplicati
    environment:
      - PUID=0
      - PGID=0
      - TZ=Etc/UTC
      - CLI_ARGS= #optional
    volumes:
      - /opt/duplicati/config:/config
      - /opt:/source
    ports:
      - 8200:8200
    restart: unless-stopped

  homeassistant:
      container_name: homeassistant1
      image: "ghcr.io/home-assistant/home-assistant:stable"
      volumes:
        - /opt/homeassistant/config:/config
        - /etc/localtime:/etc/localtime:ro
      restart: unless-stopped
      privileged: true
      network_mode: host

  omada-controller:
    container_name: omada-controller
    image: mbentley/omada-controller:5.13
    restart: unless-stopped
    ulimits:
      nofile:
        soft: 4096
        hard: 8192
    stop_grace_period: 60s
    network_mode: host
    environment:
      - PUID=508
      - PGID=508
      - 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
      - SSL_CERT_NAME=tls.crt
      - SSL_KEY_NAME=tls.key
      - TZ=Etc/UTC
    volumes:
      - omada-data:/opt/tplink/EAPController/data
      - omada-logs:/opt/tplink/EAPController/logs

volumes:
  omada-data:
  omada-logs:

Container Logs

INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508)
INFO: Group (omada) doesn't exist; creating
INFO: User (omada) doesn't exist; creating
INFO: Time zone set to 'Etc/UTC'
INFO: Value of 'manage.http.port' already set to 8088 in omada.properties
INFO: Value of 'manage.https.port' already set to 8043 in omada.properties
INFO: Value of 'portal.http.port' already set to 8088 in omada.properties
INFO: Value of 'portal.https.port' already set to 8843 in omada.properties
INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties
INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties
INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties
INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties
INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties
INFO: Value of 'port.discovery' already set to 29810 in omada.properties
INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties
INFO: Value of 'port.rtty' already set to 29816 in omada.properties
INFO: Value of 'mongo.external' already set to false in omada.properties
INFO: Value of 'eap.mongod.uri' already set to mongodb://127.0.0.1:27217/omada in omada.properties
WARN: Ownership not set correctly on '/opt/tplink/EAPController/properties'; setting correct ownership (omada:omada)
ERROR: The version from the image (5.13.30.8) is older than the last version executed (5.14.26.1)!  Refusing to start to prevent data loss!
  To bypass this check, remove /opt/tplink/EAPController/data/LAST_RAN_OMADA_VER.txt only if you REALLY know what you're doing!

MongoDB Logs

2024-09-26T23:29:36.578+0000 I STORAGE  [initandlisten] WiredTiger message [1727393376:578821][198:0x7fb5af6040], txn-recover: Main re>
2024-09-26T23:29:37.145+0000 I STORAGE  [initandlisten] WiredTiger message [1727393377:145400][198:0x7fb5af6040], txn-recover: Recover>
2024-09-26T23:29:37.427+0000 I STORAGE  [initandlisten] WiredTiger message [1727393377:427161][198:0x7fb5af6040], txn-recover: Recover>
2024-09-26T23:29:37.689+0000 I STORAGE  [initandlisten] WiredTiger message [1727393377:689941][198:0x7fb5af6040], txn-recover: Set glo>
2024-09-26T23:29:37.748+0000 I CONTROL  [initandlisten]
2024-09-26T23:29:37.748+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
2024-09-26T23:29:37.748+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
2024-09-26T23:29:37.748+0000 I CONTROL  [initandlisten]
2024-09-26T23:29:37.774+0000 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '../data/db/diag>
2024-09-26T23:29:37.775+0000 I NETWORK  [initandlisten] waiting for connections on port 27217
2024-09-26T23:29:38.843+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:56682 #1 (1 connection now open)
2024-09-26T23:29:38.844+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:56680 #2 (2 connections now open)
2024-09-26T23:29:38.883+0000 I NETWORK  [conn2] received client metadata from 127.0.0.1:56680 conn2: { driver: { name: "mongo-java-dri>
2024-09-26T23:29:38.887+0000 I NETWORK  [conn1] received client metadata from 127.0.0.1:56682 conn1: { driver: { name: "mongo-java-dri>
2024-09-26T23:29:39.128+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:56696 #3 (3 connections now open)
2024-09-26T23:29:39.130+0000 I NETWORK  [conn3] received client metadata from 127.0.0.1:56696 conn3: { driver: { name: "mongo-java-dri>
2024-09-26T23:29:39.248+0000 I NETWORK  [conn3] end connection 127.0.0.1:56696 (2 connections now open)
2024-09-26T23:29:39.250+0000 I NETWORK  [conn2] end connection 127.0.0.1:56680 (1 connection now open)
2024-09-26T23:29:39.250+0000 I NETWORK  [conn1] end connection 127.0.0.1:56682 (0 connections now open)
2024-09-26T23:29:39.365+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:56712 #4 (1 connection now open)
2024-09-26T23:29:39.366+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:56710 #5 (2 connections now open)
2024-09-26T23:29:39.366+0000 I NETWORK  [conn4] received client metadata from 127.0.0.1:56712 conn4: { driver: { name: "mongo-java-dri>
2024-09-26T23:29:39.367+0000 I NETWORK  [conn5] received client metadata from 127.0.0.1:56710 conn5: { driver: { name: "mongo-java-dri>
2024-09-26T23:29:39.376+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:56736 #6 (3 connections now open)
2024-09-26T23:29:39.377+0000 I NETWORK  [conn6] received client metadata from 127.0.0.1:56736 conn6: { driver: { name: "mongo-java-dri>
2024-09-26T23:29:39.396+0000 I NETWORK  [conn4] end connection 127.0.0.1:56712 (2 connections now open)
2024-09-26T23:29:39.397+0000 I NETWORK  [conn5] end connection 127.0.0.1:56710 (1 connection now open)
2024-09-26T23:29:39.398+0000 I NETWORK  [conn6] end connection 127.0.0.1:56736 (0 connections now open)
2024-09-26T23:30:34.543+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:48424 #7 (1 connection now open)
2024-09-26T23:30:34.551+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:48436 #8 (2 connections now open)
2024-09-26T23:30:34.555+0000 I NETWORK  [conn8] received client metadata from 127.0.0.1:48436 conn8: { driver: { name: "mongo-java-dri>
2024-09-26T23:30:34.557+0000 I NETWORK  [conn7] received client metadata from 127.0.0.1:48424 conn7: { driver: { name: "mongo-java-dri>
2024-09-26T23:30:36.678+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:48774 #9 (3 connections now open)
2024-09-26T23:30:36.680+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:48784 #10 (4 connections now open)
2024-09-26T23:30:36.684+0000 I NETWORK  [conn9] received client metadata from 127.0.0.1:48774 conn9: { driver: { name: "mongo-java-dri>
2024-09-26T23:30:36.686+0000 I NETWORK  [conn10] received client metadata from 127.0.0.1:48784 conn10: { driver: { name: "mongo-java-d>
2024-09-26T23:30:36.704+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:48796 #11 (5 connections now open)
2024-09-26T23:30:36.706+0000 I NETWORK  [conn11] received client metadata from 127.0.0.1:48796 conn11: { driver: { name: "mongo-java-d>
2024-09-26T23:30:36.754+0000 I NETWORK  [conn11] end connection 127.0.0.1:48796 (4 connections now open)
2024-09-26T23:30:36.755+0000 I NETWORK  [conn9] end connection 127.0.0.1:48774 (3 connections now open)
2024-09-26T23:30:36.758+0000 I NETWORK  [conn10] end connection 127.0.0.1:48784 (2 connections now open)
2024-09-26T23:30:36.818+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:48810 #12 (3 connections now open)
2024-09-26T23:30:36.826+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:48816 #13 (4 connections now open)
2024-09-26T23:30:36.827+0000 I NETWORK  [conn12] received client metadata from 127.0.0.1:48810 conn12: { driver: { name: "mongo-java-d>
2024-09-26T23:30:36.827+0000 I NETWORK  [conn13] received client metadata from 127.0.0.1:48816 conn13: { driver: { name: "mongo-java-d>
2024-09-26T23:30:36.847+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:48822 #14 (5 connections now open)
2024-09-26T23:30:36.848+0000 I NETWORK  [conn14] received client metadata from 127.0.0.1:48822 conn14: { driver: { name: "mongo-java-d>
2024-09-26T23:30:36.882+0000 I NETWORK  [conn14] end connection 127.0.0.1:48822 (4 connections now open)
2024-09-26T23:30:36.882+0000 I NETWORK  [conn12] end connection 127.0.0.1:48810 (3 connections now open)
2024-09-26T23:30:36.883+0000 I NETWORK  [conn13] end connection 127.0.0.1:48816 (2 connections now open)
2024-09-26T23:30:45.386+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:48838 #15 (3 connections now open)
2024-09-26T23:30:45.388+0000 I NETWORK  [conn15] received client metadata from 127.0.0.1:48838 conn15: { driver: { name: "mongo-java-d>
2024-09-26T23:30:46.991+0000 I NETWORK  [conn15] end connection 127.0.0.1:48838 (2 connections now open)
2024-09-26T23:30:46.992+0000 I NETWORK  [conn7] end connection 127.0.0.1:48424 (1 connection now open)
2024-09-26T23:30:46.994+0000 I NETWORK  [conn8] end connection 127.0.0.1:48436 (0 connections now open)

Additional Context

No response

[mbentley]

It's in your logs right at the end:

ERROR: The version from the image (5.13.30.8) is older than the last version executed (5.14.26.1)!  Refusing to start to prevent data loss!

The controller isn't actually running because it is not starting. At some point, it looks like you upgraded to 5.14.26.1 which ran and you rolled back to 5.13.30.8. The entrypoint script is trying to prevent the controller's data from becoming corrupt since it will if you try to downgrade. Did you ever actually have the controller start on 5.14.26.1 or were you running into #418 ?

[jgab76]

No, I could never get it to start with 5.14, so I assumed it was the #418 issue. I removed the container including persistent volumes using Portainer. Then changed the docker-compose file to use 5.13. With 5.14, it looked like it was hung up on even starting. With 5.13, Portainer says it's running but the log says otherwise. Not sure what to do from here.

[mbentley]

The file mentioned, LAST_RAN_OMADA_VER.txt, in your persistent data folder that is mapped to /opt/tplink/EAPController/data inside the container is still there and that is what is blocking the controller from starting. Removing that file and restarting the container should allow it to start. Portainer is probably not picking up on the fact that the container is basically stuck in a restarting loop.

[jgab76]

That worked! Thanks!