On 12/3/2025 at 8:00 AM, arjanw1 said:

Couldn't you just create a new version 6 container and import a config backup ?

Worked beautifully. Thanks!

Updated successfully via MongoDB migration to 8. These were the steps:

-Backup your settings at Omada controller --> Maintenance
-Stop controller, adjust the following command if necessary (i.e. path) and run it:
docker run -it --rm -v /mnt/user/appdata/omada-controller/data:/opt/tplink/EAPController/data mbentley/omada-controller:mongodb-upgrade-3.6-to-8

Then go to the Omada Controller Docker and change tag to i.e. mbentley/omada-controller:6.0, wait and it should be updated. Thanks mbentley 😃.

On 12/8/2025 at 11:40 PM, dayt47 said:

adjust the following command if necessary (i.e. path) and run it

On 12/8/2025 at 11:40 PM, dayt47 said:

Updated successfully via MongoDB migration to 8. These were the steps:

-Backup your settings at Omada controller --> Maintenance
-Stop controller, adjust the following command if necessary (i.e. path) and run it:
docker run -it --rm -v /mnt/user/appdata/omada-controller/data:/opt/tplink/EAPController/data mbentley/omada-controller:mongodb-upgrade-3.6-to-8

Then go to the Omada Controller Docker and change tag to i.e. mbentley/omada-controller:6.0, wait and it should be updated. Thanks mbentley 😃.

Thanks for the steps, this is exactly the information I was looking for! Unfortunately my MongoDB is locked even though I stopped the controller. I stopped the controller via the Unraid UI and is shows 'stopped'. The docker status via docker ps -a is Existed (143). Any ideas on what might be causing this?

This is the log after I ran the upgrade command

Unable to find image 'mbentley/omada-controller:mongodb-upgrade-3.6-to-8' locally

mongodb-upgrade-3.6-to-8: Pulling from mbentley/omada-controller

dfd139f7c731: Already exists

1ff20e015d5e: Pull complete

1caa0849ae6b: Pull complete

7df1face0c7b: Pull complete

27f6c810ffa2: Pull complete

Digest: sha256:fe699702a9d238897b4c7a65b09f4310aaf659869689fe240752ef9144c1250e

Status: Downloaded newer image for mbentley/omada-controller:mongodb-upgrade-3.6-to-8

INFO: running hardware prerequisite check for AVX support on x86_64 to ensure your system can run MongoDB 8...done

INFO: running pre-flight checks on MongoDB...

ERROR: mongod.lock exists and isn't empty! Either the MongoDB wasn't shut down cleanly or there is another process accessing the persistent data files! Unable to execute upgrade!

yesterday i have changed the source from mbentley/omada-controller:6.0 to mbentley/omada-controller:6
now 6.1.0.19

and now i have the problem to conect with the FF (firefox) to the controller.
(bevor the update the login works without any problem)
every time circle (as in the picture)

in the chrome browser the login page works.
can you give me a hint what i can do?
(and NO, using chrome is a option ;))

thanks a lot.

Force refresh the page with your browser - there might have been a change to something in the application that is cached for you. I use Firefox and it works fine here.

What is the process for running using a separate MongoDB install for CPUs which do not support AVX?