Skip to content

Streamer settings

A streamer has no configuration of its own: central stores it and delivers it to the machine. The settings form lives at the bottom of the streamer's card — open it from the registry by clicking the row.

How changes apply

The Save changes button submits only what you changed — parallel edits of other sections are not clobbered. From there, a trace of three indicators follows the delivery:

  • Saved — central accepted the changes.
  • In flight — the configuration is on its way to the streamer; the indicator pulses. If the streamer is offline, the form says so outright: the settings will apply when the link comes back.
  • Applied — the streamer confirmed the apply; next to it — how many seconds the delivery took.

If the settings were changed in parallel with you, the form shows a conflict banner with a choice: Show latest — re-read the other version, Overwrite — insist on yours.

A yellow ENV badge on a field means the value is set by the machine's own environment: it outranks whatever central delivers, and editing the form will not take effect on this streamer until the variable is removed.

Listeners

The ports the streamer opens per protocol: HTTP, RTSP, RTMP, WebRTC. A port is added as a chip; a chip marked tls means the port carries a certificate.

Certificates and HTTPS

The Certificates section hangs TLS onto the HTTP listeners — a certificate lives on a port, so a listener comes first. One port can carry several entries: clients pick the certificate by SNI.

The certificate source of an entry:

  • Let's Encrypt — automatic issue for the listed domains. Fill in the ACME contact e-mail below: without it nothing gets issued, and the CA sends expiry warnings to it. Leave the ACME directory URL empty — that is production Let's Encrypt.
  • Static PEM — your own certificate and private key: full PEM or a file path on the streamer.
  • Self-signed — for stands and internal networks.

Domains are comma-separated; the form suggests the hostname from the streamer's delivery addresses. ACME will not issue for a bare IP — you need a domain.

The issue state shows above, in the streamer's card: issued (with time to expiry), pending, failed — with the error text. Two weeks before expiry the row turns yellow.

DVR

Where the streamer writes the archive: the Archive root, a list of disks when there are several, and the Catalog path. The Verify mount before writing switch is on by default: writing onto the system root partition is forbidden, and a disk without a mount of its own reports as "not mounted". Turn it off only deliberately.

Recording and watching the archive in detail — the DVR page.

Publish prefixes

The name prefixes under which the streamer accepts incoming publications. Without prefixes, publishing is accepted only into existing channels.

Connection and delivery

  • Streamer API URL — the address central uses to reach the machine's management API. Without it the streamer carries a reachability chip in the registry, and its sessions vanish from the output.
  • CDN zone — which zone the streamer belongs to; the player front routes viewers by it.
  • Public payload URL — the public base of viewer addresses. Set — players get a redirect straight to the streamer; empty — central proxies the media through itself.
  • Intra-cluster payload URL — the base for streamer-to-streamer transfers and proxying; defaults to the API URL.

The resulting delivery mode shows in the streamer's card: in-process (the local streamer), redirect, proxied by central, or unreachable — in red when nothing is set. A separate warning appears when a certificate is issued for a name but the delivery base is still http:// — TLS goes unused in that case.

Reverse proxy and reset

The Reverse proxy (JSON) section is a temporary editor of the raw rproxy section; invalid JSON blocks saving.

The Reset to default button in the danger zone returns all of the streamer's settings to their defaults — the streamer applies them on its next sync. The action is irreversible.