Logs & diagnostics

Inspect the running gateway#

Open Logs & diagnostics. The diagnostics section identifies the application endpoint, private engine endpoint, Node/platform/architecture and data directory. The private engine's loopback port is not the Media Center address and should not be opened to the internet.

Read and filter logs#

1. Use Refresh to load current server logs.
2. Enter a term in Filter server logs to narrow the visible lines.
3. Inspect the time around the failed startup, scan, provider or transcode event.
4. Download logs or use Open logs folder where the native application offers it.

An empty filter resets the view. Filtering does not rewrite the log file. A connection error can originate at DNS/Cloudflare, the public gateway, the private engine or the media drive; use the stage-specific message rather than a generic Connected badge.

Export diagnostic report#

Export diagnostic report downloads a JSON snapshot. The app warns you to review private filesystem paths before sharing. Token fields are sanitized where the app handles them, but filenames, library names, usernames, endpoints and paths can still be private.

Share only the version, platform, relevant time, error stage, HTTP code and selected non-secret lines needed to investigate. Never share passwords, connector commands containing tokens, API tokens, cookies, raw runtime connection descriptors or an entire live profile.

If Administration is offline#

Reopen the installed app, confirm the background service and inspect startup logs from its menu. A corrupt/unreadable configuration should be preserved and recovered from a known backup, not silently overwritten. See troubleshooting.