Dev1 Galaxy Forum / [SOLVED] Unable to run Mullvad VPN

Re: [SOLVED] Unable to run Mullvad VPN

dummy@example.com (Catnip) — Sun, 22 Mar 2026 19:26:24 +0000

https://github.com/sys-fs/mullvad-repack

is working correctly now. Compiled and running

Re: [SOLVED] Unable to run Mullvad VPN

dummy@example.com (Catnip) — Sun, 22 Mar 2026 01:03:37 +0000

I spoke too soon. The script above compiled, however mullvad can not connect. it was pointed out to me on IRC Channel this git repo
https://github.com/sys-fs/mullvad-repack

this script does run but.... there are errors i am unable to get rid of in apt. I am not sure exactly how to correct. i have the output below. If anyone has suggestions, please let me know.

Thank you

 sudo dpkg --configure -a
Setting up mullvad-vpn (2026.1) ...
insserv: warning: current start runlevel(s) (empty) of script `mullvad-daemon' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (1 2 3 4 5) of script `mullvad-daemon' overrides LSB defaults (1).
Starting Mullvad VPN daemon: mullvad-daemon.
update-rc.d: error: initscript does not exist: /etc/init.d/mullvad-early-boot-blocking
dpkg: error processing package mullvad-vpn (--configure):
 installed mullvad-vpn package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 mullvad-vpn

Re: [SOLVED] Unable to run Mullvad VPN

dummy@example.com (Catnip) — Sat, 21 Mar 2026 19:38:09 +0000

Thank you! I was following another script shared with me which had errors. i edited your shell script on the 2026.1 deb file and everything works!

1st post as I just installed Devuan yesterday on my laptop, and second machine which i am typing on. This helped me greatly. Now i just wish I knew what each part of this shell script did..

Re: [SOLVED] Unable to run Mullvad VPN

dummy@example.com (delgado) — Fri, 06 Mar 2026 19:53:50 +0000

Edit2: Post heavily edited!

Purpose: Modify 'mullvad-vpn_2025.14_amd64.deb' to include sysv-init scripts.
Output: 'mullvad-vpn_2025.14~1sysv_amd64.deb'

'DEBIAN/postinst':
mullvad service is NOT enabled at boot time (intentionally)
systemctl lines are commented out: --> no need for systemctl on devuan; then on systemd also NOT enabled at boot time
alternatively: systemctl lines can stay --> updated "docker-systemctl-replacement" needed
Enable service: see post above "forte #9"

The following is a script to create the modified debian package. Adjust to your flavour.

$ cat modify_mullvad_deb.sh

#!/bin/bash
### recreate mullvad-deb-package for devuan
# https://unix.stackexchange.com/questions/138188/easily-unpack-deb-edit-postinst-and-repack-deb
# e.g.: (do as root!)
mkdir tmp
dpkg-deb -R mullvad-vpn_2025.14_amd64.deb tmp
## edit / patch  DEBIAN/postinst
# comment-out lines starting with 'systemctl' ?
sed -i 's/^systemctl/# systemctl/g' tmp/DEBIAN/postinst
# patch for systemctl (docker-systemctl-replacement)
sed -i -e 's/"\/usr\/lib\/systemd\/system\/mullvad-daemon.service"/mullvad-daemon.service/' \
       -e 's/"\/usr\/lib\/systemd\/system\/mullvad-early-boot-blocking.service"/mullvad-early-boot-blocking.service/' \
    tmp/DEBIAN/postinst
# create sysv-init scripts
mkdir -p tmp/etc/init.d
sysd2v.sh tmp/usr/lib/systemd/system/mullvad-early-boot-blocking.service > tmp/etc/init.d/mullvad-early-boot-blocking
sysd2v.sh tmp/usr/lib/systemd/system/mullvad-daemon.service > tmp/etc/init.d/mullvad-daemon
sed -i 's/"MULLVAD_RESOURCE_DIR=/MULLVAD_RESOURCE_DIR="/' tmp/etc/init.d/mullvad-daemon     # correct entry
chmod +x tmp/etc/init.d/mullvad-daemon tmp/etc/init.d/mullvad-early-boot-blocking
chmod g-w tmp/etc/init.d/mullvad-daemon tmp/etc/init.d/mullvad-early-boot-blocking
# re-pack
dpkg-deb -b tmp mullvad-vpn_2025.14~1sysv_amd64.deb

