Rustmilian

Try ExecStart=/usr/bin/env /path/to/daemon
Also what's the output of ldd /path/to/daemon & sudo systemd-run /path/to/daemon ? Maybe check systemctl show-environment. Maybe try adding Type=simple , this tells systemd that the service will fork.

If that fails, we could try ExecStart=/usr/bin/strace -f -o /tmp/daemon_strace.log /path/to/daemon for stactrace & ExecStart=/bin/sh -c '/path/to/daemon > /tmp/daemon.log 2>&1' to log the daemon.

Is the daemon a binary? If so drop the bash part and try sudo chmod 755 /path/to/daemon.

I assume so, but just to be sure, have you run sudo systemctl enable blah.service then reboot? It'll symbolic link to the systemd auto start service and run it at boot.
Also, make sure everything is marked as executable; especially whatever you have "/path/to/daemon" set as. sudo chmod +x /path/to/daemon
Restart the service or reboot then :
sudo systemctl status blah.service

What's the specific VPN service? I'll check their docs.

On that, make sure it's in the root systemd path. Something like /etc/systemd/system/blah.service, placing it in the user systemd service path (~/.config/systemd/user/) will cause permission errors as it'll try accessing the root user from the current user.

Just burn your worn clothes and buy new ones; the true fashion industry experience.

Can you access the BIOS/Bootloader?
Is it x86 or ARM?

Jeffrey Toobin

Maybe a wake-sleep issue with the cards power saving mode, if it happens again, ping me. Else I'mma consider this solved.

Check the output of :
lsusb | grep -A 3 -i network
lspci -v | grep -A 3 -i network
rfkill list all

[email protected]
[email protected]

Go get bitches.