[d4ggm4sk]

What is the command you’re using to try to start or enable the daemon?

According to the package build (https://aur.archlinux.org/cgit/aur.git/t...d-vpn#n220) the service unit is named “mullvad-daemon,” so try enabling mullvad-daemon.service

Code:

sudo systemctl enable mullvad-daemon.service

---

Also, you’ll need to start the daemon too. Enabling it won’t start it until next time systemd does sweep for services that are enabled (next time the system starts basically).

You can either reboot, or just use

Code:

sudo systemctl start mullvad-daemon.service

To start the daemon.

The command itself seems to have worked, and there seems to be some progress since I can now start the mullvad gui from command line,
but when I try to connect, it still says 'failed to connect to daemon' for some reason. Im sorry...... it should work by now, I have no clue why it isnt running. I want it to work, I dont want to make you disappointed in me if I cant fix this when you are helping me...... Im thinking if it may be some issue that it cant work on Arch, or something? But its strange, because I have had it running before....

I'm inclined to believe that this much is going to be down to user-end configuration. Read up on some of the configuration for Mullvad and WireGuard and using the daemon. At the very least, now you know that it should start up automatically for you when your computer starts once it is properly configured. Something to note is that just because you've ran the standalone application before without issue doesn't mean the daemon will do the same. There are different configuration files that the two are pulling from -- while the standalone application may run without issue, it is pulling configuration from your user home directory. The daemon on the other hand is not, and is pulling from system-wide configuration files.

All that being said, do a little bit of research, find the files the daemon is pulling data from. At the end of it, you will be able to restart or reload the daemon (depending on if the service unit specifies instructions for reloading or restarting the daemon) or at the very least you'll be able to restart and see if changes have been applied.

Im sorry...... it should work by now, I have no clue why it isnt running. I want it to work, I dont want to make you disappointed in me if I cant fix this when you are helping me......

At the end of the day, it's all just a learning experience. You don't need to feel disappointed in yourself, just look at it for face value, that being that you aren't experienced in this and you stand to learn something from it. Most of all, have fun doing it. Pulling system configuration files and working with [slightly] lower level parts of the userspace is something you can get a lot from. I mean, hell, even I am learning something from this experience, even though I'm just trying to help you figure it out. I've never used mullvad, or wireguard, or openvpn. But I've got several years of working with linux and various programs, and I especially have a lot of experience working with systemd and the init process as a whole. But that being the case, if I ever find someone needing to learn about mullvad or openvpn/wireguard and their services, I'll be able to further assist people in the future with it. After all, teaching is the best way to learn.

Yeah, well, the daemon is up and running now. I checked it and there was something with 'vendor process' or smth that wasnt running, but I feel like I probably can handle that on my own and we have together made process with my mullvad-vpn-daemon. If you hadnt helped me with this, it would have been really bad but thanks to you and @Drako I think Im going to be able to make it work in a couple days I was meddling with it before, but right now Im playing WoW. Its important to take breaks too.

I only have barely 2 years of experience with linux and Arch, so I feel like I know almost nothing. But like even if you spend 4 hours just to compile something, maybe you learn something from it too and have fun