A computer that’s on the public internet to run it on. While crunching through video and serving it to viewers can be intensive from the computing side, you can get away with pretty meager resources on a simple setup. If you don’t already have a server to run it on you can get a Linode instance for $5/mo that runs it fine. If you worry that you’ll be maxing out the bandwidth or transfer limits allotted to you, then utilize a service like Media Network to serve the files instead.

Here are some hosting providers people have been successful with.

Njala (privacy focused)

A Unix OS (Debian 10 preferable) is recommended.

Install tools

apt install -y curl unzip htop bmon

Installing Owncast

Paste the following into your shell and the installer will download the most recent version of Owncast for your platform. It will also download a copy of ffmpeg if you don’t currently have one installed.

curl -s | bash
[email protected]:~# curl -s | bash
Owncast Installer v0.0.7
Created directory []
Downloaded Owncast v0.0.7 for linux []
Downloaded ffmpeg because it was not found on your system []
Success! Run owncast by changing to the owncast directory and run ./owncast.
The default port is 8080 and the default streaming key is abc123.
Visit to learn how to configure your new Owncast server.

Running the instance

[email protected]:~# cd owncast/
[email protected]:~/owncast# ./owncast &
INFO[2021-06-08T00:50:48Z] Owncast v0.0.7-linux-64bit (3810ce4f63ecf7fb7a35c564af68f081c7e8b537)
INFO[2021-06-08T00:50:48Z] Video transcoder started using x264 with 1 stream variants.
INFO[2021-06-08T00:50:49Z] RTMP is accepting inbound streams on port 1935.
INFO[2021-06-08T00:50:49Z] Web server is listening on port 8080.
INFO[2021-06-08T00:50:49Z] The web admin interface is available at /admin.

Find out Owncast's port:

In this step you'll have to find out the details about your Owncast instance to be able to broadcast to it and also add it later on to Media Network. Open a new You can check what is running in each port by executing the following command:

netstat -ntpl
[email protected]:~# netstat -ntpl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0* LISTEN 1292/./owncast
tcp 0 0* LISTEN 600/sshd
tcp6 0 0 :::1935 :::* LISTEN 1292/./owncast
tcp6 0 0 :::8080 :::* LISTEN 1292/./owncast
tcp6 0 0 :::22 :::* LISTEN 600/sshd

Owncast is running on port 8080 for HTTP and 1935 for incoming RTMP streams, both under PID 1292

Find out external IP address of your device:

eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet netmask broadcast
inet6 fe80::2eea:7fff:fef0:f2fe prefixlen 64 scopeid 0x20<link>
ether 2c:ea:7f:f0:f2:fe txqueuelen 1000 (Ethernet)
RX packets 9245489 bytes 1915123059 (1.7 GiB)
RX errors 0 dropped 34 overruns 0 frame 0
TX packets 4943558 bytes 970078005 (925.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 49

The external IP address is using the eno1 interface.

This means your Owncast instance is running at the following URL, which is what we'll need to add as a CDN resource:

Your Owncast instance is ready! Just point your OBS or preffered broadcasting software to your IP and path:

Server: rtmp://
Stream Key: abc123
URL to Watch:
Web Admin: (user: "admin" pass: "abc123")

You can also use ffmpeg, for example let's restream an RT News feed:

ffmpeg -re -i -c copy -bsf:a aac_adtstoasc -f flv rtmp://

Monitoring bandwidth and hardware usage

You can use tools like htop and bmon to monitor both hardware resources and bandwidth consumption within the server / computer.

Quick install tutorial