Mullvad vpn client issue [SOLVED]

[Hooten]

oops.. no error message?

Client just stuck at "Connecting to daemon".

I meant, when you start the above daemon , do you got any messages?

Oh sorry, not at all.

[fehlix]

Client just stuck at "Connecting to daemon".

I meant, when you start the above daemon , do you got any messages?

Oh sorry, not at all.

Which is good. So what's left, I assume, is to startup the daemon earlier
in the process before the network manager is up
Which means to have a little init.d script for the sturtup of either one of the above daemons.

[fehlix]

Perhaps - at least for a test - try to start the daemon as this.
Do add those lines add the end of the file /etc/rc.local
Keep only one line un-commented either for mullvad-daemon or for qomui-service - not both.
Make sure the last line will be exit 0 followed by a new line.

Code: Select all

# leave onle one line uncommented
/opt/mullvad-vpn/resources/mullvad-daemon  -v --disable-stdout-timestamps
# 
/usr/bin/env qomui-service

So the file /etc/rc.local looks either like this
for mullvad-daemon

Code: Select all

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
/opt/mullvad-vpn/resources/mullvad-daemon  -v --disable-stdout-timestamps

exit 0

or like this for qomui-service

Code: Select all

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
/usr/bin/env qomui-service

exit 0

EDIT: and do reboot after those changes ...

[Hooten]

Perhaps - at least for a test - try to start the daemon as this.
Do add those lines add the end of the file /etc/rc.local
Keep only one line un-commented either for mullvad-daemon or for qomui-service - not both.
Make sure the last line will be exit 0 followed by a new line.

Code: Select all

# leave onle one line uncommented
/opt/mullvad-vpn/resources/mullvad-daemon  -v --disable-stdout-timestamps
# 
/usr/bin/env qomui-service

So the file /etc/rc.local looks either like this
for mullvad-daemon

Code: Select all

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
/opt/mullvad-vpn/resources/mullvad-daemon  -v --disable-stdout-timestamps

exit 0

or like this for qomui-service

Code: Select all

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
/usr/bin/env qomui-service

exit 0

EDIT: and do reboot after those changes ...

I think i've done it right, but nothing changed. BTW i'm testing it in vm, not to worry about bricking anything in my main system.

[fehlix]

I think i've done it right, but nothing changed. BTW i'm testing it in vm, not to worry about bricking anything in my main system.

Yeah, it's probably too late with rc.local at the end of the runlevel, it needs to be get started earlier.
So what is needed would be to have init.d start script to get it a bit earlier started.
You might look whether you can find any mullvad related service files, which we might convert
to inti.d scripts.

[Hooten]

I think i've done it right, but nothing changed. BTW i'm testing it in vm, not to worry about bricking anything in my main system.

Yeah, it's probably too late with rc.local at the end of the runlevel, it needs to be get started earlier.
So what is needed would be to have init.d start script to get it a bit earlier started.
You might look whether you can find any mullvad related service files, which we might convert
to inti.d scripts.

Look i'm not that stupid. I did what you said first and after that i started mullvad, but same thing happened.

[Hooten]

I also trying to run mullvad through openvpn following the instructions from here :https://mullvad.net/en/guides/linux-ope ... tallation/
But when i go to 4. step i get [FAIL] Starting virtual private network daemon: mullvad_no failed!

[fehlix]

OK, I meant if you look for mullvad servcice files within the systemd folder /etc/systemd/system.
And if you post those here we might convert them into alternative start files,
so they get started ealier than rc.local, which appreaas to be to late, when you start MX17 with the default SysVint start system.
I can't test this myself, as I have no mullvad vpn.

[Hooten]

OK, I meant if you look for mullvad servcice files within the systemd folder /etc/systemd/system.
And if you post those here we might convert them into alternative start files,
so they get started ealier than rc.local, which appreaas to be to late, when you start MX17 with the default SysVint start system.
I can't test this myself, as I have no mullvad vpn.

There is a file named "mullvad-daemon.service" and that is inside:

# Systemd service unit file for the Mullvad VPN daemon

[Unit]
Description=Mullvad VPN daemon
Wants=network.target
After=network-online.target
StartLimitBurst=5
StartLimitIntervalSec=20

[Service]
Restart=always
RestartSec=1
ExecStart=/opt/Mullvad\x20VPN/resources/mullvad-daemon -v --disable-stdout-timestamps

[Install]
WantedBy=multi-user.target

[fehlix]

Ah thats, looks nice. The path differs from the one I gave above.
What happens if you start from the command line this

Code: Select all

/opt/Mullvad\ VPN/resources/mullvad-daemon -v --disable-stdout-timestamps

Note the backslash before the space.
Would the daemon run ?