mirror of https://github.com/RWejlgaard/pez-docs.git synced 2026-05-06 03:34:44 +00:00

Pez 8e7269611d Update docs to reflect current setup (March 2026)

- Add Hetzner Cloud location (helsinki-a, nuremberg-a)
- Update london-a to FreeBSD, london-b ZFS layout to 3x raidz1
- Note offline servers (london-c, copenhagen-b)
- Update Plex docs with accurate ZFS and exporter behaviour
- Add workload docs: Nextcloud AIO, Navidrome, slskd, Monitoring,
  Auth (Authelia/LLDAP/Bitwarden), Mail (poste.io), Gaming (Minecraft/MaNGOS)
- Update README/intro with current service and location index

2026-03-04 09:09:08 +00:00

1.4 KiB

Raw Blame History

Hetzner Cloud

In contrast to the rest of the homelab which is entirely on-prem, I run two cloud servers on Hetzner for services that need a clean, reliable public IP — particularly the mail server (which really doesn't work well from residential addresses) and the traffic gateway.

Hetzner is my cloud provider of choice. Good prices, solid reliability, and datacenters in Germany and Finland.

Both servers are connected to the rest of the homelab via Tailscale, same as everything else.

Servers

helsinki-a

The main traffic gateway. All inbound HTTP traffic hits this server first and gets proxied where it needs to go via Caddy. Also runs the auth stack — Authelia, LLDAP, and Bitwarden.

Having the gateway on a cloud server with a clean IP keeps my home IP off DNS records and gives me flexibility to route traffic regardless of what's happening on-prem.

Running services:

Caddy (reverse proxy)
Authelia (SSO / authentication middleware)
LLDAP (lightweight LDAP, used by Authelia as the user directory)
Bitwarden (self-hosted password manager)

nuremberg-a

Dedicated mail server. Running poste.io in Docker, which bundles Postfix, Dovecot, and a web admin interface into a single container. Having mail on a Hetzner server with a proper PTR record and no residential IP baggage makes deliverability significantly easier.