JarvisOS HomeLab status
No signal

Recover: VIN / VPS

No signal critical

Public edge node. Terminates TLS via Caddy, hosts the tunnel endpoint and the warm standby control plane.

Owner
homelab-operator
Target RTO
15m
Last heartbeat
never
Dependent entities
6
Recovery readiness20/100
← Back to status

Procedure

Read fully before acting.
  1. VIN is the public entry point: if it is down, everything published is offline even when Home1 is healthy.
  2. Check the provider console for the VPS power state before assuming a software fault.
  3. Verify Caddy is listening on 80/443. Do not edit the Caddyfile as part of an incident response; it is managed configuration.
  4. Confirm the WireGuard tunnel to Home1 is up before restarting the control plane.
  5. This status console binds 127.0.0.1 only — reach it through an SSH tunnel, not a public route.

Bring-up order

Dependencies first — starting out of order is a common second incident.
  1. VIN / VPS Node target

What this affects

Impacted if this stays down, or while you restart it.
Downstream JarvisOS Worker (VIN) Caddy (reverse proxy) Postgres (replica) JarvisOS Auth (SSO) WireGuard (Home1 <-> VIN) JarvisOS Control Plane

Readiness breakdown