Article Summary:

Installing Fedora Server on a rented remote hardware is subject to some restrictions and peculiarities that result from the placement in a remote and inaccessible data center, as well as from specific security measures taken by the providers. For other main stream distributions, there are many descriptions. For Fedora / CentOS / RHEL, information is sparse and often outdated.

This article uses Hetzner as an example to show how these special features can be implemented exclusively with Fedora resources as part of a Server installation.

Article Description:

This article is intended to be the first in a planned series of “Fedora Server Edition Use Cases”, which will be created in collaboration with other members of the Fedora Server Edition Working Group.

Planned articles, some of which are already nearly finished:

• “Fedora Server as a modern, fully featured multi domain mail server”
  Such articles are available in large numbers for Debian and derivatives, but very rarely for Fedora.
  coming in 5 parts
  1. Requirements and system configuration
  2. Basic mail service (Postfix, Dovecot, Post Screen, SNI, auto-configuration support)
  3. Gaining trust, OpenDKIM, Dmarc, SPF
  4. Defending against spam and viruses, Amavis, ClamAV, milter
  5. Managing e-mails using Sieve
• “Fedora Server as a hosting server”
  featuring customer manged system container to let user log in and work on their own without having to be a system user.
• “Fedora Server as a home server and NAS replacement”
  Includes a comparison of affordable hardware platforms x86 MiniPCs and aarch64 SBCs
• “Using Fedora as a single login server using LDAP”

Note the discussion here:
https://discussion.fedoraproject.org/t/fedora-server-edition-on-rented-root-server-hardware-the-example-of-hetzner/132153