Skip to content

Self-hosted services overview

Status

Active — home lab: media, automation, passwords, DNS, VPN overlay (Tailscale), and shared reverse-proxy access.

Hardware

Machine Model Ubuntu Role
Seamoth Macmini6,1 (late 2012) 26.04 Home stack: Jellyfin, Home Assistant, media stack, Drop, DroppedNeedle, slskd, Tdarr (8265; transcode worker on Aurora), Technitium DNS (primary, LAN DNS), acme.sh wildcard cert (~/docker/acme), Cloudflare DDNS, Tailscale exit node, Watchtower
Prawn Macmini5,1 (2011) 24.04 Game servers (Minecraft), Technitium DNS (secondary, mirroring Seamoth), Watchtower, Tailscale member (tag:gameserver), ABB backup target. Back online 2026-10-22; 100% CPU fixed (Minecraft heaps lowered)
Leviathon Synology DS216+II (DSM 7.1.1-42962 Update 9) — Vaultwarden, Gotify, Pixel Place API, reverse proxy, NFS /volume1/media, UPS host, Tailscale subnet router, seamoth-backup rsync destination, static /volume1/web/homelab/ jump page + /volume1/web/projects-wiki

Full service matrix: projects/Homelab-Mac-Mini-Hosts.

Prawn (2026-10-22): came back online after being offline since ~mid-September. The 2026-09-26 note was Tailscale 100.91.255.109, tag:gameserver, offline for ~13 days. All CPU threads were pinned at 100% because of memory pressure: three Minecraft servers had 15G of heap on 15 GiB of RAM. Heaps were lowered to Paper 1G/3G, RLCraft 1G/4G, abyssal-ascent 1G/4500M (fixed, 2026-10-22). CPU now runs about 78–86 °C; cleaning the fan is suggested. projects/Game-Servers.

How things run (Docker vs DSM)

  • Docker on the Mac minis hosts app stacks per host (home on Seamoth, games + secondary Technitium DNS on Prawn); Vaultwarden and related apps on Leviathon (Container Manager).
  • Not Docker: Tailscale is installed as the official Synology DSM package on the NAS.
  • Not Docker: External HTTPS to Jellyfin, Home Assistant, and Vaultwarden goes through Synology’s built-in reverse proxy (Application Portal / Login Portal). The proxy itself is DSM-native. As of 2026-10-27 the Let’s Encrypt wildcard for kiefermenard.com is issued by acme.sh in Docker on Seamoth and deployed onto those reverse-proxy entries — #wildcard-certificate-2026-10-27.

Jellyfin (media server)

Host Seamoth — Macmini6,1, Ubuntu 26.04, 10.0.0.20
Purpose Primary media server for movies, TV shows, music, and books.

Details

  • Runs in Docker on Ubuntu Server (faster hardware for transcoding).
  • Media library on Synology NAS, mounted via NFS at /mnt/media (export 10.0.0.10:/volume1/media on Leviathon). If Seamoth’s LAN IP changes, update Control Panel → Shared Folders → NFS Permissions on the NAS.
  • Configuration, cache, and metadata stored locally on the Mac Mini.
  • Reached from the internet via Synology reverse proxy (HTTPS).

Automation stack: Radarr, Sonarr, Prowlarr, qBittorrent/VPN, Bazarr, Lidarr, Mylar3, Bookshelf (Readarr fork), Seerr (public hostname still jellyseerr.kiefermenard.com) — see projects/Media-Automation-Stack-Seamoth (~/docker/media-stack, same NFS mount pattern).

Tdarr (2026-10-28): the server stays on Seamoth at http://10.0.0.20:8265. Transcoding runs on a remote worker on Aurora (RTX 5070). The libraries hold new files for 31 days and skips hardlinked (still-seeding) files. Movies rules re-encode H.265 only above about 8 Mbps at 1080p — to save space on bloated H.265, not to skip H.265. The homelab media library is close to 1 TB and server storage is getting tight. projects/Media-Automation-Stack-Seamoth#tdarr-2026-10-28.

NFS + Docker: the Jellyfin compose file should use a bind mount with propagation: shared for /mnt/media → /media. Docker’s default bind does not propagate submounts; without shared, the host can ls /mnt/media but the container sees an empty /media.

volumes:
  - ./config:/config
  - ./cache:/cache
  - type: bind
    source: /mnt/media
    target: /media
    bind:
      propagation: shared

URLs

Kind URL
Short https://jf.kiefermenard.com
Full https://jellyfin.kiefermenard.com
Internal http://10.0.0.20:8096

