3.7 KiB
3.7 KiB
schema_version, id, type, scope, sensitivity, last_reviewed, sources, related, update_triggers, unknowns
| schema_version | id | type | scope | sensitivity | last_reviewed | sources | related | update_triggers | unknowns | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | home-server.mercury | reference |
|
private-infrastructure | 2026-10-27 |
|
|
|
|
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/<domain>/{fullchain.pem,privkey.pem}; renewal method unknown |
- Ingress, tunnel addresses and nginx configuration: Networking.
- Alert scope, thresholds and Discord destinations: Operations.
Uptime Kuma runtime
- Supplied launch script:
~/uptime-kuma.sh; Compose replacement inmercury/stacks/uptime-kuma/docker-compose.ymlis not confirmed deployed. - Image
louislam/uptime-kuma:2-slim; containeruptime-kuma; restartunless-stopped. - Bind
/opt/uptime-kuma:/app/data; loopback127.0.0.1:3001. - Limits: 300 MiB / 0.5 CPU;
json-filelogs 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; OUTPUTACCEPT. - Allows TCP
22,80,443; UDP80,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;ignoreipempty. 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) andjail.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.
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