relay/ (Fly or VPS).
What a relay is
A Go service that:- Maps
HMAC(email) → node(no long-term plaintext email after confirm) - Accepts each node’s outbound WebSocket tunnel
- Peeks TLS SNI on :443 and forwards ciphertext to that tunnel
*.relay.<domain> node hostnames.
Deep dive: Relay. Frames: Wire specification § Tunnel.
Critical constraint
DNS forrelay.<domain> and *.relay.<domain> must be DNS-only (no TLS-terminating
CDN / Cloudflare orange cloud). Otherwise SNI routing breaks and the threat model
collapses.
Path A — Public FAU relay
Usehttps://relay.fau.run (already deployed). Nodes:
Path B — Your own domain
Prerequisites
- Domain you control
- VPS or Fly app with a stable IPv4
- Port 443/tcp open to the relay process
- Optional: registrar DNS API for ACME (e.g. Porkbun on Fly)
DNS
Configure and run
Followrelay/deploy/README.md (Docker/VPS) or relay/deploy/fly.md (Fly).
Typical flow:
Verify
https://relay.example.com and confirm
/.well-known/fau-node on its hostname.
Before inviting strangers: configure SMTP so registration codes are emailed (otherwise
codes only appear in relay logs).
Failure modes
3 AM checklist
/v1/health- DNS grey-cloud / not proxied
nodes_connectedvs expected- Node-side
relay status - AUTH_FAIL / rate_limited in logs
Next
- Point nodes at your relay: Run a node
- Agent resolve URL must match your relay if you are not on
relay.fau.run