Hi I have selected the option Launch on Device Startup. But it doesn’t start and when I start it manually I need to sudo into the daemon every time
Is there a way to fix that?
Are you on Linux and how did you install nymvpn?
You might have to create a systemd service for the daemon and the vpn app manually.
I followed these instructions from nym.com
Download NymVPN for Linux | Nym
1 Like
If you followed that it should be installed correctly.
Could you check systemctl status nym-vpnd.service (may need sudo)? It should show that it’s enabled and active.
Also what do you mean by “I need to sudo into the daemon every time”, does that mean it’s not started?
Also it not starting means that the vpn window doesn’t open on reboot, correct? Not that it doesn’t connect automatically?
If nym-vpnd.service would be enabled and active, you could try creating and enabling a systemd user service executing the nym vpn gui app binary instead of relying on the option in the app.
You could also create and enable another systemd service that runs nym-vpnc connect. This automatically connects to the VPN if you’re logged in.
More info on nym-vpnc is available here. It should already be installed for you.
tested on debian 13 same behavior u have to confirm the root privileges
this should be integrated on the install routine to create an elevated system.d process or
1 Like
It does show both active and enabled. The VPN app itself doesn’t open on startup and when I open it manually it requires a sudo for the daemon to connect.
1 Like
That to me seems like a bug. I installed nym vpn some time ago the same way you did, also on debian 13 and the app did open automatically after activating it and did not require authentication for super user privileges to connect to the daemon.
Might be a regression in one of the newer versions of nymvpn. But this seems generally strange to me, as far as I know the daemon is meant to allow the vpn app to run without super user privileges.