Mullvad-vpn not working after being included in manjaro repos

Support Software & Applications
1

Since the new stable release today (2026-02-23), mullvad-vpn is a package in the manjaro repositories.
Before this I was using the aur repository of the same name and it worked fine.
The new version does not appear to work on my system. The application can start, the daemon can start, but then in the application I cannot connect to the VPNs and I can’t even get the list of available servers.

Logs from the daemon:

Feb 24 13:00:24 hostname mullvad-daemon[1670]: [mullvad_daemon::management_interface][DEBUG] is_performing_post_upgrade
Feb 24 13:00:24 hostname mullvad-daemon[1670]: [mullvad_daemon::management_interface][DEBUG] app_upgrade_events_listen
Feb 24 13:00:24 hostname mullvad-daemon[1670]: [mullvad_daemon::management_interface][DEBUG] get_account_history
Feb 24 13:00:24 hostname mullvad-daemon[1670]: [mullvad_daemon::management_interface][DEBUG] get_tunnel_state
Feb 24 13:00:24 hostname mullvad-daemon[1670]: [mullvad_daemon::management_interface][DEBUG] get_device
Feb 24 13:00:25 hostname mullvad-daemon[1670]: [mullvad_daemon::management_interface][DEBUG] get_account_data
Feb 24 13:00:25 hostname mullvad-daemon[1670]: [mullvad_daemon::management_interface][DEBUG] get_settings
Feb 24 13:00:25 hostname mullvad-daemon[1670]: [mullvad_daemon::management_interface][DEBUG] get_account_history
Feb 24 13:00:25 hostname mullvad-daemon[1670]: [mullvad_daemon::management_interface][DEBUG] update_device
Feb 24 13:00:25 hostname mullvad-daemon[1670]: [hyper_util::client::legacy::pool][DEBUG] pooling idle connection for ("https", api.mullvad.net)
Feb 24 13:00:25 hostname mullvad-daemon[1670]: [hyper_util::client::legacy::pool][DEBUG] pooling idle connection for ("https", api.mullvad.net)
Feb 24 13:00:25 hostname mullvad-daemon[1670]: [mullvad_daemon::device][DEBUG] The current device is still valid
Feb 24 13:00:28 hostname mullvad-daemon[1670]: [mullvad_daemon::management_interface][DEBUG] get_version_info
Feb 24 13:00:28 hostname mullvad-daemon[1670]: [hyper_util::client::legacy::pool][DEBUG] reuse idle connection for ("https", api.mullvad.net)
Feb 24 13:00:28 hostname mullvad-daemon[1670]: [hyper_util::client::legacy::pool][DEBUG] pooling idle connection for ("https", api.mullvad.net)
Feb 24 13:00:28 hostname mullvad-daemon[1670]: [mullvad_daemon::version::check][DEBUG] Version data unchanged
Feb 24 13:00:28 hostname mullvad-daemon[1670]: [mullvad_daemon::version::check][DEBUG] Writing version check cache to /var/cache/mullvad-vpn/version-info.json
Feb 24 13:00:30 hostname mullvad-daemon[1670]: [mullvad_daemon::management_interface][DEBUG] connect_tunnel
Feb 24 13:00:30 hostname mullvad-daemon[1670]: [mullvad_daemon][DEBUG] Target state Unsecured => Secured
Feb 24 13:00:30 hostname mullvad-daemon[1670]: [talpid_core::firewall][INFO] Applying firewall policy: Connecting to { 123.456.789.0:44265/UDP }, Allowing LAN, interface: none. Allowing endpoint 45.83.223.196:443/TCP
Feb 24 13:00:30 hostname mullvad-daemon[1670]: [talpid_core::firewall::imp][ERROR] Expected 'mullvad' netfilter table to be set, but it is not
Feb 24 13:00:30 hostname mullvad-daemon[1670]: [talpid_core::tunnel_state_machine::connecting_state][ERROR] Error: Failed to apply firewall policy for connecting state
Feb 24 13:00:30 hostname mullvad-daemon[1670]: Caused by: Failed to set firewall rules
Feb 24 13:00:30 hostname mullvad-daemon[1670]: [talpid_core::firewall][INFO] Applying firewall policy: Blocked. Allowing LAN. Allowing endpoint: 123.456.789.0:443/TCP
Feb 24 13:00:30 hostname mullvad-daemon[1670]: [talpid_core::firewall::imp][ERROR] Expected 'mullvad' netfilter table to be set, but it is not
Feb 24 13:00:30 hostname mullvad-daemon[1670]: [talpid_core::tunnel_state_machine::error_state][ERROR] Error: Failed to apply firewall policy for blocked state
Feb 24 13:00:30 hostname mullvad-daemon[1670]: Caused by: Failed to set firewall rules
Feb 24 13:00:30 hostname mullvad-daemon[1670]: [mullvad_daemon][DEBUG] New tunnel state: Error(ErrorState { cause: SetFirewallPolicyError(Generic), block_failure: Some(Generic) })
Feb 24 13:00:30 hostname mullvad-daemon[1670]: [mullvad_daemon][ERROR] FAILED TO BLOCK NETWORK CONNECTIONS, ENTERED ERROR STATE BECAUSE: Failed to set firewall policy
Feb 24 13:00:56 hostname mullvad-daemon[1670]: [mullvad_daemon::management_interface][DEBUG] get_version_info
Feb 24 13:00:56 hostname mullvad-daemon[1670]: [hyper_util::client::legacy::pool][DEBUG] reuse idle connection for ("https", api.mullvad.net)
Feb 24 13:00:56 hostname mullvad-daemon[1670]: [hyper_util::client::legacy::pool][DEBUG] pooling idle connection for ("https", api.mullvad.net)
Feb 24 13:00:56 hostname mullvad-daemon[1670]: [mullvad_daemon::version::check][DEBUG] Version data unchanged
Feb 24 13:00:56 hostname mullvad-daemon[1670]: [mullvad_daemon::version::check][DEBUG] Writing version check cache to /var/cache/mullvad-vpn/version-info.json
Feb 24 13:00:59 hostname mullvad-daemon[1670]: [mullvad_daemon::management_interface][DEBUG] connect_tunnel
Feb 24 13:00:59 hostname mullvad-daemon[1670]: [mullvad_daemon][DEBUG] Target state Secured => Secured
Feb 24 13:00:59 hostname mullvad-daemon[1670]: [talpid_core::dns][INFO] Resetting DNS
2

The Arch Package Maintainer decided to completely revamp the packaging and removed the functions performed after an upgrade. Perhaps try the following which used to be done with the AUR package. Quit the Mullvad application first:

/usr/lib/mullvad-vpn/mullvad-setup prepare-restart
systemctl disable --now mullvad-daemon
systemctl disable mullvad-early-boot-blocking.service
sudo cp /var/log/mullvad-vpn/daemon.log /var/log/mullvad-vpn/old-install-daemon.log
sudo rm -f /var/cache/mullvad-vpn/relays.json
sudo rm -f /var/cache/mullvad-vpn/api-ip-address.txt
sudo chmod u+s "/usr/bin/mullvad-exclude"
systemctl daemon-reload
systemctl enable --now mullvad-daemon
systemctl enable mullvad-early-boot-blocking

EDIT: One can install mullvad-vpn-bin from the AUR that still contain those functions.

2 Likes
6

@mAritz I forgot to mention the following and snuck in an edit above:

7

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.