Unifi Controller container problem


There are a few days I can’t run the Unifi controller and I get a message:

’‘Unify controller is starting up. Please wait a moment…’'

Can anyone please help me to troubleshoot this?
Many thanks

please share your host os and version, your docker compose or run snippet, and your full docker logs (in pastebin)

1 Like


Thank you very much for your response.

“build_version”: “Linuxserver.io version:- 5.10.25-ls29 Build-date:- 2019-08-03T08:30:46-04:00”

[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
usermod: no changes

          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/

Brought to you by linuxserver.io
We gratefully accept donations at:

User uid:    1000
User gid:    100

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

You’re using an image that’s nearly 2 years old. Get your container updated to the latest version and see if you still have the same issue. Though bare in mind you may receive updates to your hardware aswell.

1 Like

Thank you for your answer.

The thing is I set it up 2 years ago and I can’t remember what I did hence I haven’t tried to update it until now.

Now, I deleted the container, pulled a new image, run it but unfortunately I’m getting errors while I’m trying to enter and save the arguments.

I’m hoping to use the same configuration saved in my hard disc.

If you’re seeking help with the new problem, you still need to provide what I originally asked for. your docker run or docker compose snippet and updated logs in pastebin. If you are using something other than docker compose, you can hope someone helps you, but we do not support anything other than docker cli or docker-compose (both of which work fine on OMV) we do not in any way support portainer.