Run FFmpeg in the foreground as a systemd service, then set Restart=on-failure to relaunch it after errors—or Restart=always if even a clean exit should start another stream process. Add a retry delay, enable the unit at boot, and confirm the actual broadcast in YouTube Live Control Room: systemd can restart an encoder, but it cannot by itself guarantee a healthy stream.
Configure the service unit
Create a unit file such as /etc/systemd/system/youtube-stream.service. This illustrative template assumes a local video file and an installed FFmpeg build with the required options. Replace the user, paths, input, ingest URL, and key with values appropriate to your host and YouTube Live Control Room.
As an Amazon Associate I earn from qualifying purchases.
[Unit]
Description=YouTube live stream encoder
Wants=network-online.target
After=network-online.target
[Service]
Type=simple
User=streamer
WorkingDirectory=/srv/stream
ExecStart=/usr/bin/ffmpeg -re -stream_loop -1 -i /srv/stream/loop.mp4 -c:v libx264 -preset veryfast -b:v 4500k -maxrate 4500k -bufsize 9000k -c:a aac -b:a 128k -f flv rtmps://YOUR_INGEST_URL/YOUR_STREAM_KEY
Restart=on-failure
RestartSec=10s
[Install]
WantedBy=multi-user.targetKeep FFmpeg as the main process
Type=simple lets systemd supervise the process started by ExecStart. Run FFmpeg in the foreground; do not add a backgrounding option that makes the command exit while the encoder continues separately. The example uses a looping local file, H.264 video, AAC audio, and illustrative bitrate values. It is not a tested configuration or a guarantee of compatibility with your FFmpeg build, stream-key format, or endpoint.
Choose restart behavior deliberately
Restart=on-failurerestarts after a failure, such as an unsuccessful exit or abnormal termination, but not after a clean exit. Choose it if a clean FFmpeg exit should leave the stream stopped.Restart=alwaysrestarts after clean exits as well as failures, signals, and timeouts. Choose it if FFmpeg exiting successfully should still be followed by another run.- An explicit manager stop, such as
systemctl stop youtube-stream.service, is not automatically reversed by these restart policies. RestartSec=10sin the example is a chosen pause, not a universal setting. A delay gives a destination or network time to recover; too-short retries can create a rapid failure loop.
Automatic retries are subject to systemd start-rate limits. If FFmpeg fails repeatedly in a short period, systemd may stop scheduling starts until the limit window allows recovery or an operator intervenes. The systemd project’s current configuration reference lists manager defaults of a 10-second interval and five attempts, but these settings are configurable and may differ on your distribution or installed release. Check man systemd.service, man systemd.unit, and man systemd-system.conf on the target host before relying on version-specific behavior. See the systemd service documentation and systemd system configuration reference.
#1 Best Overall
- Includes Raspberry Pi 4 4GB Model B with 1.5GHz 64-bit quad-core CPU (4GB RAM)
- Includes Pre-Loaded 32GB EVO+ Micro SD Card (Class 10), USB MicroSD Card Reader
- CanaKit Premium High-Gloss Raspberry Pi 4 Case with Integrated Fan Mount, CanaKit Low Noise Bearing System Fan
- CanaKit 3.5A USB-C Raspberry Pi 4 Power Supply (US Plug) with Noise Filter, Set of Heat Sinks, Display Cable - 6 foot (Supports up to 4K60p)
- CanaKit USB-C PiSwitch (On/Off Power Switch for Raspberry Pi 4)
Enable, start, and inspect the service
- Save the file, then reload systemd’s unit definitions:
sudo systemctl daemon-reload. - Enable the service for the configured boot target and start it now:
sudo systemctl enable --now youtube-stream.service. - Check the unit’s current state:
sudo systemctl status youtube-stream.service. - Follow its logs while diagnosing startup or runtime problems:
sudo journalctl -u youtube-stream.service -f. - Open YouTube Live Control Room and verify the incoming preview and stream health. An active systemd unit proves only that systemd considers the service active; it does not prove viewers are receiving a healthy broadcast.
After editing the unit, run daemon-reload again before restarting the service. Command behavior and available options can vary across distributions; use the local systemctl and systemd manuals as the authority for the installed system.
Set up YouTube ingest and encoder settings
Use the current endpoint and protect the key
Get the stream URL and key from YouTube Live Control Room rather than copying a generic endpoint from an example. YouTube describes stream keys as credentials used by an encoder to send its feed; treat the key like a password. If it is exposed, reset it in YouTube and update the service configuration. YouTube recommends RTMPS where supported; it is RTMP over TLS/SSL. See YouTube’s live stream settings guidance and YouTube’s encoder setup guidance.
Rank #2
- Broadcom BCM2711, quad-core Cortex-A72 (ARM v8) 64-bit SoC @ 1. 5GHz
- 2. 4 GHz and 5. 0 GHz IEEE 802. 11b/g/n/ac wireless LAN, Bluetooth 5. 0, BLE
- 2 × USB 3. 0 ports, 2 x USB 2. 0 Ports
- 2 × micro HDMI ports supproting up to 4Kp60 video resolution
- Micro SD card slot for loading operating system and data storage
The example places the key in the unit’s command line. Restrict access to the unit file and avoid sharing logs or configuration that might reveal credentials. For a production setup, consider a protected configuration mechanism supported by your system and FFmpeg workflow.
Free tools Windows power users keep installed
One-click scans. No signup required.
Match bitrate to resolution and available upload
YouTube’s published H.264 recommendations include 5 Mbps for 1080p at 30 fps and 14 Mbps for 4K at 30 fps. These are platform recommendations, not evidence that a particular connection can sustain them. YouTube advises leaving 20% upload headroom; account for the stream’s bitrate and any other concurrent upload use, and monitor actual stream health. See YouTube’s encoder settings and bitrate recommendations and YouTube’s streaming tips.
Rank #3
- Broadcom BCM2711, Quad core Cortex-A72 (ARM v8) 64-bit SoC @ 1.5GHz
- 1GB, 2GB, 4GB or 8GB LPDDR4-3200 SDRAM (depending on model)
- 2.4 GHz and 5.0 GHz IEEE 802.11ac wireless, Bluetooth 5.0, BLE Gigabit Ethernet
- 2 USB 3.0 ports; 2 USB 2.0 ports.
- Raspberry Pi standard 40 pin GPIO header (fully backwards compatible with previous boards)
The sample command’s 4500k video bitrate, 9000k buffer, and 128k audio bitrate are examples only, not YouTube’s universal settings. Choose settings for your resolution, frame rate, codec, encoder capacity, and measured network conditions. Test a private or otherwise suitable stream before depending on it continuously.
Troubleshoot restarts and missing video
| Symptom | Likely cause | What to check or do |
|---|---|---|
| The service fails immediately | Wrong FFmpeg path, unsupported option, missing input, or invalid unit configuration. | Read systemctl status and journalctl output; verify the executable, input path, permissions, and installed FFmpeg options. Test the command as the configured service user. |
| It starts and then stops without retrying | The process exited cleanly while the unit uses Restart=on-failure, or the unit was intentionally stopped. |
Choose Restart=always if clean exits should trigger a new run. A manager-issued stop is intentional and is not undone by the restart policy. |
| Restarts stop after repeated errors | Systemd start-rate limiting may have been reached. | Inspect the unit status and journal for rate-limit messages. Fix the underlying failure first, then start the service again; review the installed systemd manuals before changing rate-limit settings. |
| Service is active but YouTube has no healthy stream | The encoder may be stalled, the endpoint or key may be wrong, the input may be unavailable, or the network may not sustain the bitrate. | Check FFmpeg logs, current YouTube ingest details, source-file access, upload capacity, and YouTube’s stream-health indicators. Restarting an active but hung process requires a failure signal or a separate health check. |
| Stream drops during network trouble | The connection or upload capacity is insufficient or unstable. | Measure sustained upload, leave YouTube-recommended headroom, and review its connectivity guidance. A process restart cannot repair a network path. |
What systemd recovery does—and does not—cover
Systemd can launch the encoder at boot and restart it when its process exits according to the policy you chose. It cannot ensure the input file exists, repair invalid credentials, restore a broken network, or necessarily detect an encoder that remains alive but has stopped sending usable video. Check YouTube’s actual stream health as well as the service state. YouTube also has copyright and other live-stream rules; a continuously available encoder does not grant rights to the music or video being broadcast. Review YouTube’s live streaming guidance and its applicable copyright policies before streaming content.
Rank #4
- Vilros Complete Starter Kit for Pi 4 Includes Raspberry Pi 4 Model B Board and all the accessories you need to get started.
- 9-PART KIT WILL HAVE YOU READY TO GET UP AND RUNNING: Kit Includes 1. Raspberry Pi 4 Model B Board 2. Case With Easy to connect Built-in fan 3. 64GB Micro SD card Preloaded with RP OS 4. Vilros Pi 4 Compatible Power Supply with Inline on/off switch (power supply color may vary white/black) 5. Micro HDMI to Standard HDMI cable (5ft) 6. Micro SD to USB adapter to reflash card if desired 7. Neoprene Storage Bag to store all parts when not in use 8. Set of 4 Heatsinks 9. Vilros QuickStart Guide instruction booklet for Pi 4
- PASSIVE & ACTIVE COOLING: The included case is well-vented and the kit also includes a set of heatsinks with thermal stickers for easy application and a pre-installed fan to keep the board cool in any use.
- CONVENIENT ACCESSORIES: The power supply features an inline on/off switch neoprene bag that holds and protects all the parts when not in use and the QuickStart guide is updated and written for Raspberry Pi 4.
- IMPORTANT: Kit does NOT include Keyboard, Mouse or Monitor
Or let it run in the cloud
If you want a YouTube loop without maintaining a host, StreamNeo runs uploaded videos from the cloud. The setup is three steps: upload a recording or build a playlist, add your YouTube stream key once, and go live. Your computer and home connection do not have to stay on. StreamNeo automatically recovers if YouTube drops the stream, and uploaded video streams as made up to 4K 60fps at one flat price per slot, without re-encoding or quality tiers.
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 →The first day is free with no card (one free day per account). The monthly option is $9.99 per month. You can also choose daily, weekly, six-month, or yearly billing; the product is the same on every plan, with the billing length changing. UPI and cards are supported in India; card checkout is available worldwide. See StreamNeo pricing, then start your free StreamNeo day.
Quick Recap
Best Value
- Includes Raspberry Pi 4 4GB Model B with 1.5GHz 64-bit quad-core CPU (4GB RAM)
- CanaKit 3.5A USB-C Power Supply with Noise Filter (UL Listed) specially designed for the Raspberry Pi 4 (5-foot cable)
- CanaKit USB-C PiSwitch (On/Off Power Switch)
- Set of 3 Aluminum Heat Sinks for the Raspberry Pi 4
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.
