--- schema_version: 1 id: home-server.mercury type: reference scope: [mercury, vps, firewall, fail2ban, uptime-kuma] sensitivity: private-infrastructure last_reviewed: "2026-10-27" sources: - kind: owner-report reference: "Hosting/firewall snapshot 2026-10-06; Fail2ban CLI/config and Kuma runtime 2026-10-26" - kind: live-inspection reference: "Hostname mercury and nginx 1.26.3 inspected 2026-10-27; firewall/hosting not revalidated" - kind: repository repository: jupiter-stacks revision: working-tree paths: [mercury/stacks/uptime-kuma/docker-compose.yml] related: [home-server.networking, home-server.operations, home-server.backups] update_triggers: [hosting-renewal, vps-resize, os-upgrade, firewall-change, kuma-change] unknowns: [renewal-price-and-date, creation-timestamp-timezone, certificate-renewal-method, mercury-backup-policy, fail2ban-enforcement-details-and-log-retention] --- # Mercury VPS ## Host | Setting | Value | | --- | --- | | Provider / plan | Fasthosts UK; KVM `1-1-10` | | CPU / RAM | 1 vCore, AMD EPYC-Milan reported; 1 GB plan / 864.37 MiB guest | | Disk | 10 GB NVMe plan / 9.64 GiB ext4 root; no swap | | OS / kernel | Debian 13 x86_64; `6.12.85+deb13-amd64` | | Hostname | `mercury`; older snapshot: `my-vps` | | Public interface | `ens6`; `185.230.217.66/32` | | Created / payment | `2026-03-01 20:48:51`, timezone unknown; GBP 10 prepaid/year | | Administration | From Jupiter: `ssh mercury`; nginx/WireGuard apt-managed | | Certificates | `/etc/letsencrypt/live//{fullchain.pem,privkey.pem}`; renewal method unknown | - Ingress, tunnel addresses and nginx configuration: [Networking](networking.md). - Alert scope, thresholds and Discord destinations: [Operations](operations.md#observability). ## Uptime Kuma runtime - Supplied launch script: `~/uptime-kuma.sh`; Compose replacement in `mercury/stacks/uptime-kuma/docker-compose.yml` is **not confirmed deployed**. - Image `louislam/uptime-kuma:2-slim`; container `uptime-kuma`; restart `unless-stopped`. - Bind `/opt/uptime-kuma:/app/data`; loopback `127.0.0.1:3001`. - Limits: **300 MiB / 0.5 CPU**; `json-file` logs **10 MiB x 3**. - Stop before copying state for migration; preserve the bind directory. nginx stays host-managed. ## Firewall / Fail2ban - Supplied firewall: UFW/iptables INPUT + FORWARD `DROP`; OUTPUT `ACCEPT`. - Allows TCP `22,80,443`; UDP `80,443,51820`. Docker forwarding has separate rules. - Fail2ban **1.1.0**, enabled at boot; effective settings from **2026-10-26**: | Jail | Source | Retries / window | Ban | | --- | --- | --- | --- | | `sshd` | journal: `_SYSTEMD_UNIT=ssh.service + _COMM=sshd` | 5 / 600s | 600s | | `nginx-http-auth` | `/var/log/nginx/error.log` | 3 / 600s | 600s | | `nginx-botsearch` | `/var/log/nginx/access.log` | 2 / 600s | 3600s | - All three: action `nftables`; `ignoreip` empty. SSH journal `+` means **OR**. - nginx jails target `http,https`. Action names do not prove blocked chains, ports or IPv6 coverage. - Persistent overrides: `/etc/fail2ban/jail.local` (nginx filters/paths/retries; botsearch timing) and `jail.d/defaults-debian.conf` (SSH systemd backend/match; nftables defaults). - `banaction_allports=nftables[type=allports]` is defined; active use is unconfirmed. Other timing values are inherited. - Log: `/var/log/fail2ban.log`; DB: `/var/lib/fail2ban/fail2ban.sqlite3`; `dbpurgeage=86400`. - DB purge age is **not** ban duration or log retention; escalation, rotation and config backup remain unknown. - No administrator IP exemption: retain recovery access before testing failed logins. ```sh sudo fail2ban-client version sudo fail2ban-client status sudo fail2ban-client status sshd sudo fail2ban-client status nginx-http-auth sudo fail2ban-client status nginx-botsearch ```