Troubleshooting

Diagnose common self-hosted runtime problems from the supported operator surface.

Start with:

sudo leamout doctor
sudo leamout status

If a runtime service is unhealthy, inspect its logs:

sudo leamout logs <service>

Common failure areas are incomplete initialization, missing/stale staged runtime files, invalid generated environment configuration, container-runtime failures, DNS/TLS mismatches, public/NAT address mistakes, blocked SIP or media ports, and carrier authentication/routing errors.

For BYOC problems, validate the carrier connection through its API before changing lower-level runtime configuration. Leamout’s carrier validator reports configuration issues and bounded SIP endpoint reachability data.

Avoid editing durable state or private runtime internals as a normal recovery technique. Public APIs and the CLI are the supported control surfaces.