Home Assistant

Host Seamoth — Macmini6,1, 10.0.0.20
Purpose Home automation and smart-home hub.

Details

  • Runs in Docker on the same Ubuntu Server as Jellyfin.
  • All data (configuration, database, history, integrations) stored locally on the Mac Mini (no NAS mount).
  • External access via Synology reverse proxy (HTTPS).
  • menu.json in www/: automated deploy from a MacBook (Vaultwarden SSH agent → scp + docker compose) — projects/Home-Assistant-menu-json-deploy. That Garmin/HA file is not the Leviathon homelab jump page (below).

URLs

Kind URL
Short https://ha.kiefermenard.com
Full https://homeassistant.kiefermenard.com
Internal http://10.0.0.20:8123

Dorm Home Assistant (Aurora)

Host Windows PC Aurora (campus dorm network, not the home LAN). Home 10.0.0.x is reachable only through Leviathon over Tailscale
Access Tailscale http://100.107.146.20:8123 (linked from the homelab jump page)
Runtime HA Docker container homeassistant on WSL; Zigbee stick via usbipd
Notes Separate instance from Seamoth HA. Jump-page / wiki-deploy facts from 2026-09-08 still apply. Hardware, GPU/CPU overclock, and the 2026-10-06 Ollama / Open WebUI stack: projects/Aurora-Gaming-PC. Tailscale Serve on Aurora keeps Home Assistant on https :443. Open WebUI is http://aurora (:80 → 3000).

Zigbee USB auto-reattach

Aurora passes a Silicon Labs CP210x stick (10c4:ea60, BUSID often 2-17, COM3, usbipd-bound Shared) into WSL/Docker. The HA container mounts /dev/ttyUSB0.

usbipd bind persists across Windows reboots; attach does not. After every Windows restart the stick must be re-attached, and the HA/Zigbee container often restarted.

The auto-reattach script targets docker-desktop WSL (not Ubuntu WSL) and loads the cp210x driver so the stick appears as /dev/ttyUSB0 in Docker’s WSL.

Script C:\Users\kiefe\homelab\attach-zigbee-wsl.ps1
Launch Windows Startup folder (hardware ID + --auto-attach, wait for /dev/ttyUSB0, then docker restart homeassistant)
Log C:\Users\kiefe\homelab\zigbee-usbipd.log
Dropped Scheduled task Zigbee-WSL-AutoAttach — tried, then dropped for elevation issues

Presence lighting (live)

Desk lamp light.table_lamp is wired into the awake occupancy and leave-asleep restore path with the presence LED. Spare bulb light.lamp_bulb remains device-disabled. Asleep night light stays presence LED only.

Helpers: input_boolean.asleep, input_boolean.room_occupied, input_number.presence_awake_brightness (1–255, default 255). Asleep/Awake is currently manual (dashboard / Helpers); nothing auto-flips it yet.

presence_awake_brightness is saved when entering Asleep (if the LED is on) or when awake occupancy clears. The ~15% night light does not overwrite it. Leave-asleep and awake occupancy on restore light.presence_sensor to that saved brightness.

Mode Behavior
Awake (Asleep off) Occupancy on → light.table_lamp + light.presence_sensor on (LED at saved awake brightness); occupancy clear 1 min → off
Leave asleep Turning Asleep off while occupancy still on turns on light.table_lamp + light.presence_sensor (LED restored to saved brightness) and sets Room occupied (Dorm leave asleep)
Enter asleep Turns off both lights; still triggers SignalRGB sleep
Asleep night light binary_sensor.motion_sensor on → light.presence_sensor ~15% only (desk lamp stays off); motion clear 2 min → off

Live automations (enabled): Dorm awake presence on/off, Dorm asleep night light on/off, Dorm enter asleep, Dorm leave asleep.

Open loop: air purifier airflow can cause false mmWave presence; R3 sensor reportedly lacks zone masking.

SignalRGB Asleep bridge (confirmed working)

Aurora Asleep drives free SignalRGB via a Windows HTTP bridge on port 18765. Confirmed working via the HA Asleep toggle.

Script C:\Users\kiefe\homelab\signalrgb-asleep-bridge.ps1 (+ Startup VBS)
Config C:\Users\kiefe\homelab\signalrgb-asleep.conf
HA rest_command.signalrgb_sleep / signalrgb_wake → host.docker.internal
Sleep Applies Good Night!
Wake Restores Sakura

The apply script installs the effect if needed. Uses the URL protocol (not Pro API); SignalRGB must already be running.

Homelab jump page (Leviathon)

