Rustmilian

You fap to YouTube?

Sus mime

Good to hear that it worked.
To explain env, typically when systemd is running a service it only provides a very minimal environment. When using env it passes more of the environment variables and whatnot from userspace, so it's likely that the binary daemon was looking for specific environment variables and it returned an empty string and that's what caused error, it's also useful if the daemon's location changes during runtime or if it's not in a standard location.

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.

System76 is no stranger to desktop development nor Rust-lang. Their team is relatively large, skilled, diverse, and highly dedicated, with years of experience in high-level and low-level development, UX/UI design, and even an OS built from scratch (Redox OS), and so on. Unlike elementary OS's Pantheon, which builds upon existing frameworks like GTK & forked Gnome components, Cosmic (Epoch) is entirely written from scratch, toolkits and all. System76's approach is also more comprehensive and ambitious compared to elementary OS. They're developing native Rust applications like the COSMIC app store, terminal, screenshot tool, and text editor. Early performance tests show promising results, even in virtual environments. The company's financial resources also allow for significant investment in COSMIC's development, supporting a dedicated team and a long-term vision. This contrasts with elementary OS's more gradual, community-driven growth.
Pop_OS! is also an already very popular distribution, and importantly popular amongst newbies. System76 is also a hardware vendor meaning they can tightly integrate Cosmic with their hardware, and in fact do so much more easily than what they've already been doing with Pop_OS!.
Compared to ElementaryOS, System76 is in a much better position.

Nice.
Don't forget to put [Solved] in your post title.

It's already going to be the default on one of the major distros at launch; Pop_OS! by System76. It'll grow in popularity pretty quickly.