Welcome!
Important information
-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Mullvad vpn client issue [SOLVED]

User avatar
fehlix
Forum Veteran
Forum Veteran
Posts: 3934
Joined: Wed Apr 11, 2018 5:09 pm

Re: Mullvad vpn client issue

#31

Post by fehlix » Fri Sep 28, 2018 1:21 pm

Hooten wrote:
Fri Sep 28, 2018 11:22 am
Phew... you scared me for a moment.
Fine. :happy: Would you please add [Solved] to the subject line of your first post, just in case others seeking for a similar clue.
Thanks
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
mystic
Forum Novice
Forum  Novice
Posts: 41
Joined: Tue Aug 21, 2018 1:37 am

Re: Mullvad vpn client issue [SOLVED]

#32

Post by mystic » Sun Dec 23, 2018 10:55 am

I went through the same issue yesterday when I switched to Mullvad, luckily Wireguard works flawlessly in MX which Mullvad provides. :number1:

User avatar
Hooten
Forum Novice
Forum  Novice
Posts: 75
Joined: Sat May 05, 2018 5:52 pm

Re: Mullvad vpn client issue [SOLVED]

#33

Post by Hooten » Sun Dec 23, 2018 11:24 am

mystic wrote:
Sun Dec 23, 2018 10:55 am
I went through the same issue yesterday when I switched to Mullvad, luckily Wireguard works flawlessly in MX which Mullvad provides. :number1:
Yes you can use Wireguard ofcourse, but if you want to use their client, follow the instructions that fehlix wrote in this thread. Works like a charm. :happy:

flugzeit
Forum Novice
Forum  Novice
Posts: 5
Joined: Wed May 22, 2019 9:49 am

Re: Mullvad vpn client issue

#34

Post by flugzeit » Wed May 22, 2019 9:58 am

fehlix wrote:
Thu Sep 27, 2018 12:53 pm

Command:

Code: Select all

/opt/MullvadVPN/resources/mullvad-daemon -v --disable-stdout-timestamps
If need to run this automatically after login,
we can prepare this later... :snail:
Hi there,
Thanks for this fix. I used it to successfully get Mullvad working on MX-18.
How can I set this up to run automatically after boot/login? Do I need a bash script and use /etc/init.d/.
Any advice would be much appreciated.
Thanks
-flugzeit

User avatar
fehlix
Forum Veteran
Forum Veteran
Posts: 3934
Joined: Wed Apr 11, 2018 5:09 pm

Re: Mullvad vpn client issue

#35

Post by fehlix » Wed May 22, 2019 12:24 pm

flugzeit wrote:
Wed May 22, 2019 9:58 am
How can I set this up to run automatically after boot/login? Do I need a bash script and use /etc/init.d/.
Please try the attached init-script for Mullvad VPN.
Download the attached tar file mullvad-daemon.init.tgz
Extract the init.d script:

Code: Select all

sudo tar -C / -xvzf mullvad-daemon.init.tgz
update init-service links

Code: Select all

sudo update-rc.d mullvad-daemon defaults

Code: Select all

sudo service mullvad-daemon start
Check status:

Code: Select all

sudo service mullvad-daemon status
Note: Actually I leave now the original install directory within '/opt/Mullvad VPN'
and to avoid "space" issue within the path I add an additional symlink like this

Code: Select all

ln -s '/opt/Mullvad VPN'  /opt/MullvadVPN
:puppy:
You do not have the required permissions to view the files attached to this post.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

flugzeit
Forum Novice
Forum  Novice
Posts: 5
Joined: Wed May 22, 2019 9:49 am

Re: Mullvad vpn client issue

#36

Post by flugzeit » Fri May 24, 2019 3:32 am

fehlix wrote:
Wed May 22, 2019 12:24 pm
Check status:

Code: Select all

sudo service mullvad-daemon status
Followed these steps and all worked perfectly!
fehlix wrote:
Wed May 22, 2019 12:24 pm
Note: Actually I leave now the original install directory within '/opt/Mullvad VPN'
and to avoid "space" issue within the path I add an additional symlink like this

Code: Select all

ln -s '/opt/Mullvad VPN'  /opt/MullvadVPN
Yes, I've implemented this, also.

Thanks so much for the help! Very much appreciated, and I hope to spend more time on the forum now that I've committed to MX Linux.

-flugzeit

Post Reply

Return to “General”