## installation
# cp mullvad-vpn_2025.14~1sysv_amd64.deb /tmp     # user "_apt" can not access files in /root/*
# apt install /tmp/mullvad-vpn_2025.14~1sysv_amd64.deb

#-----------------------------------------------------------------------------#
# Supplemental:
#
## sysd2v.sh   (to create sysv-init scripts)
# https://web.archive.org/web/20210412005920/http://www.trek.eu.org/devel/sysd2v/
# wget https://cgit.git.savannah.nongnu.org/cgit/sysvinit.git/tree/contrib/sysd2v.sh
# chmod +x sysd2v.sh; cp sysd2v.sh /usr/local/bin
#
# systemctl    (updated script - if installed package throws errors)
# git clone https://github.com/gdraheim/docker-systemctl-replacement
# cp docker-systemctl-replacemen/files/docker/systemctl3.py /usr/local/bin/systemctl

Re: [SOLVED] Unable to run Mullvad VPN

dummy@example.com (lynch9) — Sat, 22 Mar 2025 18:41:27 +0000

Had the same problem, great to see it was easier than what I was expecting! I'm happy with OpenVPN and just using mullvad servers though. I don't trust those kinds of "custom" VPN software

Re: [SOLVED] Unable to run Mullvad VPN

dummy@example.com (Deze) — Sat, 15 Mar 2025 16:25:22 +0000

This is great, thank you forte and juic3. The steps had to be spelled out to register x).

Re: [SOLVED] Unable to run Mullvad VPN

dummy@example.com (forte) — Sat, 15 Mar 2025 13:34:10 +0000

The systemctl command is not available on non-systemd distributions. That's why Mullvad VPN doesn't work automatically on Devuan.

1. Create a new file in /etc/init.d called "mullvad".
2. Paste the contents of the script kindly provided by juic3 a few posts back (thanks again).
3. Grant the script with executable permissions by running: sudo chmod +x /etc/init.d/mullvad.
4. Run sudo update-rc.d mullvad defaults.

Mullvad VPN should start automatically now.

Re: [SOLVED] Unable to run Mullvad VPN

dummy@example.com (Deze) — Sat, 15 Mar 2025 13:19:48 +0000

After installing the app using the Mullvad repository it's a matter of
sudo systemctl start mullvad-daemon or am I missing something?

I would like to autostart this terminal command but haven't found a way that's beginner-friendly.

Re: [SOLVED] Unable to run Mullvad VPN

dummy@example.com (forte) — Sun, 09 Mar 2025 10:54:11 +0000

I thought that was just generic boilerplate, and didn't stop to read through but I'll be sure to take a closer look. Thanks again!

Re: [SOLVED] Unable to run Mullvad VPN

dummy@example.com (juic3) — Sat, 08 Mar 2025 13:31:15 +0000

I guess I must have used the sysd2v script, mentioned in the comments in mullvad init script
"# Generated by sysd2v v0.3 -- http://www.trek.eu.org/devel/sysd2v"

Re: [SOLVED] Unable to run Mullvad VPN

dummy@example.com (forte) — Fri, 07 Mar 2025 18:20:56 +0000

All right, that worked perfectly! This leaves me with so many questions such as... why? From all the example init scripts that I've seen, this seems so much shorter. How did you come up with that? Asking because I'd like to know more about it in case I have to do the same with some other service.

Thank you very much!

Re: [SOLVED] Unable to run Mullvad VPN

dummy@example.com (juic3) — Fri, 07 Mar 2025 04:46:26 +0000