Whole-homelab HTML menu (full media stack + infra, not media-only). Chosen host is the NAS. A temporary Python menu on Seamoth :8888 was tried in the 2026-09-08 CS Lab session and then removed.

Host Leviathon (Synology)
Path /volume1/web/homelab/
LAN URL http://10.0.0.10/homelab/
Remote Same folder via Leviathon Tailscale IP 100.72.52.29

Coverage (as of 2026-09-08): qBittorrent and arr ports on Seamoth 10.0.0.20 (projects/Media-Automation-Stack-Seamoth); Jellyfin / Home Assistant (Seamoth); Pi-hole (removed 2026-10-23); Vaultwarden; Gotify LAN + public; iGotify https://igotify.kiefermenard.com; dorm HA on Aurora; this wiki; DSM; Tailscale admin.

Early October: DroppedNeedle and slskd were added to this links page. Uptime Kuma at https://status.kiefermenard.com monitors the homelab.

qBittorrent Referer: menu links use rel=noreferrer. Without it, qBittorrent’s Web UI returns 401 Unauthorized when the Referer is cross-origin from the jump page.

Drop cards (2026-10-03): /volume1/web/homelab/index.html now has LAN and public cards for Drop (backup index.html.bak-20261003-083926). See projects/Drop.

Drop (private clipboard)

Self-hosted private clipboard on Seamoth. Paste text or drop a file in a signed-in browser and it shows up on that account's other devices. Friends get separate accounts and cannot see each other's items. Accounts, limits, and the accepted host-compromise limit: projects/Drop.

Compose /home/kiefermenard/docker/drop
Image Built locally as drop-drop
Service drop
Listen Container 8080; host 8095 (8080 is already Gluetun)
Data Volume drop_drop-data, path /data (SQLite ciphertext)
LAN http://10.0.0.20:8095
Public name https://drop.kiefermenard.com
DNS Favonia (cloudflare-ddns) already updates that name
Reverse proxy Leviathon rule not added. Still needs http://10.0.0.20:8095 with WebSockets and X-Forwarded-Proto, X-Forwarded-Host, and X-Real-IP

No public signup. SETUP_SECRET is an env var used once at /setup to create the admin username and password. The password is not the setup secret.

Vaultwarden (Bitwarden-compatible)

Host Synology DS216+II (Docker via Container Manager)
Purpose Self-hosted password manager compatible with official Bitwarden clients.

Details

  • Runs in Docker on the NAS (Container Manager).
  • Database, attachments, and icons live on the NAS under the docker/vaultwarden folder.

URLs

Kind URL
Short https://vw.kiefermenard.com
Full https://vaultwarden.kiefermenard.com
Admin https://vw.kiefermenard.com/admin

Clients

  • Web vault, browser extension, and desktop clients work as usual.
  • iOS: “Log in with device” works reliably.

Pi-hole (network-wide ad blocking) — removed 2026-10-23

Historical: Pi-hole was removed from both Seamoth and Prawn on 2026-10-23; Technitium DNS (below) replaces it.

Two Docker Pi-hole instances on the home LAN for redundancy.

Primary (Seamoth)

Host Seamoth — 10.0.0.20
Purpose Primary DNS for the home network (router DNS1).
Admin UI http://10.0.0.20/admin
DNS 10.0.0.20

Secondary (Prawn)

Host Prawn — 10.0.0.21
Purpose Backup DNS (router DNS2); same blocking goal if Seamoth is down.
Admin UI http://10.0.0.21/admin
DNS 10.0.0.21

Sync: use Pi-hole Teleporter (export on primary, import on secondary) or keep adlists aligned manually. No public hostname for either instance.

2026-10-23: both Pi-holes removed; Technitium (below) serves LAN DNS.

Technitium DNS (2026-10-22)

Technitium DNS (Docker) is serving homelab DNS (cutover done, confirmed 2026-10-27). Seamoth 10.0.0.20 is the primary (ports 53 and 1053). Prawn 10.0.0.21 is the secondary (port 53) and mirrors zones from Seamoth (10.0.0.20:1053). Pi-hole was removed from both hosts on 2026-10-23.

Confirmed as DNS for Snowfox, which reaches it over the tailnet via Tailscale’s DNS setting. The API/web UI is reachable only on the LAN IPs (port 5380), not localhost.

Local .home names exist: seamoth.home, prawn.home, leviathon.home.

Split horizon (2026-10-27): 21 kiefermenard.com zones (LAN shortcuts that send service subdomains straight to Leviathon) were re-enabled once Leviathon stopped serving its default leviathon.synology.me certificate on local connections. The ab, abyssal, mc, and rlcraft zones remain disabled.

