bug: BlueOS web interface dead after reboot, but SSH works (Pi missing from router)

### Bug description

Hi everyone,

I'm running BlueOS on a Raspberry Pi and running into a weird connection issue.

When I flash a fresh copy of BlueOS, everything works perfectly. But after running it for a while, if I reboot the Pi, I get completely locked out of the web interface. I cannot access it via its IP address or blueos.local.

Additionally, the Pi completely disappears from my router's connected clients list—I don't see an IP for it in the router at all.

However, despite all of this, I can still SSH into the Pi perfectly fine. Has anyone experienced the web UI/Docker containers failing to load and the Pi dropping off the router list, while SSH somehow stays alive? I noticed a 0x50005 under-voltage warning in the terminal—could a power dip during the boot sequence cause the heavy BlueOS services (and DHCP broadcasts) to timeout while leaving the lightweight SSH service running?

Any advice on how to fix this would be appreciated!

### Steps to reproduce

1. install blueos into the rasberry-pi
2. assign static ip
3. reboot

### Primary pain point(s)

everytime ip is lost on reboot

### Additional context

_No response_

### Prerequisites

- [x] I have checked to make sure that a similar request has not already been filed or fixed.