SRT Stream Manager.
The manual.

What it does

CiegoLink Stream receives a TV signal as UDP or multicast (MPEG-TS) and forwards it as SRT to a cable network, a partner or a playout. Every stream is monitored continuously – separately for input and output.

Installation

You need a Linux server (Ubuntu 22.04 / 24.04 recommended) with internet access for the first build.

1. Copy and unpack the package on the server.

   cd ~
   unzip ciegolink-stream.zip
   cd ciegolink-stream
   chmod +x run.sh host-setup.sh

2. Prepare the server – once per server. Installs Docker if missing, keeps containers running during Docker updates, enlarges UDP buffers and limits log sizes.

   sudo bash host-setup.sh

3. Set token and port in docker-compose.yml. Check first that the port is free: sudo ss -tulpn | grep 8090 (no output = free).

   ADMIN_TOKEN: "choose-a-long-secret"
   PORT: "8090"

4. Build and start. Wait for Uvicorn running on http://0.0.0.0:8090, then press Ctrl+C.

   docker compose up -d --build
   docker compose logs -f

5. Open the firewall if one is active.

   sudo ufw allow 8090/tcp
   sudo ufw allow 9000:9100/udp   # SRT ports you plan to use

First login

1. Open http://<server-ip>:8090 in a browser.
2. Click Admin (top right) and enter the token from docker-compose.yml.
3. The admin buttons appear: New stream, Settings, Log out.

Without logging in, anybody who can reach the page sees the stream status (read-only). Passphrases, stream IDs and receiver IPs are never shown publicly.

Creating a stream

Click New stream. The dialog has two columns: the essentials on the left, options on the right.

General

Input · UDP / multicast

Output · SRT

SRT options

Receiver in listener mode: the receiver connects as caller to srt://<server-ip>:<port> with the same latency, passphrase and stream ID.

Reading the stream list

Every stream is one row. Input and output each have their own coloured dot: green = OK, red = no data or not running, orange = waiting for receiver / connecting, grey = unknown or stopped.

Status values

The red line under a faulty stream explains the cause, e.g. Input lost – no UDP data on 239.1.1.9 @ 10.0.0.5:5004. Filter with All / Live / Faulty / Stopped or search by name, port, IP, cable network or role.

Controlling streams

Alarms

Open the Alarms tab. The red number on the tab shows how many streams are currently faulty.

• Critical input lost, no output, stream down, peer unreachable
• Warning receiver disconnected, process restarted, peer reports a fault
• Recovered the stream is OK again

Use the filter buttons and the search field (stream name or message). 20 alarms are shown per page; up to 1000 are kept.

Settings

Monitoring

Default interfaces

Input and output IP used by all streams set to Default. Running streams use new values after their next restart.

Admin token

Enter the current token and twice the new token (min. 8 characters), then Change token. You stay logged in.

Maintenance

Restart app restarts only the web interface and the monitoring. Streams keep running without interruption.

Alarm mail (SMTP)

Send test mail saves the settings and sends a test message. Click Save to apply.

Status API

These addresses work without login and can be used by dashboards, partners or monitoring tools:

curl http://<server>:8090/api/health
curl "http://<server>:8090/api/alarms?level=critical&limit=20"

The full technical API (creating streams, settings, admin endpoints) is documented in README.md and interactively at /api/docs.

Main & backup

For real 24/7 availability run two servers – ideally at two locations.

1. Install CiegoLink Stream on both servers.
2. Create the same stream on both: role Main on server A, Backup on server B.
3. In Settings → Peer instances, enter server B on server A and server A on server B.
4. Configure the receiver (cable network) with both SRT sources.

If one server fails, the other reports Peer unreachable and sends an e-mail.

Maintenance

Update the web interface – no interruption

Replace the files in app/ and web/, then Settings → Restart app. The running version is shown at the bottom of the page (e.g. v1.1.0 · engine 3.45-4798).

Update the container – short interruption

Only needed when the Dockerfile changes. All streams stop for a few seconds – use a maintenance window.

cd ~/ciegolink-stream
docker compose up -d --build

Backup & restore

Everything (streams, settings, alarms, token) is in the data/ folder. To restore, unpack it into the project folder and run docker compose up -d.

tar czf ciegolink-backup-$(date +%F).tgz data/

Useful commands

docker compose ps                 # status – should be "Up (healthy)"
docker compose logs -f            # application log
docker compose restart            # restart container (interrupts streams briefly)
docker stats ciegolink-stream     # CPU / memory

Removing

docker compose down               # remove containers, data is kept
docker compose down --rmi all     # also remove the image
sudo rm -rf ./data                # delete all streams and settings

Troubleshooting