Fedora
Fedora on a dedicated server: the version the panel offers, how short the support window is, and when another distribution is the better answer.
Fedora is where the Red Hat family tries things first: recent kernels, recent toolchains, and a release every six months. On a workstation that is the point. On a server it is a commitment to upgrade roughly every year.
Install it from the panel
In the client area, open your server, then Reinstall the server. Pick the Fedora tile, open its version list and choose the one you want, then fill in the partitioning, the software RAID, the hostname and the password below the grid. The form itself is described in reinstalling your OS.
This tile carries a single version, Fedora 32, with no list to open. That release is long past its support window, so treat it as a base for a short lived experiment, not for anything exposed to the internet.
Careful
A reinstall erases every drive in the machine. There is no undo and we keep no copy: take your backups off the server first.
Before you pick it
A Fedora release is supported for about thirteen months. After that it stops receiving security updates entirely: there is no LTS branch to fall back on, which is the deliberate trade for how current the packages are.
For a server you intend to leave alone, the better answers are AlmaLinux or Rocky Linux in the same family, or Debian outside it. Pick Fedora when you specifically need something newer than they carry, and plan the upgrades.
First steps
dnf upgrade --refresh
dnf install -y curlThen your own user and no password logins, per first connection.
The family defaults apply
firewalld runs from the first boot, SELinux is enforcing, and the interfaces are driven by NetworkManager through nmcli. All three behave as described on AlmaLinux.
cat /etc/fedora-release
firewall-cmd --list-all
getenforceNote
Need something newer than the tile offers? Upload your own installer image from the ISO Upload tab and run the installer over the console. Anything we do not carry as a template installs that way.
Where to go next
- First connection: your own user, SSH keys, password logins off.
- IP addresses: configuring the additional addresses on the fresh system.
- The console: watching the install, and getting in when the network does not answer.
Reviewed on September 15, 2026