Fasthosts plan, fastfetch, nginx sites, iptables and fail2ban output, 2026-10-06
kind
reference
owner-report
nginx/WireGuard apt management and public IPv4/CGNAT rationale, 2026-10-06
kind
reference
owner-report
Uptime service confirmed as Uptime Kuma; notifications received in Discord server Jupiter, channel #uptimekuma-alerts, 2026-10-23
kind
reference
owner-report
Mercury uptime-kuma.sh supplied with bind mount, resource limits and log rotation, 2026-10-26
kind
reference
owner-report
Mercury Uptime Kuma only checks WireGuard tunnel health and whether Jupiter is online; alerts Jay on Discord when down, 2026-10-26
kind
reference
owner-report
Mercury monitored in Beszel; CPU above 90% for 10 minutes, memory above 90% for 10 minutes and any failed systemd services alerts configured, 2026-10-26
GBP 10.00 prepaid for one year; renewal terms unconfirmed
Capacities distinguish provider allocation from guest-visible values.
Ingress
nginx runs directly in the VM, not in Docker; nginx and WireGuard are
apt-managed. Mercury provides static public IPv4 ingress because Jupiter's
home connection uses CGNAT. Residential-IP exposure is avoided by design.
Mercury is now monitored by the Beszel hub on Jupiter, confirmed by the
owner on 2026-10-26. The following Mercury alerts are configured:
Alert
Trigger
CPU usage
Above 90% for 10 minutes
Memory usage
Above 90% for 10 minutes
Failed Services
Any failed systemd service
These are deployed alert settings, not proposed additions. Beszel's Failed
Services rule detects failed systemd units, not every error-level journal entry.
Alert settings are stored in the Beszel hub UI/database, not the agent Compose
file. Beszel cannot deliver these alerts while Jupiter or its hub is down.
Uptime Kuma runs on Mercury, served at https://uptime.umbra.mom through
the local upstream http://127.0.0.1:3001. Its current monitoring scope is
only the health of the WireGuard tunnel and whether Jupiter is online.
It notifies Jay on Discord when either is down, using the Jupiter
Discord server's #uptimekuma-alerts channel. Coverage confirmed by the owner
on 2026-10-26; notification receipt previously confirmed on 2026-10-23.
It does not currently monitor individual containers or application health.
The supplied ~/uptime-kuma.sh is now represented by
mercury/stacks/uptime-kuma/docker-compose.yml in jupiter-stacks.
It retains image louislam/uptime-kuma:2-slim, container name uptime-kuma,
restart policy unless-stopped, loopback port 3001, and bind mount
/opt/uptime-kuma:/app/data. Limits remain 300 MiB RAM and 0.5 CPU, with
10 MiB / 3-file log rotation (Compose explicitly selects json-file).
The adjacent README documents a stopped-data backup and migration into the
Mercury Portainer environment. Migration has not been confirmed; the repository
change alone does not replace the running container. nginx remains host-managed.
Exact probe types, targets and alert timing have not been recorded. A failed
check over WireGuard can indicate a tunnel/path failure rather than a powered-off
Jupiter. Mercury monitors independently of Jupiter, but cannot report its own
complete outage through this instance; an external monitor is not yet confirmed.
See Observability for container-alerting guidance.