How to Update a Fedora Server

This guide explains how to update the packages on your Fedora server, how to tell whether a reboot is needed and how to have updates installed automatically. Fedora 41 and later use DNF5; the commands below are for these versions.

Which version are you using?

cat /etc/os-release

The PRETTY_NAME line shows the version, for example Fedora Linux 45.

Support status

Fedora releases have a short life: a new version comes out about every six months, and a version stops receiving updates about a month after the second version that follows it is released. As of November 2026, Fedora 45 (released on 3 November 2026) and 44 are supported; Fedora 43 will reach end of life soon. To keep receiving updates, you need to move to a new version about once a year.

Before you start

• Run the commands as root or with sudo.
• Take a backup. Backups are the customer's responsibility; for your server you can use our backup services or take a copy of the whole server with the System Copy add-on.
• Choose a quiet time. Some services restart during the update, and a kernel update needs a reboot.
• If you lose your SSH connection, you can still reach a VDS server from the console in the client area: Using the Console on a VDS Server.

Installing updates

1. See which updates are available:

   dnf check-upgrade

2. Install them:

   dnf upgrade

   Confirm with y and Enter.

If you only want security updates: dnf upgrade --security. To see the pending advisories: dnf advisory list.

Is a reboot needed?

dnf needs-restarting

In DNF5 the command says directly whether a reboot is needed (the -r option is no longer necessary). To list the services still using old files: dnf needs-restarting -s. If the command is not found, install it with dnf install dnf5-plugins. To reboot: reboot.

Installing updates automatically

In DNF5 the package and timer names have changed. Install the plugin:

dnf install dnf5-plugin-automatic

Set these lines in the [commands] section of /etc/dnf/automatic.conf (create the file if it does not exist):

[commands]
upgrade_type = security
apply_updates = yes

Turn on the timer:

systemctl enable --now dnf5-automatic.timer

By default the server is not rebooted; reboot = when-needed in the same section reboots it when an update needs it.

Troubleshooting

• "Waiting for process with pid … to finish": another dnf process is running (often the automatic update). Wait for it to finish.
• "Cannot download repomd.xml" or "Failed to download metadata": check the server's internet and DNS settings, then try again with dnf clean all and dnf upgrade.
• The server does not come back after a reboot: open the console in the client area and check the screen (Using the Console on a VDS Server). The boot menu usually still has the previous kernel. If you cannot solve it, you can open a support ticket from your client area.

The information in this guide is taken from official documentation: Fedora Linux 45, dnf5 upgrade, dnf5 check-upgrade, dnf5 needs-restarting, dnf5 automatic, Changes from DNF4.