Troubleshooting
This page helps you navigate from a symptom to the most relevant docs.
“I can’t reach it”
Section titled ““I can’t reach it”” VPN / private access Most internal hostnames require VPN/LAN reachability.
DNS resolves to the wrong place Split-horizon DNS behavior for LAN/VPN clients.
Firewall / public ingress Public IP forwarding and ingress model.
“It loads, but it’s broken”
Section titled ““It loads, but it’s broken”” 502 / 504 (proxy errors) Ingress layout and default-vhost behavior; use it to reason about routing.
TLS / certificate warnings Public vs internal certificate issuance and renewal.
Internal CA trust issues Trust and internal issuance via the LEF CA.
“Database connection fails”
Section titled ““Database connection fails”” DB endpoints (db.lef) Pick the endpoint page, then follow the routing source of truth.
TCP proxy connectivity Diagnose *.db.lef connectivity via VIPs, DNS, and backend reachability.
“Runtime / container issues”
Section titled ““Runtime / container issues”” Containers as a Service Rootless containers + systemd patterns.
Middleware (runtimes) Upstream → backend mappings and runtime notes.