I guess it should work, but upgrade from 38 to 39 and 39 to 40, do not try 38 to 40 directly.
The procedure for upgrading a Fedora standalone is the same as for a template.
1 Like
Thanks for this great guide
I used this to build a template based on a clone of debian-12-minimal, because I donāt like Fedora much 
Iām not an authority on this, please use with caution and test it before relying on it for strong privacy
You will need to add the following for ivpn-ui to work:
apt-get install libatk-bridge2.0 libatk1.0-0 libnss3 libcups2 libgtk-3.0 libasound2
If you leave out this next step on a debian-minimal vm, you wonāt see the option to āSettings->DNS->Force management of DNS using resolv.confā
apt-get install systemd-resolved
A few other notesā¦
The setting mentioned for starting at boot is (specifically) two settings
Settings->General->Autoconnect->On launch(to connect VPN when app starts)Settings->General->Autoconnect->Allow background daemon to manage autoconnect(to start app at boot, via systemd)
There are quite a few settings in the IVPN app, Iām testing with a few of these:
Enabled for Settings->IVPN Firewall->Always-on firewall
Disabled for Settings->IVPN Firewall->Allow LAN traffic when IVPN Firewall is enabled
Enabled for Settings->IVPN Firewall->Allow access to IVPN servers when Firewall is enabled
Iām not sure I understand what the last option means exactly - possibly that it will have an exception to communicate with IVPN HTTP API even if the tunnel is down and IVPN Firewall is on. Not sure how helpful it is to have it or how much of a hassle it is to disable it