Fedora Server Administration Guide

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

Where Fedora Server sits

Fedora Server is upstream of CentOS Stream and RHEL. Releases are short. A server on Fedora is a server you intend to upgrade often, or a lab. It is a weak choice for a host that must sit still for five years. If that is the requirement, use a rebuild or RHEL and their pillars.

dnf, NetworkManager, firewalld, and SELinux enforcing are the family tools. hostname edge-01, lab address 192.0.2.10/24 via 192.0.2.1, named admin and a key. Replace the address outside the lab.

Upgrades between Fedora releases are planned events with a backup and a reinstall path. They are not something unattended updates should surprise you with on a Friday.

The software is newer. A third-party module that only supports a RHEL minor version may not belong here. Check that before you promise the application.

The first hour on a lab host

Step 1 on Fedora Server covers the release. Record the Fedora version and its end-of-life from the lookup. Without the date, the host will expire in silence. The check is: The date is in the ticket. If that check fails, stop and fix the ticket before the next step. The way back is the previous file or the previous image, which the provisioning guide told you to keep. Do not install a second package to hide a failed step. The browser generators for Fedora Server draft a starter. They do not log in. Read the draft, delete what this lab does not need, and replace prompt-for-this. A line that worked on a different distribution is not a reason to paste it here.

Step 2 on Fedora Server covers admin. Named user and key. Same as the rest of the family. The check is: Key login works. If that check fails, stop and fix the ticket before the next step. The way back is the previous file or the previous image, which the provisioning guide told you to keep. Do not install a second package to hide a failed step. The browser generators for Fedora Server draft a starter. They do not log in. Read the draft, delete what this lab does not need, and replace prompt-for-this. A line that worked on a different distribution is not a reason to paste it here.

Step 3 on Fedora Server covers network. nmcli and firewalld for the lab prefix. A desktop NetworkManager profile left unmanaged is still a config. The check is: The address survives a reboot. If that check fails, stop and fix the ticket before the next step. The way back is the previous file or the previous image, which the provisioning guide told you to keep. Do not install a second package to hide a failed step. The browser generators for Fedora Server draft a starter. They do not log in. Read the draft, delete what this lab does not need, and replace prompt-for-this. A line that worked on a different distribution is not a reason to paste it here.

Step 4 on Fedora Server covers SELinux. Enforcing. Newer policy is not a reason to turn it off. The check is: getenforce is Enforcing. If that check fails, stop and fix the ticket before the next step. The way back is the previous file or the previous image, which the provisioning guide told you to keep. Do not install a second package to hide a failed step. The browser generators for Fedora Server draft a starter. They do not log in. Read the draft, delete what this lab does not need, and replace prompt-for-this. A line that worked on a different distribution is not a reason to paste it here.

Step 5 on Fedora Server covers the next upgrade. Write when you will move to the next Fedora or leave for a longer-lived OS. A lab that became production needs that sentence immediately. The check is: The sentence exists. If that check fails, stop and fix the ticket before the next step. The way back is the previous file or the previous image, which the provisioning guide told you to keep. Do not install a second package to hide a failed step. The browser generators for Fedora Server draft a starter. They do not log in. Read the draft, delete what this lab does not need, and replace prompt-for-this. A line that worked on a different distribution is not a reason to paste it here.

# Fedora Server lab. Review before you paste.
# Short lifecycle. Record the release number.
# dnf, firewalld, SELinux Enforcing.
# Lab address 192.0.2.10/24 via 192.0.2.1.
# prompt-for-this is not a password to keep.

The commands you will actually repeat

dnf update regularly. Read it. Reboot for kernels. The patch guide still wants a canary if more than one host exists.

When the release approaches end of life, the lookup on the patch guide should already be on the calendar. A Fedora host past that date is the migration, not a frozen museum.

firewalld allows the management prefix. SELinux stays enforcing. Do not disable either because a newer userspace denied something unfamiliar.