Wildcard certificate (2026-10-27)

acme.sh running in Docker on Seamoth (~/docker/acme) issued a Let’s Encrypt wildcard certificate for kiefermenard.com. It is assigned to Leviathon’s DSM reverse-proxy entries. It auto-renews and redeploys to DSM using a dedicated DSM user. That replaces the default leviathon.synology.me certificate Leviathon was serving on local connections, which caused certificate mismatch errors in Uptime Kuma and browsers.

Cloudflare SSL mode for kiefermenard.com is Full (strict). The homelab service subdomains work with it. Open: the main website (kiefermenard.com / www on Leviathon) was still serving a self-signed certificate and was being investigated. projects/Personal-Website.

Uptime Kuma

https://status.kiefermenard.com monitors the homelab. It saw leviathon.synology.me certificate mismatches when LAN shortcuts sent kiefermenard.com names straight at Leviathon. The wildcard on the DSM reverse proxy is what fixes that mismatch for those service subdomains.

Home LAN numbering

Logical layout, static assignments, and migration notes: projects/Home-Network. Service IPs: Seamoth 10.0.0.20, Prawn 10.0.0.21, Leviathon 10.0.0.10 unless noted otherwise.

Tailscale (remote access to the home LAN)

Subnet router Leviathon (Synology DSM package) — advertises 10.0.0.0/24
Exit node Seamoth (Ubuntu on the Mac Mini) — --advertise-exit-node, --accept-routes=false
Purpose Remote mesh VPN: reach the home LAN via the NAS; optional internet egress via Seamoth when a client selects that exit.

Details

  • Leviathon runs the official Synology Tailscale package (not Docker). Tailscale IP 100.72.52.29. It is the only tailnet device that should advertise the home subnet (10.0.0.0/24). Approve the route in the Tailscale admin console.
  • Seamoth runs the Linux Tailscale client. It acts as an exit node but does not advertise LAN routes (avoids duplicating the subnet router and avoids routing loops on a host that already lives on 10.0.0.0/24).
  • On Seamoth, typical bring-up:
sudo tailscale up --advertise-exit-node --accept-routes=false

Use --reset only when intentionally clearing prior CLI flags. After advertising, enable the machine as an exit node in the admin console if it is not already allowed.

  • --accept-routes=false on Seamoth is deliberate: Leviathon also advertises 10.0.0.0/24; accepting that route on Seamoth can interfere with direct same-LAN traffic to 10.0.0.x. Remote members still reach the LAN via Leviathon’s subnet route; more-specific routes on clients take precedence over the default route when using an exit node.

  • Leviathon may optionally be configured as a second exit node in the admin console; that does not conflict with being the subnet router. Do not advertise 10.0.0.0/24 from both machines.

  • UDP / throughput (Seamoth): for exit-node performance on Linux, Tailscale recommends ethtool offloads on the WAN-facing NIC (enp2s0f0). A persistent hook is installed at /etc/networkd-dispatcher/routable.d/50-tailscale (see Tailscale performance / UDP GRO).

  • Game access for shared users uses Prawn’s Tailscale IP / MagicDNS and tag:gameserver — see projects/Game-Servers. Seamoth is exit node only; friends do not need Seamoth for Minecraft. 2026-10-22: Prawn came back online after ~mid-September offline; its 100% CPU was Minecraft memory pressure, fixed by lowering heaps.

  • Aurora (2026-10-27): sits on the campus dorm network, not the home LAN, so home 10.0.0.x is reachable only through Leviathon over Tailscale. Tailscale DNS (CorpDNS) must stay off on Aurora. A Tailscale hang killed all internet on Aurora. Tailscale auto-start races also caused drops. Snowfox does use Tailscale DNS and was confirmed against Technitium. Open WebUI is Tailscale Serve :80 → 3000 at http://aurora; Home Assistant stays on https :443. Detail: projects/Aurora-Gaming-PC.

  • Administration and keys live in the Tailscale admin console — not a custom domain on this stack.

  • The tailnet uses a grants-based ACL policy — shared users are restricted to game server ports only. Full JSON: projects/Game-Servers#tailscale-acl-grants-config. The member subnet grant in the admin console matches the LAN: 10.0.0.0/24 (updated from 192.168.0.0/24 when the home network moved).

Historical routing caveat (resolved pattern)

