Overview & server lifecycle

Access and purpose#

Open the native Administration app and sign in with an administrator. Overview brings together server status, catalog counts, endpoint information, connected sessions and library activity.

Read the dashboard#

• Media engine and Server uptime identify the running engine, not a remote browser.
• Gateway memory and Platform describe the local gateway process.
• Local bind / listen and Local Media Center show the actual loopback address and port.
• Public HTTPS endpoint is a saved external address. Public HTTPS verification is the separate end-to-end check.
• Reverse proxy / tunnel and Connection checks distinguish connector state from actual public reachability.

The scan card shows playable items indexed, task progress when reported and last activity. A dash or unknown remaining count means that the engine did not supply that value; it is not a fabricated scan estimate.

Restart or stop#

1. Check connected sessions first; a restart interrupts their streams.
2. Use Restart to restart the media engine, or Stop server to stop playback service deliberately.
3. Confirm the dialog and wait for status to return to ready.
4. If the engine stays failed, open Logs & diagnostics rather than clicking repeatedly.

Quitting Administration does not perform these actions. The background service and tray remain running. The menu bar offers browser windows, the Admin panel, library scan, restart, logs and explicit server/tray quit actions. See Application.

Connected sessions#

The dashboard includes a refreshable list and a confirmation before disconnecting one device. People & access explains session-level revocation.