Mullvad System Service Can't Be Contacted (Linux)
Quick answer
The Mullvad app is only a front end for the mullvad-daemon service. If the app says it can't contact the system service, start or restart the daemon with systemctl and check its verbose output.
Most likely fix: Start or restart the daemon
How to fix it
Try these in order — the most common fix is first.
1. Start or restart the daemon
- Run: sudo systemctl enable --now mullvad-daemon
- If it's stuck after an update: sudo systemctl restart mullvad-daemon
Did this fix it?2. Read the daemon's error
- Run: sudo /usr/bin/mullvad-daemon -v
- Check the output for the failing step
Did this fix it?3. Reload AppArmor
- Run: sudo apparmor_parser -r /etc/apparmor.d/mullvad
- Start the app again
Did this fix it?4. Reinstall from the official repository
- Remove community packages that ship a broken service
- Install Mullvad's official .deb/.rpm or repository package
Did this fix it?
Symptoms
The app opens but says it's unable to contact the Mullvad system service, often after an update or on Arch/Fedora Silverblue.
Why it happens
- mullvad-daemon isn't enabled or crashed
- The daemon is stuck after an update
- Missing systemd service file (seen on immutable distros and some AUR packages)
- AppArmor profile not loaded
This guide also covers
- mullvad system service can't be contacted
- mullvad daemon not running
- mullvad-daemon failed linux
Still not working?
If Mullvad VPN keeps failing, you're not alone. See every Mullvad VPN problem users report or the alternatives people switch to.
Need a custom web app or internal tool? Our small team builds it, on your domain or hosted by us. Price agreed together.
Get a quote