It’s “nano” 
Thanks for reporting the typo 
How can you update the qube? The normal update way for qubes always failes. Manually running sudo dnf update && sudo dnf upgrade returns something this:
Errors during downloading metadata for repository 'qubes-vm-r4.2-current':
- Curl error (6): Couldn't resolve host name for http://yum.qubesosfasa4z<i skip this part because i write the error manually>.onion/r4.2/current/vm/fc40/repodata/repomd.xml [Not resolving .onion address (RFC 7686)]
Error: Failed to download metadata for repo 'qubes-vm-r4.2-current': Cannot download rpomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
there are so many methods of installing VPN, wireguard, vpn app, networkmanager
can someone explain the underlying feature that makes the traffic go to VPN tunnel?
I understand it create wireguard interface for VPN, then traffic is sent there
how? does Linux firewall move traffic to VPN interface?
Some other setting in wireguard takes priority?
please explain!
You’re using onion repositories and they only work if you’re updating through Tor.
If you want to update through VPN then change the repositories back to the clearnet ones.
It’s adding the default route through VPN interface with higher priority than the route through eth0 interface.
Read about routing in linux.
Check the output of these commands:
ip rule
ip route
ip route show table VPN_TABLE_NAME_OR_ID
Does this Guide need an update? Since this morning I am unable to connect to any Mullvad servers. Everything was working fine when I followed this guide 2 months ago, however this morning no matter what country I select it is stuck on “Connecting” which never progresses from here. Sometimes it will say connected, however there is no connection on AppVM firefox browser?
I was reading that Mullvad has changed bandwidth/servers recently could this be the issue?
Hope there is a solution to get around this issue.
Thanks
The guide is really generic, it installs Mullvad app and block non VPN traffic. Even if Mullvad changed something, I don’t see how this would affect the setup (given they didn’t screw anything).
I followed this guide a few weeks ago, did all available updates, and the Mullvad VPN is still working well.
Maybe it’s just a temporary problem? I guess you have already checked that your account isn’t expired?
Thanks, @solene , for this and all your other guides. They are very useful, especially for a Qubes OS beginner like me 
@solene I think it might be to do with a large update they have going on right now. I have noticed on the Mullvad Icon it says “UPDATE AVAILABLE” however it directs you to there website to update it. How do we update mullvad without undoing all the works from this guide?
Many thanks
If you installed mullvad from the Fedora repository, you just need to update the qube where it’s installed:
- if you used a template, update the template
- if you have a standalone qube for the vpn, update it
the update command can be run manually without the qubes os update tool with sudo dnf upgrade
I have the standalone qube for the VPN. I tried using the update command as it’s fedora based as you specified sudo dnf upgrade I then restarted standalone mullvad qube and it still needs an update.
Anything else I can try?
what is the output of dnf list --installed | grep mullvad ?
Shows the following when I input that command:
mullvad-vpn.x86_64 2024.7-1
@mullvad-stable
Got it working @solene ended up updating to mullvads BETA repo using the following command and it’s working perfect now.
sudo dnf config-manager --add-repo https://repository.mullvad.net/rpm/beta/mullvad.repo
Thanks
Hello !
I have tried this tutorial on Qubes OS 4.1.
And everything seems to work except for the fact that connections to a Mullvad server last no more than 15 seconds before reconnecting (during approximately 15 seconds). During this period, I can use internet through the VPN but during the reconnexion, I can’t.
It is so frequent that it makes it unusable.
Do you have any idea to fix this ?
Thank you !
is this with openvpn or wireguard servers?
I used to be able to chain the VPN App VM on the standalone VPN (Mica Flee) method, sadly that no longer works for some reason with fedora 41 template/latest mullvad app.
Small change needed for Fedora 41 to install the repo
sudo dnf config-manager addrepo --from-repofile https://repository.mullvad.net/rpm/stable/mullvad.repo
You might also consider updating the inotify warning to include the command and make it stand out more
sudo dnf install inotify-tools
This might not be the right place to ask, but I figured it’s related enough. I followed this guide from privsec.dev to set up multiple Mullvad net qubes, and everything is working fine. Network works in all VMs with mullvad-vpn as their net qube. But I set the net qube of the mullvad-vpn qube to sys-whonix, abused the Wireguard UDP-over-TCP obfuscation feature to force TCP so the connection would work over Tor, and now specifically DNS is broken in the VMs using the mullvad-vpn net qube.
In the mullvad-vpn qube:
[user@mullvad-vpn ~]$ ping quad9.net
PING quad9.net (216.21.3.77) 56(84) bytes of data.
[...]
^C
--- quad9.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
[...]
[user@mullvad-vpn ~]$ ping 9.9.9.9
PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data.
[...]
^C
--- 9.9.9.9 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
In the VMs using mullvad-vpn as their net qube:
[user@disp4909 ~]$ ping quad9.net
ping: quad9.net: Name or service not known
[user@disp4909 ~]$ ping 9.9.9.9
PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data.
[...]
^C
--- 9.9.9.9 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
So network traffic in the VMs are being routed through AppVM --> Tor --> Mullvad --> 9.9.9.9 correctly, but DNS breaks once mullvad-vpn’s net qube is set to sys-whonix. DNS works fine inside VMs when mullvad-vpn’s net qube is set to sys-firewall. Maybe I’m missing something obvious. 