Back

nginx-rtmp VPS Hosting, Pre-Installed

An nginx-rtmp server takes the live stream from software like OBS and passes it on to YouTube and similar platforms at the same time. After you order, the server sets itself up, and the connection address and secret stream path appear in your panel. The stream isn't re-encoded, only relayed, so encoding stays on the computer you broadcast from and the server needs no graphics card.

How big is your publication?

Total$2.58/mo

Prices include VAT.

Scale RAM and CPU up or down whenever you like. Disk can only grow, so start small.

What's installed on your nginx-rtmp server?

  • Nginx and nginx-rtmp-module, from the 26 October 2026 build of the tiangolo/nginx-rtmp image
  • RTMP input on port 1935, with recording off
  • A randomly generated secret stream path, so nobody can publish without it
  • A separate file for relay targets: /opt/seturack/nginx-rtmp/hedefler.conf
  • Firewall with only ports 22 and 1935 open

What size do you need for nginx-rtmp?

There's no official RAM figure for nginx-rtmp. Since the server doesn't re-encode anything, 1 GB of RAM and 1 CPU are generally enough to start, as a rule of thumb, and 2 GB makes sense if you relay to many targets. Recording is off, so no video is written to disk and you need little of it. The network is where the use shows up: each target takes as much outbound bandwidth as your stream's bitrate, so 6000 kbps to three targets comes to about 18 Mbps. Traffic is unlimited.

UseSizePriceChoose
New publication 1 GB RAM · 1 vCore · 25 GB NVMe $2.58/mo
Growing publication 2 GB RAM · 1 vCore · 40 GB NVMe $4.01/mo
Busy publication 4 GB RAM · 2 vCore · 60 GB NVMe $6.89/mo

Who is it for?

  • Streamers who want to send one stream to several platforms at once
  • Streamers whose home upload speed can't cover several platforms
  • Developers who need their own RTMP endpoint
  • Anyone who'd rather manage target platforms on the server and leave OBS alone

What happens after you order?

  1. Set the size and complete your payment.
  2. Your server starts and nginx-rtmp installs itself.
  3. On the Overview tab of your panel, copy the Connection address row. It looks like rtmp://IP-address/secret-path.
  4. In OBS, go to Settings, then Stream, and set the service to Custom. Enter this address as the Server and any name you like as the Stream Key.
  5. To relay to another platform, connect over SSH and add that platform's push line to hedefler.conf.
  6. Run docker compose restart rtmp in /opt/seturack/nginx-rtmp, then start your stream.

With every server

  • Daily backups included in the price
  • Unlimited traffic
  • Full root access
  • Scale RAM and CPU up or down later, and grow the disk
  • Location: Istanbul · IST-1.

Good to know

  • A secret path stands in for publisher authentication. Anyone with the address can publish to it or watch, so don't share it.
  • The connection is plain RTMP, and RTMPS isn't installed. That means you can't relay directly to a platform that only accepts RTMPS.
  • There's no web interface, viewer page or chat here. You configure everything from a file over SSH.
  • Running docker compose restart rtmp cuts any stream in progress, so change targets before you go live.
  • You hold the rights and legal responsibility for what you stream, and you must follow each platform's rules. Platform stream keys sit in hedefler.conf, so protect that file.
  • The software needs no fee or account, and nginx-rtmp-module is BSD-licensed. Target platform accounts and version updates are your responsibility.

nginx-rtmp questions and answers

How do I connect OBS to an nginx-rtmp server?

In OBS, go to Settings, then Stream, and set the service to Custom. Paste the Connection address value from your panel as the Server, and enter any name as the Stream Key, such as stream. You don't need a port, since RTMP uses 1935 by default.

How do I relay my stream to YouTube with nginx-rtmp?

Get your stream key from YouTube. Connect over SSH, add the line push rtmp://a.rtmp.youtube.com/live2/YOUR-STREAM-KEY; to hedefler.conf, then run docker compose restart rtmp in /opt/seturack/nginx-rtmp.

How much RAM does nginx-rtmp need?

There's no official figure. The stream isn't re-encoded, so 1 GB of RAM and 1 CPU are generally enough to start, as a rule of thumb, with 2 GB for many targets. If that falls short, scale up from your panel. The server restarts once and your address stays the same.

How many platforms can I stream to at once?

There's no fixed number. You add a separate push line to hedefler.conf for each platform, and each target uses as much outbound bandwidth as your stream's bitrate. More targets mean more network use, and traffic is unlimited.

Does an nginx-rtmp server transcode video?

No. This install relays the stream as it is, so resolution and bitrate are whatever you set in OBS. CPU load stays low as a result, and having no graphics card doesn't matter here. Choose OBS settings your target platforms accept.

Can viewers watch from this server?

There's no viewing page installed. A player like VLC can open rtmp://IP-address/secret-path/stream-name, but that exposes the secret path. For a wider audience, relay the stream to platforms instead.

Read more and see similar apps