Health and logs
Fast health check
Section titled “Fast health check”cd ~/relaytvdocker compose pscurl -fsS http://127.0.0.1:8787/healthRun the HTTP request on the RelayTV host first. A local success and remote failure points toward firewall, routing, DNS, proxy, or client-network behavior rather than the application process.
Recent logs
Section titled “Recent logs”docker compose logs --tail=200 relaytvFollow logs only while reproducing a specific problem:
docker compose logs --follow relaytvStop following with Ctrl+C; this does not stop the container.
Before sharing diagnostics
Section titled “Before sharing diagnostics”Remove or redact:
RELAYTV_API_TOKEN- Jellyfin, Emby, Seerr, and playlist credentials
- credential-bearing source URLs
- private hostnames, public IPs, and reverse-proxy headers when unnecessary
- personal library names or artwork
A healthy API is not a healthy display
Section titled “A healthy API is not a healthy display”The health endpoint proves the service responds. It does not prove mpv can start, the display session is accessible, audio reaches the correct sink, or the GPU supports the selected media. Reproduce a real playback after every runtime change.
Canonical server source: native runtime operations. Reviewed 2026-08-29.
