Hello again! The default-mgmt-dvm template is: debian-12. I’m guessing this needs to be debian-13 ?? I will wait to change it until you confirm. I didn’t know it existed or purpose until you mentioned it. I thought the default-dvm template was involved. Sorry.
I am uploading the log files to hopefully save you from having to dig out an old install. Hope this helps! ( I didn’t see anything confidential in them). They’re not big, but very informative! They explain much better than what I was trying to say.
3isec-mullvad-vpn-pkg-install-ERRORS.log (11.4 KB)
mgmt-template-mullvad.log (8.7 KB)
mgmt-sys-mullvad.log (3.1 KB)
Thanks for taking the time!! I know you’re probably very busy with v4.3 and other things.
I moved ahead and left the default-mgmt-dvm template set to debian-12 while instead I set each of the 3 qubes involved individually to management-dispVM to debian-13. I then used apt to purge and reinstall mullvad-vpn but had no effect. I then kept searching through the log with journalctl looking for StartApp+mullvad. It appears debian-13-minimal is missing some shared object files:
libnspr4
libnss3
I installed those and I am now able to load the mullvad-gui both in sys-mullvad and in disposables using mullvad-dvm.
Wrapping this up…this seems to work fine as a basic vpn setup. It is nice to be able to run either the browser and/or the gui within a disposable vm. However there are some functional caveats versus my previous standalone sys-vpn appVM setup created using some earlier docs.
- The Multihop functionality does not work well. The multihop is so slow it is unusable and mostly times-out.
- Under the gui vpn settings, DNS content blockers are unable to be used. This is understandable since ‘update_dns.nft’ creates dnat chains specifically for 10.64.0.1 and the dns content blocking uses other dns I believe. So maybe some tweaks here in the update_dns file can add some of that functionality back? Probably not necessary for a basic vpn setup.
- Using DAITA didn’t seem to have a problem. Still able to access internet.
- There may be other things that may/may not work. I only tested what I used most in my previous setup. Perhaps things will be different in someone else’s setup? (Or maybe an uninstall and reinstall might give better results? idk)
Since it is currently up and running, I will probably keep it for a backup vpn installation despite the slightly reduced functionality. I was disappointed to see multihop pretty much breaks with this setup, but figuring it out is beyond my knowledge level and time I want to spend on it.
Alternative:
Instead I revisited my fedora 41 standalone vpn install originally based on @solene setup guide found here: Mullvad VPN 4.2 setup guide .
I found the earlier fail with curl errors for my in-place upgrade of fedora41 to fedora42 was due to a ‘newbie’ error whereas the mullvad-vpn installation early blocking service was working even with both mullvad services stopped. So I uninstalled mullvad-vpn and the inplace upgrade sailed on through! After the upgrade, I reinstalled mullvad-vpn, rechecked files to be sure that changes still existed from Solene’s quide and setup the gui to mullvad and all functionality was available as was in my earlier install such as dns content blockers, multihop, quantum resistance and daita. Tested successful with other appVM using it. 
So this is a great option available to use as well as the 3isec qubes package.