Setting Up Live Streaming Infrastructure on Dedicated Servers

Building a Live Streaming Dedicated Server Setup gives you full control, performance, and reliability for professional-grade streaming. This guide will show you how to create a complete pipeline using open-source tools and best practices.

You will learn how to handle RTMP and SRT ingest, perform CPU and GPU-accelerated transcoding with FFmpeg, and generate HLS and CMAF streams ready for web and mobile delivery. Also, to ensure the live streaming platform is secure, we will cover TLS encryption, token-based security, and monitoring.

This setup guide will help you deploy a powerful and flexible live streaming infrastructure on PerLod's dedicated Linux servers.

Before you start setting up your dedicated server for live streaming, you need to prepare your server.

The recommended hardware specifications:

• CPU Only: You need about 6–10 vCPUs to handle one full HD (1080p) stream that’s transcoded into three quality levels, including 1080p, 720p, and 480p.
• NVIDIA GPU (NVENC): A mid-range NVIDIA GPU can handle many streams efficiently using hardware encoding.
• RAM: Around 8–16 GB of memory is enough for a few simultaneous transcoding ladders.
• Disk: Use a fast NVMe SSD. Keep a separate fast drive or partition for storing HLS segment files. For example, /var/www/hls.
• Network: Choose a 1–10 Gbps network card, depending on how many viewers or streams you plan to support.

Note: If you’re using a GPU dedicated server, ensure your hosting provider supports NVIDIA NVENC or AMD AMF acceleration for FFmpeg.

Then, you must prepare your OS. Here, our OS is Ubuntu 24.04. Run the system update, set the correct timezone, and install the required packages with the command below:

You can also create an app user for your streaming with the commands below:

Next, install the UFW firewall on your Ubuntu server:

Allow the required ports, including 80, 443, 1935 for RTMP, and 9000 for SRT:

Then, enable your UFW firewall with:

At this point, you need to tune a few Linux kernel parameters to handle many connections and reduce latency. You can use the commands below to apply optimized network and system settings:

To apply the changes, run the command below:

Also, you need a domain name that is pointed to your server's IP address.

Once you are done with these requirements, proceed to the next steps to complete the live streaming dedicated server setup.

By default, Ubuntu 24.04 ships with the Nginx RTMP module. To install it, you can easily use the command below:

You can verify your installation with the command below:

Then, you must create a directory for your HLS output and set the correct permissions. To do this, run the commands below:

At this point, you need to set up Nginx to accept RTMP streams and automatically generate HLS (CMAF/fMP4) segments.

You can create or update your Nginx configuration file with the following minimal config:

Once you are done, test your configuration to make sure it is set correctly:

And reload Nginx to apply the changes:

To secure your setup, you can install Certbot and enable HTTPS for your domain. To do this, you can use the following commands:

This creates an HTTPS server block and ensures your HLS paths are served under:

FFmpeg handles transcoding, bitrate ladder generation, and format conversion. A CPU-only setup is perfectly fine for a few 1080p streams.

For a CPU-only installation, you can install FFmpeg using the command below:

Verify the installation with:

For optional GPU-accelerated (NVENC) encoding, you must install drivers with NVENC-capable FFmpeg. Install the drivers and reboot the system with the commands below:

After reboot, verify the GPU with the command below:

Also, you can check that FFmpeg recognizes NVENC. To do this, run:

If you see h264_nvenc or hevc_nvenc, hardware encoding is ready to use.

Modern live streaming dedicated server setups often use SRT (Secure Reliable Transport) for contribution, especially when broadcasting over the public internet. It provides better error recovery and lower latency than RTMP in unstable network conditions.

As you may know, Nginx with the RTMP module cannot accept SRT natively. To integrate SRT streams into the pipeline, we can use FFmpeg as a bridge. It receives the SRT input and forwards it internally to Nginx as RTMP.

You can run a bridge service via systemd. To do this, run the command below:

Enable the service and check the status with:

This bridge allows your server to accept SRT ingest while keeping the rest of your RTMP-based workflow safe and healthy.

To deliver smooth playback across different devices and network conditions, each live stream should be transcoded into multiple quality levels, which is known as an Adaptive Bitrate (ABR) ladder.

In this step, we want to create a fully automated process that converts one incoming stream into three H.264 CMAF/HLS renditions, including 1080p, 720p, and 480p.

While Nginx-RTMP can trigger transcoding automatically using the exec directive, managing these jobs through systemd is more reliable and easier to monitor. Each live stream or stream key runs its own supervised FFmpeg process, ensuring stability and automatic restarts if a transcode stops.

Now create a script at /usr/local/bin/transcode-cmaf.sh that converts an RTMP live stream into multiple HLS video qualities:

Make it executable with:

Then, create a systemd service that automatically runs the transcode script for any stream key:

To apply the changes, run the command below:

Next, you can start the transcode service immediately for a stream key. For example, for the myevent stream key:

Also, you can check live logs from the transcoding process with:

To set up the streaming workflow, follow these steps:

Push from OBS for RTMP with the myevent stream key:

Then run:

For SRT push from OBS on port 9000, then run:

The transcoder will automatically convert your stream into multiple HLS qualities for playback.

For GPU-accelerated NVIDIA NVENC, you need to replace the CPU encoding with:

Or you can target -b:v/-maxrate similarly. For example, for 1080p:

Apply these settings for 720p and 480p.

At this point, you can create a player page that automatically loads and plays the current broadcast.

To create the player HTML file, run the command below:

Then you can access it at:

At this point, you can secure both RTMP publishing with private stream keys and HLS playback with signed URLs using Nginx's secure_link module.

For stream keys in RTMP, OBS uses rtmp://HOST/live/STREAM_KEY. Keep these keys private and rotate them per event.

You can also add a secret and URL pattern in your Nginx server block with:

Then, generate signed URLs in your app:

The player would request signed URLs from your backend instead of accessing HLS files directly.

It is recommended to keep your live stream running smoothly with comprehensive monitoring. You must track viewer counts, stream health, and system resources to quickly identify and resolve issues before they impact your audience.

You can monitor active streams, viewers, and bandwidth usage with Nginx's built-in RTMP statistics page. Add the Nginx RTMP stats to your config file in http{}:

Check for syntax errors and reload Nginx to apply the changes:

Now start monitoring stats with the following curl command:

You can also check system health and process monitoring. You can track transcoder performance, resource usage, and service logs with the commands below:

You can also automatically record your live streams while they're broadcasting to create instant video-on-demand assets for later viewing and distribution. To do this, you can append this to your FFmpeg command:

This creates files like archive.mp4 for later viewing or editing.

That's it, you are done with the live streaming dedicated server setup.

Live Streaming Dedicated Server Setup gives you complete control over quality, scalability, and cost. By using open-source tools like Nginx-RTMP, FFmpeg, and Certbot, you can create a professional-grade streaming workflow. We hope you enjoy this guide.

Subscribe to our X and Facebook channels to get the latest articles for live streaming servers.

For further reading:

Low Latency Game Servers for Faster Performance

Advantages of GPU-Dedicated Servers for Video Editing

Enhancing 3D Rendering on VPS