Caddy (reverse proxy)

No signal critical tier-0 Service

TLS termination and public routing. Managed configuration — treated as read-only by JarvisOS tooling.

Last heartbeat: never
Signal source: probe
Host: VIN / VPS
Target RTO: 10m

Recovery readiness20/100

Recovery procedure →

Why it is no signal

self No heartbeat has ever been received from this entity.

Availability class

Fleet-fatal · target 99.5%

TLS termination and public routing for every published route.

Class: tier-0 Fleet-fatal: loss stops the estate or risks data. Everything else waits.
RTO (declared): 10m
RTO (achievable): 15m set by vin
RPO: —
State: rebuildable
Redundancy: single node
Failover: none
Failure domain: fd-vps

Health check: TCP 443 probe every 120s — proves the TLS listener accepts connections. Observed independently of the service.
Blind spot: Accept-only. It does not prove a published route returns 200, and it cannot see a certificate that expires tomorrow.

Without it: Nothing published resolves to a working endpoint. Loopback and LAN access to home-rack services is unaffected, which is why the recovery console is deliberately loopback-only.

Accepted risk: The class requires redundancy and there is none. caddy

Caddy (reverse proxy) is single-node but tier-0 requires a redundancy model.

Accepted by homelab-operator, review 2027-02-15: Inherited from VIN being the only public-ingress node. A second proxy would need a second public node and DNS failover. The Caddyfile is managed configuration restored from the crown-jewels tier in minutes.

Full classification and SLOs →

Dependencies

blast radius: 0

Depends on VIN / VPS Public DNS

Depended on by: none