Client connectivity not working on Raspbian (aarch64)

### Describe the Bug

Hi,

I have tried to get the "Zero-Trust Private Access" functionality to work for some time and eventually figured out, that it is my newt which is causing the connection to fail. I believe this might have to do with the architecture of my host, which is ARM64 (`aarch64`). While this host has some special network setup (it is part of a DMZ), I never had issues with the "Web-based Public Access", and I was able to get the "Zero-Trust Private Access" functionality to work in no time on a `x86_64` machine.

On the `x86_64` host I can see this line on startup of newt:
```
INFO: 2026/02/17 14:11:48 Client connectivity setup. Ready to accept connections from clients!
```

This line is missing from the log on the `aarch64` host and when I try to connect the app, I will instead get:
```
INFO: 2026/02/17 12:57:00 WireGuard device is not initialized
```
and obviously the App will never complete the connection attempt. This makes me believe that there may be some code which is missing for my architecture, or some other issue with setting up the required wireguard tunnel.

### Environment

- OS Type & Version: Debian GNU/Linux 12 (bookworm) (<-- this is Raspbian)
- Kernel Version: 6.12.34+rpt-rpi-v8
- Pangolin Version: v1.15.4
- Gerbil Version: v1.3.0
- Traefik Version: I don't know, :latest 🙃
- Newt Version: v1.9.0
- Docker Version: v28.3.2

### To Reproduce

This is my `docker-compose.yml` on the Raspberry Pi 4 Model B Rev 1.5:
```yaml
services:
newt:
image: fosrl/newt
container_name: newt
restart: unless-stopped
network_mode: host
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
environment:
- TZ=Europe/Berlin
- PANGOLIN_ENDPOINT=https://xxxxxxxx
- NEWT_ID=xxxxxxxxxx
- NEWT_SECRET=xxxxxxxxxx
- DOCKER_SOCKET=unix:///var/run/docker.sock
```

### Expected Behavior

Same behavior as on `x86_64` obviously 🙂