Just the new one, no combining. Rest of your procedure sounded right.

Re: [SOLVED] Unable to run Mullvad VPN

dummy@example.com (forte) — Thu, 06 Mar 2025 18:40:15 +0000

I'm sorry, do I need to combine this with the script linked in the previous post? Thanks for that as well, just realized it's yours!

If I were to completely remove Mullvad and start over, is this what I should do:

1. Install Mullvad by either:
a) adding their repository (replacing the code name for "bookworm").
b) running from the .deb file directly.
2. Create a new file at /etc/init.d/mullvad with the contents of this snippet, followed by the rest of the code from the other post starting at around line 20 onwards.
3. Run sudo update-rc.d mullvad defaults.
4. Reboot?

Clearly, I'm out of my element here. I don't mind using the command line and navigate up and down directories, but I've just never handled anything related to SysVinit. In fact, I've never even handled any systemd services, either.

Anyway, thanks for the help.

Re: [SOLVED] Unable to run Mullvad VPN

dummy@example.com (juic3) — Thu, 06 Mar 2025 14:56:14 +0000

Hello, I'm still running Mullvad on Devuan.
The Mullvad file locations have changed a little, my current /etc/init.d/mullvad file looks like this:

#!/bin/sh
# Generated by sysd2v v0.3  --  http://www.trek.eu.org/devel/sysd2v
# kFreeBSD do not accept scripts as interpreters, using #!/bin/sh and sourcing.
if [ true != "$INIT_D_SCRIPT_SOURCED" ] ; then
    set "$0" "$@"; INIT_D_SCRIPT_SOURCED=true . /lib/init/init-d-script
fi
### BEGIN INIT INFO
# Provides:       mullvad-daemon.service
# Required-Start: $syslog $local_fs $remote_fs  
# Required-Stop:  $remote_fs
# Should-Start:   $network NetworkManager
# Should-Stop:    $network NetworkManager
# chkconfig: 35 90 10
# Default-Start:  2 3 4 5
# Default-Stop:   0 1 6
# Description:    Mullvad VPN daemon
### END INIT INFO
DESC="mullvad-daemon"
DAEMON=/usr/bin/mullvad-daemon
DAEMON_ARGS="-v --disable-stdout-timestamps"
PIDFILE=/var/run/mullvad-daemon.service-sysd2v.pid
START_ARGS="--background --make-pidfile"

Then you need to run 'sudo update-rc.d mullvad defaults' to enable mullvad-daemon.
I just commented out the systemctl lines from the postinst script to get rid off errors while running system updates.

[SOLVED] Unable to run Mullvad VPN

dummy@example.com (forte) — Wed, 05 Mar 2025 21:26:56 +0000

Hi everyone,

I've recently moved to Devuan and I'm still working out a few issues that I have. The ones that I'm most unfamiliar with are all related to SysVinit, and more specifically I'd like to ask for some assistance with getting Mullvad VPN up and running.

I did search in the forum and found a few matches about this same issue, including one where an init script was suggested and which I've tried, to no avail.

https://dev1galaxy.org/viewtopic.php?id=3500

Unfortunately, after trying this the Mullvad GUI doesn't even launch after I created this script in /etc/init.d/mullvad. Before that, it would launch but with an error saying that the connection did not work, or something around those lines. Which I assume is because of this other error that I got while installing it in the first place (this is from /var/log/apt/term.log):

Preparing to unpack .../mullvad-vpn_2025.4_amd64.deb ...
Unpacking mullvad-vpn (2025.4) ...
Setting up mullvad-vpn (2025.4) ...
/var/lib/dpkg/info/mullvad-vpn.postinst: line 6: systemctl: command not found
dpkg: error processing package mullvad-vpn (--configure):
 installed mullvad-vpn package post-installation script subprocess returned error exit status 127
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for mailcap (3.70+nmu1) ...
Errors were encountered while processing:
 mullvad-vpn

Obviously, something to do with systemd... I wonder if someone here could help me?

Thank you