The Settings of an Appvm application are not persistent between reboots

[unman]

4. Copy and paste the Mullvad VPN settings from the original configuration file, which is located in the Fedora template VM at the following path:
   /etc/mullvad-vpn/mullvad-vpn.conf

At point 1. you said that you should be working in the appVM where you
had installed Mullvad VPN, but now you refer to a “Fedora template VM”.
That’s quite confusing.

6. Type the following command to make the configuration file persistent:
   sudo qvm-service --add mullvad-vpn --opts config=/rw/config/mullvad-vpn.conf

This looks like nonsense.
qvm-service is a dom0 application, not available in an appVM.
It doesn’t have an --add option, and it doesn’t support use of --opts
like that. I don’t know what you were thinking of.

After following these steps, your Mullvad VPN settings should be persistent between appVM reboots.

No one will be able to follow these steps, and they certainly wont result in
VPN settings becoming persistent.
They are simply confused.

I never presume to speak for the Qubes team. When I comment in the Forum or in the mailing lists I speak for myself.