unifi-os-server LXC won't come up after a node reboot

[joshuataylor]

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

ct/unifi-os-server.sh

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/unifi-os-server.sh)"

⚙️ What settings are you using?

• Default Settings
• Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.1.6/71482d1833ded40a (running kernel: 6.17.13-1-pve)

📝 Provide a clear and concise description of the issue.

Was running this for a while, today did a node reboot and it now seems to be failing to start, and is giving me a podman error.

Not sure of where to raise this, or how to troubleshoot further. Let me know what you would like from me.

Proxmox 9.1 (Debian 13), I seem to be getting an IPv6 address for this LXC containers (And others, even though it's set to static for this LXC node (??)). Unrelated, is that a new 9.x feature, I use IPv6 for all my other containers anyway. Disabled via sysctl.conf in the LXC container.

cat /etc/pve/lxc/103.conf

#<div align='center'>
#  <a href='https%3A//Helper-Scripts.com' target='_blank' rel='noopener noreferrer'>
#    <img src='https%3A//raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/images/logo-81x112.png' alt='Logo' style='width%3A81px;height%3A112px;'/>
#  </a>
#
#  <h2 style='font-size%3A 24px; margin%3A 20px 0;'>UniFi-OS-Server LXC</h2>
#
#  <p style='margin%3A 16px 0;'>
#    <a href='https%3A//ko-fi.com/community_scripts' target='_blank' rel='noopener noreferrer'>
#      <img src='https%3A//img.shields.io/badge/&#x2615;-Buy us a coffee-blue' alt='spend Coffee' />
#    </a>
#  </p>
#
#  <span style='margin%3A 0 10px;'>
#    <i class="fa fa-github fa-fw" style="color%3A #f5f5f5;"></i>
#    <a href='https%3A//github.com/community-scripts/ProxmoxVE' target='_blank' rel='noopener noreferrer' style='text-decoration%3A none; color%3A #00617f;'>GitHub</a>
#  </span>
#  <span style='margin%3A 0 10px;'>
#    <i class="fa fa-comments fa-fw" style="color%3A #f5f5f5;"></i>
#    <a href='https%3A//github.com/community-scripts/ProxmoxVE/discussions' target='_blank' rel='noopener noreferrer' style='text-decoration%3A none; color%3A #00617f;'>Discussions</a>
#  </span>
#  <span style='margin%3A 0 10px;'>
#    <i class="fa fa-exclamation-circle fa-fw" style="color%3A #f5f5f5;"></i>
#    <a href='https%3A//github.com/community-scripts/ProxmoxVE/issues' target='_blank' rel='noopener noreferrer' style='text-decoration%3A none; color%3A #00617f;'>Issues</a>
#  </span>
#</div>
arch: amd64
cores: 4
features: nesting=1
hostname: unifi-os-server
memory: 5000
net0: name=eth0,bridge=vmbr0,gw=192.168.123.1,hwaddr=c0:ff:ee:04:02:21,ip=192.168.123.21/24,type=veth
onboot: 1
ostype: debian
rootfs: kitthin:vm-103-disk-0,size=20G
swap: 512
tags: community-script;network
timezone: UTC
lxc.cgroup2.devices.allow: a
lxc.cap.drop:
lxc.cgroup2.devices.allow: c 188:* rwm
lxc.cgroup2.devices.allow: c 189:* rwm
lxc.mount.entry: /dev/serial/by-id  dev/serial/by-id  none bind,optional,create=dir
lxc.mount.entry: /dev/ttyUSB0       dev/ttyUSB0       none bind,optional,create=file
lxc.mount.entry: /dev/ttyUSB1       dev/ttyUSB1       none bind,optional,create=file
lxc.mount.entry: /dev/ttyACM0       dev/ttyACM0       none bind,optional,create=file
lxc.mount.entry: /dev/ttyACM1       dev/ttyACM1       none bind,optional,create=file
lxc.cgroup2.devices.allow: c 10:200 rwm
lxc.mount.entry: /dev/net/tun dev/net/tun none bind,create=file

🔄 Steps to reproduce the issue.

reboot the container

❌ Paste the full error output (if available).

Mar 01 04:37:24 unifi-os-server podman[2038]: 2026-03-01 04:37:24.307307395 +0000 UTC m=+0.048748525 container exec_died 8fe2c0f24c634148d2f9979a86faea1a99d849d283d9d6c530ec810eab17a73b (image=docker.io/library/uosserver:0.0.54, name=uosserver)
Mar 01 04:37:24 unifi-os-server podman[2021]: 2026-03-01 04:37:24.318565155 +0000 UTC m=+0.136605354 container exec_died 8fe2c0f24c634148d2f9979a86faea1a99d849d283d9d6c530ec810eab17a73b (image=docker.io/library/uosserver:0.0.54, name=uosserver)
Mar 01 04:37:24 unifi-os-server uosserver-service[143]:  INFO Supervisor connected
Mar 01 04:37:24 unifi-os-server uosserver-service[143]:  INFO Received action: getPorts msg: Message { header: Json(Object {"action": String("getPorts"), "id": String("409c30be-1a54-4572-b28a-913463fa7a7d"), "timestamp": Number(1772339844357), "type": String("request")}), body: Json(Object {}) }
Mar 01 04:37:24 unifi-os-server uosserver-service[143]:  INFO Sending ports configuration...
Mar 01 04:37:31 unifi-os-server netavark[103]: timeout met: exiting after 30 secs of inactivity
Mar 01 04:37:31 unifi-os-server systemd[1]: netavark-dhcp-proxy.service: Deactivated successfully.
Mar 01 04:38:13 unifi-os-server podman[2328]: 2026-03-01 04:38:13.094985315 +0000 UTC m=+0.170400702 container health_status 8fe2c0f24c634148d2f9979a86faea1a99d849d283d9d6c530ec810eab17a73b (image=docker.io/library/uosserver:0.0.54, name=uosserver, health_status=healthy, health_failing_streak=0, health_log=)

/var/lib/uosserver/logs/uos-discovery-client.log

2026-03-01T04:21:06.044316044Z  INFO Trying UDP listener again failed_count=1 backoff=36s
2026-03-01T04:21:06.044395534Z  INFO Initializing TCP listener host="127.0.0.1" port=11002
2026-03-01T04:21:06.044409694Z  INFO Initializing server addr=127.0.0.1:11002
2026-03-01T04:21:31.705200734Z  INFO Starting UniFi OS discovery client v0.1.7
2026-03-01T04:21:31.705274054Z ERROR UDP listener error err=creating socket for passive listener

Caused by:
    0: joining multicast group
    1: No such device (os error 19)

🖼️ Additional context (optional).

Tried giving it a static IPv4, DHCP (was DHCP before, same go).

Not sure of where to raise this, or how to troubleshoot further. Let me know what you would like from me.

Was happy with Unifi Network Application, thanks Ubiquiti, :-/. (Not y'all, you do great work, just a rant.)

Relevant maybe -- will play with it https://community.ui.com/questions/Uosserver-does-not-seem-to-start-properply-after-reboot/75ff79fa-a1b7-4ab4-98d6-6ab96e485914

[MickLesk]

This isnt caused by the script itself — it’s a known upstream startup race with uosserver on Debian 13/Ubuntu.
After a reboot, uosserver sometimes starts before the user session / DBus / network stack is fully ready, so it appears “running” but isn’t actually reachable. Manually restarting the service after boot usually fixes it.

You can either;

1. Restart uosserver once after each reboot as a quick workaround, or
2. Adjust the systemd unit so it starts after DBus and the user session are fully up, which has resolved it for many users.

[joshuataylor]

I gave that a go, but couldn't get it to work earlier -- I decided to try a full reinstall. I'll try again later tonight (AU).

I'll test various workarounds and see what's easiest/best as a recommendation (or a default?), IMHO a proper systemd override would be nicer than just monkey-patching the systemd service, which is what the forum post recommends.

We could then recommending adding /etc/systemd/system/whatever.service.d/99-proxmoxscripts.conf or something, so we know the file exists, and can get users to remove if later if needed.

Not sure how it's handled elsewhere.