early boot blocking service prevents api connection on first signin

[secretmango]

Is it a bug?

• [X] I know this is an issue with the app, and contacting Mullvad support is not relevant.

I have checked if others have reported this already

• [X] I have checked the issue tracker to see if others have reported similar issues.

Current Behavior

Install MullvadVPN on Fedora Atomic Desktops. The postinstall script doesnt seem to start.

After reboot the RPM is added and I enable the 2 systemd services, mullvad-daemon and mullvad-early-boot-blocking.

Then I tried to log in but could not connect to the API. It mentioned a firewall issue, so I enabled wireguard in firewalld-gui, didnt change anything (the changes apply live)

I tried pinging 1.1.1.1 but the action was blocked, dns was also not working.

I disabled early boot block, rebooted and suddenly had internet, could log in, and then could enable early boot block again

Expected Behavior

Early boot block should not be active before being logged in, or somehow allow logging in.

Steps to Reproduce

1. Install on Fedora Silverblue/Kinoite/other
2. Reboot
3. Enable the 2 services
4. Try to log in
5. Disable early boot blocking
6. Reboot
7. Try to log in again
8. Log in
9. Enable early boot blocking again

Failure Logs

No response

Operating system version

Fedora 40

Mullvad VPN app version

latest stable from repo

Additional Information

No response

[raksooo]

The firewall rules set by the early boot blocker are active until the daemon starts. If the daemon isn't starting properly the early boot firewall rules will still apply. Is the daemon starting up properly? Do you get any error messages in the logs? If you send a problem report from within the app we will receive logs that help us understand the issue.

[secretmango]

all I can say is that I installed it, rebooted, enabled mullvad-daemon.service and mullvad-early-boot-blocking.service and then tried to log in in the app. There should have been no reason for the daemon to not start.