Keep the release number in the inventory. Fedora 40 and Fedora 41 are not a minor patch apart in the way a RHEL minor is.

What Fedora Server is not

Fedora is not a long-term server platform unless your process loves upgrades.

It is not RHEL with newer packages. Vendors who certify RHEL did not certify this host.

It is not Rocky or Alma. Do not add their repositories for one library.

The hour you stop

Write the hostname, the role, and the clock time before you change Fedora Server. If this host is also serving users, it is not the lab and this first hour belongs on a spare. The provisioning guide is how the spare gets built. A change without a spare is a change you can still postpone.

Keep the console or the out-of-band path open for the whole hour. Reloading a network service, a firewall, or a secure-shell daemon from the only session is how a lab becomes a drive across town. The hardware guide names that path for a physical machine. A virtual machine uses the hypervisor console. A cloud instance uses the serial console the platform gives you. Test it before the reload, not after.

The address 192.0.2.10/24 and the gateway 192.0.2.1 are documentation. They belong in the lab note and nowhere else. On a real network, use the prefix the network desk already assigned. On a cloud instance, use the address the platform assigned and do not hard-code the documentation range into user-data. If a generator filled the documentation address into a production draft, delete it.

prompt-for-this is a reminder that a secret is missing. It is not a password you set, not a token you commit, and not a string you leave in a configuration file because the service started. The real secret lives in the password store. The ticket says who can read it. A file that still contains the reminder is a file you have not finished.

One service is enough for the first hour on Fedora Server. The purpose from the fundamentals page says which service. Every other package stays uninstalled until its own guide has a ticket. A host that enables a web server, a database, and a queue in the first hour has three changes and no proof. Finish the login, the address, and the update. Then stop.

Read the package transaction before you accept it. A count of packages is not a review. If the list contains a repository you did not add, stop. If it contains a kernel, the patch guide's reboot decision applies and the console stays open. If it contains software this role does not need, remove that line from the plan rather than installing it and disabling it later.

The previous image, the previous configuration file, or the previous package version is the rollback. Write the path down while the host still works. A rollback you invent after a failed reload is a guess. The migration guide assumes the old copy is still there. Do not delete it in the same hour to free a disk.

When the checks pass, copy the notes into the ticket and leave the host alone. The next host waits until a second person can repeat the login and the address from the notes. A fleet built from memory drifts. A fleet built from the file the provisioning guide stored stays boring, which is the point of Fedora Server in production.

If a step on Fedora Server fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a host nobody can rebuild. Rebuild from the image instead. The time you lose is smaller than the time you will spend explaining the hybrid.

Hand the finished lab to the guide that matches the role: web, mail, storage, backup, or hardening. Fedora Server being installed is not the same as the role being ready. The role guide has its own proof. Do not skip it because the package manager exited without an error.

A second person reads the hostname, the address, and the rollback path aloud before you build the next host. If they cannot find those three in the ticket, the notes are not done. Silence is not agreement. The check is the sentence they repeat back.

Store the working notes next to the image version. A month from now Fedora Server will still boot from that pair, and the chat where you remembered a flag will be gone. The file is the memory. The host is replaceable. That is the whole point of writing this hour down.

Fedora Server checks before a second host

Confirm this before you call the change done: Fedora Server is the OS the hostname reports, not a neighbour you copied from. The lab address 192.0.2.10/24 is gone before this host is placed on a real network. prompt-for-this is not the password that was set, and no password is in the ticket. The named admin can log in with a key. The package manager used is the one this page names. A network file from a different distribution was not pasted in. The config test or the apply command for this network tool succeeded. The previous image or install file is kept. No new third-party repository was added in the first hour. A service you do not need was not enabled to see what it does. Console or out-of-band access works before you reload SSH. A second person read the hostname and the address. The Fedora release number and end-of-life date are filed. A long-lived production role was not placed here by accident. SELinux is Enforcing. And no RHEL rebuild repository is mixed in. If one of those fails, stop.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

Guides in this cluster

These supporting pages belong to this pillar.