An older setup had Seamoth (then macOS) combining exit node + subnet advertisement (and overlapping accept-routes) for the same LAN it was on, which broke same-LAN access from other 10.0.0.x devices. The current split fixes that: subnet routing only on Leviathon, exit on Seamoth without advertising 10.0.0.0/24, accept-routes=false on Seamoth. Background: exit nodes, subnet routers.

DNS and domains (Cloudflare)

Cloudflare is the authoritative DNS and primary domain / zone control for public names (e.g. kiefermenard.com): A, AAAA, CNAME, and other records you maintain there. That includes every Internet-facing hostname you point at home or elsewhere — not only the short service aliases. This wiki calls out jf., ha., and vw. as examples; the same zone also carries the full hostnames (jellyfin.…, homeassistant.…, vaultwarden.…), the personal site, and any other public records you add in the Cloudflare dashboard.

Contrast: Technitium DNS on the Mac minis is the resolver for devices on the home LAN (Pi-hole removed 2026-10-23; cutover confirmed 2026-10-27). It does not replace Cloudflare for worldwide DNS for your domain; Cloudflare does not replace it for on-network client DNS. See the Technitium DNS section above.

SSL (2026-10-27): Cloudflare SSL mode for kiefermenard.com is Full (strict). Homelab service subdomains work with it. The origin certificate on Leviathon’s reverse proxy is the Let’s Encrypt wildcard from acme.sh — #wildcard-certificate-2026-10-27. The apex and www were still on a self-signed certificate (open).

Public DNS layout (proxied vs Minecraft)

  • Most web hostnames use proxied (orange cloud) A records or CNAMEs pointing at leviathon.synology.me (Synology DDNS to the home WAN).
  • Minecraft names (mc, minecraft, rlcraft — full FQDNs under kiefermenard.com) are DNS-only (grey cloud) CNAMEs to TCPShield’s hostname so raw TCP works and the home IP stays off the public game path. Details: projects/Game-Servers#tcpshield-ddos-protection-for-minecraft.

DDNS (Cloudflare, Seamoth)

The home connection uses a dynamic residential WAN (e.g. CenturyLink). Seamoth runs favonia/cloudflare-ddns in Docker so A/AAAA records in the kiefermenard.com zone follow the current public IP automatically—no manual Cloudflare edits when the ISP rotates the address. drop.kiefermenard.com is already updated by this Favonia setup. Early October: subdomains dn and droppedneedle (DroppedNeedle) were added to the same updater.

DNS records for subdomains kv, kavita, vd, and navidrome point at Leviathon’s reverse proxy. Proxy routes are pending.

Compose file ~/docker/cloudflare-ddns/docker-compose.yml on Seamoth
Image favonia/cloudflare-ddns:latest
Why two services Proxied (orange cloud) and DNS-only (grey cloud) hostnames need different PROXIED values, so they run as separate containers with the same API token.

docker-compose.yml (shape; token only on the server)

services:
  cloudflare-ddns-proxied:
    image: favonia/cloudflare-ddns:latest
    restart: unless-stopped
    environment:
      CLOUDFLARE_API_TOKEN: "<set in place on Seamoth; do not commit>"
      DOMAINS: "backup.kiefermenard.com,diskstation.kiefermenard.com,drive.kiefermenard.com"
      PROXIED: "true"

  #cloudflare-ddns-unproxied:
    #image: favonia/cloudflare-ddns:latest
    #restart: unless-stopped
    #environment:
      #CLOUDFLARE_API_TOKEN: "<set in place on Seamoth; do not commit>"
      #DOMAINS: ""
      #PROXIED: "false"
  • API token: create under My Profile → API Tokens in Cloudflare. Needs Zone → DNS → Edit (or equivalent) scoped to kiefermenard.com only. Never commit the token to git or paste it in chat; if it leaks, revoke it in the dashboard and create a new one.
  • Proxied list — hostnames that should go through Cloudflare’s proxy (HTTP/S and related) for the NAS and other services. Game subdomains are not orange-cloud proxied; they are DNS-only CNAMEs to TCPShield (see Public DNS layout above), not PROXIED: "false" A records from this updater unless you intentionally manage them here instead.

Gotify + iOS push (Leviathon)

Self-hosted notification server. Public https://gotify.kiefermenard.com; LAN http://10.0.0.10:8765. The homelab jump page links both.

Runtime Docker via Container Manager on Leviathon
Publish Host 8765 → container 80
Data /volume1/docker/gotify/data → /app/data
First run Set GOTIFY_DEFAULTUSER_PASS in the container env

iGotify Notification Assistant (APNs relay)

Apple push requires a companion container. Example:

