iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If your Owncast YouTube stream shows offline after an Ubuntu restart, first determine which part is offline: the Owncast website, the incoming broadcast to Owncast, or the separate output to YouTube. An active Owncast webpage does not prove that a broadcaster has reconnected, and an active Owncast feed does not prove that YouTube is receiving a stream. Check each link in that order.
First identify what “offline” means
Owncast’s web interface and its RTMP ingest are separate endpoints: the web interface uses port 8080, while broadcasters publish to the Owncast /live RTMP endpoint on port 1935. YouTube has its own destination settings and stream key. Use the visible symptom to choose the first check.
- Owncast website will not load: check whether the server or container started after reboot.
- Owncast website loads, but its player is offline: check whether the broadcaster is running and publishing to Owncast.
- Owncast is receiving video, but YouTube says offline: check the separate YouTube output path and its key.
Do not assume that restarting the Owncast process also restarts an external encoder or any separate YouTube relay.
Recommended Free Tools
Check how Owncast is installed
Use the recovery steps for the deployment you actually have. A native Ubuntu installation may run as a systemd service; a Docker installation is managed as a container. A manually launched foreground process does not automatically become a boot-time service. Owncast’s installation instructions describe the manual setup and link to service configuration for startup behavior.
#1 Best Overall
Native Ubuntu installation: inspect systemd
Check the service state and this boot’s logs
-
Check the unit’s current state:
sudo systemctl status owncast -
Read its logs from the current boot:
sudo journalctl -u owncast -b --no-pager -
If the service is running, watch logs while the broadcaster reconnects:
sudo journalctl -u owncast -f
Owncast documents the systemctl and journalctl checks in its system service guide. Look for startup errors, permission failures, repeated exits, or evidence that a publishing attempt reached the server. If no publishing attempt appears during a reconnect, investigate the broadcaster or network route. If the attempt is rejected, compare the key configured in the encoder with the key configured in Owncast. Never share stream keys in logs, screenshots, or public support posts.
If the unit is missing or disabled
Compare your unit with Owncast’s documented service example, adapting its paths and account details rather than copying sample paths blindly. The example uses After=network.target, Restart=always, RestartSec=5, and WantedBy=multi-user.target. After creating or changing a unit, reload systemd and enable and start the service:
sudo systemctl daemon-reload
sudo systemctl enable --now owncastEnabling a service makes it eligible to start at boot, while the restart policy handles process exits according to the unit configuration. Neither action proves that the incoming broadcaster reconnects or that a separate YouTube publishing path is live.
Check paths, account permissions, and hardening
- Working directory: set
WorkingDirectoryto the directory containing the Owncast binary anddata/. - Service account: Owncast recommends a dedicated non-root user. Confirm the configured
UserandGroupcan read the binary and write to the data directory. - Filesystem restrictions: if the unit uses
ProtectSystem=strict, Owncast’s service guide says to allow its data path throughReadWritePaths; otherwise the service may be unable to write needed data. - Executable path: verify that
ExecStartpoints to the binary that is actually installed.
If the unit repeatedly starts and exits, use the current-boot journal to identify the first error, then check these paths and permissions before changing restart behavior.
If Owncast loads but its player is offline, check RTMP ingest
-
Confirm the broadcaster or encoder is running after the Ubuntu restart. The server’s recovery does not itself restart a separate computer or encoder.
-
Check that the encoder publishes to Owncast’s
/liveRTMP endpoint using the Owncast stream key—not a YouTube key.The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Confirm port 1935 is reachable through the Ubuntu host firewall and any cloud firewall or security rules. Port 8080 is for the web interface; opening it does not establish that RTMP ingest works.
-
Watch the Owncast journal while reconnecting. No log evidence of an attempt points toward the broadcaster or network route; a key rejection points toward a mismatch between the encoder and Owncast configuration.
Owncast’s installation guide identifies the web and RTMP ports and the /live ingest endpoint. Keep the Owncast ingest key distinct from any YouTube destination key.
If Owncast receives video but YouTube is offline
Owncast being online and receiving video establishes only the Owncast side. The available setup information does not establish how your particular installation sends video onward to YouTube. It may use a second encoder output, a relay, or another service, so first identify which arrangement you configured rather than assuming Owncast is forwarding the feed.
-
Check whether your encoder or relay has a separate YouTube destination and whether it is actively publishing.
-
Open YouTube Live Control Room and inspect the stream’s status and settings.
-
Check that the YouTube key in the publishing encoder matches the key shown in YouTube. YouTube’s stream settings instructions explain where to find the key and how to reset it.
-
If you reset the YouTube key, enter the newly generated key in the encoder or relay that publishes to YouTube. Resetting the YouTube key does not change the Owncast ingest key.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Docker installation: check container startup and data persistence
Do not use systemctl status owncast as the health check for an Owncast container that is managed separately. Inspect the container’s status and logs using the workflow you use to run it, then check that it has a restart policy and persistent data storage.
docker run: Owncast documents the--restart unless-stoppedpolicy and a persistent data mount in its container installation instructions.- Docker Compose: check the Compose configuration, confirm that the data mount persists, and use the documented
docker compose up -dworkflow to start the service.
A restart policy and persistent mount address container restart and data retention; they do not establish that an external encoder has reconnected or that YouTube output is active.
Troubleshooting by symptom
| What you see | Check next | What it may indicate |
|---|---|---|
| Owncast website does not load after reboot | Native service or container status, startup logs, working directory, and service permissions | The server may not be running or may not be able to access or write its installation data. |
| Owncast website loads, but its player is offline | Encoder process, Owncast /live destination, Owncast key, and port 1935 reachability |
The web service is reachable, but the incoming RTMP feed may not be publishing. |
| Owncast receives video, but YouTube says offline | Identify the YouTube output topology; check its destination and YouTube Live Control Room key | Owncast ingest and YouTube output are separate configuration paths. |
| Native service starts and then exits or loops | Current-boot journal, executable path, user and group, data permissions, and systemd write restrictions | A startup error, invalid path, or inability to write data may be preventing a stable process. |
| Docker deployment stays down after host restart | Restart policy, Compose startup workflow, persistent data mount, and container logs | The container may not be configured to restart, or its startup or data configuration may need attention. |
Or let it run in the cloud
If your goal is to keep uploaded videos playing on YouTube without depending on an Ubuntu server, encoder PC, or home connection staying on, StreamNeo is a separate cloud option. Upload a recording or build a playlist, add your YouTube stream key, and go live; it loops uploaded videos from the cloud. It is YouTube-only and does not broadcast from a camera.
- Nothing has to stay on at home for the stream to keep running.
- Each slot streams the video as uploaded, up to 4K 60fps, at one flat price per slot.
- It automatically attempts recovery if YouTube drops the stream.
- The first day is free with no card required.
Monthly billing is $9.99 per month. Start your free StreamNeo day.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
