-
Notifications
You must be signed in to change notification settings - Fork 32
Troubleshooting
lemker edited this page May 27, 2026
·
5 revisions
UniFi OS Server runs as a collection of systemd services inside a container. When a service does not start properly, it can break the startup sequence and prevent the next service from starting.
At a high level, the service startup sequence is as follows: postgres > mongodb > unifi-core > unifi
View the container logs with docker logs unifi-os-server. The output should look similar to:
No UOS_UUID present, generating...
Setting UOS_SYSTEM_IP to <IP>
Setting UOS_UUID to <UOS_UUID>
Setting UOS_SERVER_VERSION to 5.0.8
Setting FIRMWARE_PLATFORM to linux-x64Make sure all services are up and running inside the container. Open a shell into the container with docker exec -it unifi-os-server bash and run:
systemctl --type=service list-unitsIf the above troubleshooting steps did not resolve your issue, please feel free to create a new issue in the repo with the following information:
- Your host specs including device/platform, OS, CPU, RAM, and number of connected devices
- The container logs
- The output of
systemctl --type=service list-unitsfrom inside the container