sudo docker run -d \
  --name igotify-assistant \
  --restart unless-stopped \
  -p 8766:8080 \
  -e GOTIFY_URLS="http://10.0.0.10:8765" \
  -e GOTIFY_CLIENT_TOKENS="<client-token-from-gotify>" \
  -e SECNTFY_TOKENS="<secntfy-token-from-igotify-app>" \
  ghcr.io/androidseb25/igotify-notification-assist:latest

Tokens

  • GOTIFY_CLIENT_TOKENS: Gotify web UI → Clients → create client.
  • SECNTFY_TOKENS: iGotify iOS app → Settings → instance → SecNtfy Token (also logged on first container start as DeviceToken: NTFY-DEVICE-...).

Public UI: https://igotify.kiefermenard.com (linked from the homelab jump page).

Gotchas

  • Prefer GOTIFY_URLS (plural); older images used GOTIFY_SERVER_URL (singular).
  • The assistant must use the internal URL http://10.0.0.10:8765. The public https://gotify… URL goes through Cloudflare and breaks the long-lived WebSocket the assistant needs.
  • The Synology firewall rule allowing 172.17.0.0/16 is required so the assistant container can reach Gotify (see projects/Home-Network#synology-firewall-leviathon).
  • If the assistant cached a wrong URL, remove its Docker volume and recreate without a stale -v mount.
  • Lock-screen notifications show “tap to view” by design (payload is encrypted until opened on device).

Watchtower (monitor-only)

Watchtower checks for newer images on a schedule and notifies Gotify; it does not auto-update containers.

Seamoth — ~/docker/watchtower/docker-compose.yml:

services:
  watchtower:
    image: containrrr/watchtower:latest
    container_name: watchtower
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      DOCKER_API_VERSION: "1.40"
      WATCHTOWER_MONITOR_ONLY: "true"
      WATCHTOWER_SCHEDULE: "0 0 4 * * *"
      WATCHTOWER_NOTIFICATIONS: gotify
      WATCHTOWER_NOTIFICATION_GOTIFY_URL: "https://gotify.kiefermenard.com"
      WATCHTOWER_NOTIFICATION_GOTIFY_TOKEN: "<app-token>"
      WATCHTOWER_NOTIFICATION_TITLE: "Watchtower Seamoth"
      WATCHTOWER_CLEANUP: "true"
      WATCHTOWER_INCLUDE_STOPPED: "false"

Leviathon — DSM 7.1.x Container Manager has no Compose “Project” flow; use docker run over SSH if you need the same pattern (include the same WATCHTOWER_NOTIFICATION_TITLE if you later move this to a compose file on the NAS):

sudo docker run -d \
  --name watchtower \
  --restart unless-stopped \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -e DOCKER_API_VERSION=1.40 \
  -e WATCHTOWER_MONITOR_ONLY=true \
  -e "WATCHTOWER_SCHEDULE=0 0 4 * * *" \
  -e WATCHTOWER_NOTIFICATIONS=gotify \
  -e WATCHTOWER_NOTIFICATION_GOTIFY_URL="https://gotify.kiefermenard.com" \
  -e WATCHTOWER_NOTIFICATION_GOTIFY_TOKEN="<app-token>" \
  -e WATCHTOWER_NOTIFICATION_TITLE="Watchtower Leviathon" \
  -e WATCHTOWER_CLEANUP=true \
  containrrr/watchtower:latest

Use a separate Gotify app token per host (e.g. “Watchtower Seamoth” vs “Watchtower Leviathon”). DOCKER_API_VERSION: "1.40" avoids “client version 1.25 is too old” against the local daemon.

Prawn — same pattern at ~/docker/watchtower/docker-compose.yml with WATCHTOWER_NOTIFICATION_TITLE: "Watchtower Prawn" and a separate Gotify app token.

WATCHTOWER_NOTIFICATION_TITLE is set so Gotify titles can identify the host; in practice the prefix may not show up as expected in Gotify, but it is kept in the configs for clarity.

Machine backup (Seamoth vs Prawn)

Host Method Notes
Seamoth (26.04) rsync → Leviathon Share seamoth-backup; nightly seamoth-backup.timer — projects/Seamoth-Backup-Rsync
Prawn (24.04) Synology ABB Active Backup for Business agent on supported 24.04
Leviathon DSM backup / snapshots Hyper Backup on shares as configured

Security hardening (summary)

Measure Notes
DSM 5000/5001 not exposed DSM only via diskstation.kiefermenard.com through reverse proxy
Synology firewall Geo US + Canada, default deny; Docker bridge + LAN allows — projects/Home-Network#synology-firewall-leviathon
Synology auto-block + 2FA Control Panel → Security
Cloudflare 2FA Controls public DNS
TCPShield + UFW on Prawn Minecraft public path — projects/Game-Servers#tcpshield-ddos-protection-for-minecraft
Paper whitelist; ProtocolLib / Paper aligned ProtocolLib 5.4.0+ for Paper 1.21.5
Cloudflare proxy on web Absorbs volumetric noise on HTTP/S origins
Bitwarden SSH keys Keys in vault, not on disk (operational habit)

Reverse proxy and security (shared)

Jellyfin, Home Assistant, and Vaultwarden are exposed with:

  • Public hostnames are defined in Cloudflare (see DNS and domains above); inbound HTTPS reaches the Synology reverse proxy on 443 according to however you publish the origin (proxied records, direct A/AAAA to your WAN IP, etc.).
  • Synology DSM built-in reverse proxy (Login Portal / Application Portal) terminating HTTPS — not Docker; forwards to the backends (Docker on the Mac Mini or NAS as configured). As of 2026-10-27 the certificate on those entries is the Let’s Encrypt wildcard for kiefermenard.com issued by acme.sh on Seamoth and redeployed to DSM — #wildcard-certificate-2026-10-27.
  • External traffic: HTTPS on port 443.

Technitium DNS (formerly Pi-hole) stays internal-only and acts as the network DNS resolver for LAN clients (separate from Cloudflare’s role for the public zone).

Tailscale is orthogonal to the reverse proxy: it provides encrypted mesh access to nodes and (if configured) routed subnets, not HTTPS termination on 443 like Synology’s DSM proxy.

  • Homelab jump page (LAN) — http://10.0.0.10/homelab/
  • Drop (LAN) — http://10.0.0.20:8095
  • Drop (public name) — https://drop.kiefermenard.com
  • Projects wiki — https://wiki.kiefermenard.com
  • Jellyfin — https://jf.kiefermenard.com
  • Tdarr (LAN) — http://10.0.0.20:8265
  • Home Assistant (Seamoth) — https://ha.kiefermenard.com
  • Home Assistant (Aurora, Tailscale) — http://100.107.146.20:8123
  • Vaultwarden — https://vw.kiefermenard.com
  • Vaultwarden admin — https://vw.kiefermenard.com/admin
  • Gotify (public) — https://gotify.kiefermenard.com
  • iGotify — https://igotify.kiefermenard.com
  • Technitium (primary) — http://10.0.0.20:5380 / http://dns.home (LAN IP only; not localhost)
  • Technitium (secondary) — http://10.0.0.21:5380 (LAN IP only; not localhost)
  • Uptime Kuma — https://status.kiefermenard.com
  • Tailscale admin — https://login.tailscale.com/admin/machines
  • UPS shutdown orchestration — projects/UPS-NUT-Power-Shutdown

Known issues

  • Tailscale: current layout (subnet on NAS, exit on Seamoth, no duplicate subnet advertise from Seamoth) is the supported pattern. Reverting to subnet + exit + accept-routes on Seamoth for the same 10.0.0.0/24 risks the old same-LAN breakage. See Tailscale above.
  • Media storage (2026-10-28): the homelab media library is close to 1 TB and server storage is getting tight. Tdarr on Seamoth (http://10.0.0.20:8265) transcodes on a remote Aurora RTX 5070 worker, holds new files for 31 days and skips hardlinked (still-seeding) files, and re-encodes H.265 movies only above about 8 Mbps at 1080p.
  • Drop public name: Favonia already updates drop.kiefermenard.com. The Synology reverse proxy on Leviathon was not changed. It still needs a rule to http://10.0.0.20:8095 with WebSockets and X-Forwarded-Proto, X-Forwarded-Host, and X-Real-IP. A compromised host that swaps Drop's JavaScript can steal a password on the next login; that limit was accepted. iOS App Store screenshots, build selection, and the 2026-10-04 dark-mode / keyboard-dismiss bugs are still open. projects/Drop.
  • Technitium (2026-10-27): cutover done. Seamoth primary, Prawn secondary mirroring it. Confirmed as DNS for Snowfox over the tailnet via Tailscale’s DNS setting. API/web UI only on the LAN IPs (port 5380), not localhost. Pi-hole removed 2026-10-23.
  • Split-horizon zones (2026-10-27): 21 kiefermenard.com zones (LAN shortcuts to Leviathon) are re-enabled. ab, abyssal, mc, and rlcraft remain disabled.
  • Apex certificate (open, 2026-10-27): Cloudflare SSL is Full (strict) and homelab service subdomains work. kiefermenard.com / www on Leviathon was still serving a self-signed certificate and was being investigated.
  • kv / kavita / vd / navidrome: DNS points at Leviathon’s reverse proxy; proxy routes pending.
  • Prawn CPU (2026-10-22): back online after ~mid-September offline. All CPU threads were pinned at 100% because of memory pressure: three Minecraft servers had 15G of heap on 15 GiB of RAM. Heaps were lowered to Paper 1G/3G, RLCraft 1G/4G, abyssal-ascent 1G/4500M (fixed, 2026-10-22). CPU now runs about 78–86 °C; cleaning the fan is suggested.
  • Aurora Tailscale DNS: Aurora is on the campus dorm network, not the home LAN, so home 10.0.0.x is only through Leviathon over Tailscale. CorpDNS must stay off. A Tailscale hang killed all internet. Auto-start races also caused drops.
  • Homelab jump page → qBittorrent: without rel=noreferrer, qBittorrent returns 401 Unauthorized on a cross-origin Referer from http://10.0.0.10/homelab/.
  • Aurora Zigbee: usbipd bind survives Windows reboot; attach does not — Startup attach-zigbee-wsl.ps1 re-attaches and restarts homeassistant. Scheduled task Zigbee-WSL-AutoAttach was dropped for elevation.
  • Aurora presence: Asleep/Awake is manual; awake occupancy / leave-asleep drive light.table_lamp + light.presence_sensor; asleep night light remains light.presence_sensor ~15% only. Spare light.lamp_bulb is device-disabled. Air purifier airflow can false-trigger mmWave; R3 reportedly has no zone masking.
  • Aurora plants (shopping, not installed): want HA watering notifications; looking at cheap Zigbee soil-moisture probes — Style1-class moisture+temp is enough (no fertility/EC).
  • Aurora SignalRGB: bridge uses URL protocol (not Pro API); SignalRGB must already be running.

Raw sources

  • Summary ingested into this wiki (see log).
  • raw/homelab-networking-docs.md — Cloudflare layout, firewall, Gotify, Watchtower, Jellyfin NFS mounts, TCPShield/UFW pointers (May 2026).
  • 2026-09-08 CS Lab / Grok Bot session — homelab jump page, iGotify public URL, Aurora HA access, Seamoth :8888 menu retired.
  • 2026-09-11 CS Lab / Grok Bot session — Aurora Zigbee usbipd auto-reattach, presence lighting, SignalRGB Asleep bridge.
  • 2026-09-15 CS Lab / Grok Bot session — Aurora desk lamp (light.table_lamp) + input_number.presence_awake_brightness; spare light.lamp_bulb device-disabled; night light remains presence LED ~15%.
  • 2026-10-26 weekday ingest — Technitium DNS (Seamoth primary, Prawn secondary; Pi-hole removed 2026-10-23); .home names; LAN shortcuts to Leviathon switched off because of the default synology.me cert; Uptime Kuma https://status.kiefermenard.com; Favonia dn / droppedneedle; kv / kavita / vd / navidrome DNS with proxy routes pending; DroppedNeedle and slskd on the homelab links page; Prawn back online, 100% CPU fixed by lowering Minecraft heaps; Aurora CorpDNS stays off and Open WebUI is Tailscale Serve :80→3000.
  • 2026-10-28 weekday ingest (facts as of 2026-10-27) — Technitium cutover confirmed; Snowfox uses it over the tailnet via Tailscale DNS; UI on LAN IPs port 5380 only, not localhost; acme.sh on Seamoth (~/docker/acme) Let’s Encrypt wildcard assigned to DSM reverse-proxy entries (dedicated DSM user, auto-renew and redeploy); 21 split-horizon zones re-enabled (ab, abyssal, mc, rlcraft stay disabled); Cloudflare SSL Full (strict) for service subdomains; apex/www still self-signed (open); Aurora on the campus dorm network reaches home 10.0.0.x only through Leviathon over Tailscale.
  • 2026-10-29 weekday ingest (facts as of 2026-10-28) — Tdarr on Seamoth (http://10.0.0.20:8265) uses a remote transcoding worker on Aurora (RTX 5070). The libraries hold new files for 31 days and skips hardlinked (still-seeding) files. Movies rules re-encode H.265 only above about 8 Mbps at 1080p (save space on bloated H.265, not skip H.265). Media library close to 1 TB; server storage getting tight.