You can run a private live-streaming endpoint by putting a Linux VPS on the public internet, installing NGINX with its RTMP module, defining an RTMP application, and sending a stream from OBS. RTMP handles the ingest connection; if viewers need browser playback, configure the module to create HLS files and serve them over HTTP or HTTPS.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
The reliable order is: harden the VPS, install NGINX, install and load a module that matches your NGINX build, validate the configuration with nginx -t, restrict publishing, configure OBS, and then verify the stream and any HLS playlist from a separate client.
As an Amazon Associate I earn from qualifying purchases.
What this server does
The VPS is the public Linux host and network endpoint. NGINX accepts an incoming RTMP connection on TCP port 1935, places the feed in an application such as live, and can either relay that feed or package it for HTTP clients. OBS is the encoder and publisher; it sends video and audio to the RTMP URL you provide.
RTMP is an ingest protocol, not a browser playback format. Modern browsers generally need an HTTP-delivered format such as HLS or DASH. The NGINX RTMP dynamic module is documented as supporting RTMP, HLS, and DASH, but each output still requires its own configuration and delivery path. See the NGINX RTMP module documentation for the capabilities and directives supported by your package.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
| Part | Role | What it does not provide automatically |
|---|---|---|
| VPS | Public compute, storage, IP address, and network connection | Application-level stream authentication, transcoding, CDN distribution, or a viewer interface |
| NGINX | Web server and process that accepts connections | A video encoder or adaptive-bitrate ladder |
| RTMP module | RTMP ingest plus optional HLS or DASH packaging | Capacity guarantees, viewer authentication, or CDN delivery |
| OBS | Captures, encodes, and publishes your program | Protection of a server that accepts unauthorized publishers |
Plan the deployment before installing packages
Choose a supported Linux image
Select a currently supported distribution image offered by your VPS provider. Package names, service defaults, firewall tools, and the location of NGINX modules vary by distribution. Record the image version and whether the provider supplies NGINX Open Source, NGINX Plus, or a third-party build; the RTMP package must match that choice.
Decide which network paths you need
- Allow SSH only from trusted administrator addresses where practical.
- Open TCP 1935 only when you intend to accept RTMP ingest. If you can restrict it to a known publishing address, do so.
- Open TCP 80 and 443 when you will serve HLS or another HTTP playback format.
- Apply rules in both the provider firewall and the host firewall. The exact commands differ by provider and distribution, so use the current documentation for the image you selected.
Separate publishing from playback
A stream key should be treated as a credential, but a basic RTMP application does not necessarily reject every other stream name. Restrict publishing with source-IP rules when the encoder has a stable address, or use an authentication and network-control design appropriate for dynamic addresses. Playback permissions are a separate decision: a server can allow public HLS viewing while allowing only approved sources to publish.
Make an operations decision about recording
The baseline configuration below uses record off. Enabling recording changes storage consumption, privacy obligations, retention policy, and recovery procedures. Decide this before going live rather than discovering that disk usage grows during a long broadcast.
Provision and harden the VPS
- Create the VPS from the supported Linux image and note its public IPv4 or IPv6 address.
- Create a non-root administrator account and grant it the minimum administrative privilege needed for package and service work. Keep root login and password authentication disabled if your provider and recovery process support that arrangement.
- Install all security updates before exposing the service. Reboot if the distribution requires it, then reconnect using the administrator account.
- Configure the provider firewall and the host firewall. Permit SSH from trusted addresses, permit TCP 1935 only for required ingest, and permit TCP 80/443 for HTTP playback. Do not leave unrelated ports open.
- Set the VPS clock and verify that you can reach it by SSH before changing NGINX. Keep a provider-console recovery path available in case a firewall rule blocks you.
Do not copy firewall commands from a different distribution without checking their syntax and persistence behavior. A rule that works in a test shell but disappears on reboot is not an operational firewall.
Install NGINX
For NGINX Open Source, follow the distribution-specific procedure in the official NGINX Open Source installation guide. On a Debian or Ubuntu system using the distribution repositories, the usual sequence is to update package metadata, install NGINX, start it, and verify the local HTTP response:
sudo apt update
sudo apt install nginx
sudo systemctl enable --now nginx
curl -I http://127.0.0.1Those commands are an example for apt-based systems, not a universal instruction. On another distribution, use its supported package manager and service command. The official guide identifies the usual configuration file at /etc/nginx/nginx.conf and log directory at /var/log/nginx/; package layouts can differ.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Before adding RTMP, confirm that the web server starts cleanly and that the VPS firewall permits the test path you actually intend to use. A successful local curl proves only that NGINX is running on the host; it does not prove that RTMP is installed or that the public firewall is correct.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Install an RTMP module that matches your NGINX build
NGINX Plus on Debian or Ubuntu
The NGINX RTMP page documents this package command for NGINX Plus on Debian and Ubuntu:
sudo apt update
sudo apt install nginx-plus-module-rtmpThat package name is for the NGINX Plus repository. Do not assume it is the correct package for an NGINX Open Source installation.
NGINX Open Source and distribution packages
Open Source distributions and third-party repositories use different names and may ship the module as a dynamic shared object or as a build compiled into NGINX. Search the package metadata for the RTMP module supplied by your exact image and repository, then read that package’s installation notes. A package built for a different NGINX version can fail to load even when the filename looks right.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOne third-party packaging page identifies nginx-module-rtmp version 1.2.2 as released on July 5, 2025. That is a statement about that packaging source, not a universal NGINX Open Source release or a guarantee that your distribution has the same version. Check the package’s current compatibility information at the NGINX Extras RTMP module page.
Load a dynamic module
If your package installs a dynamic module, add its load directive in the top-level NGINX context, before the events, http, or rtmp blocks. The NGINX documentation shows this form:
load_module modules/ngx_rtmp_module.so;The relative path must resolve to the module directory used by your installation. Some packages add a file under a modules-enabled directory automatically; in that case, follow the package instructions instead of loading the same object twice. A duplicate load or a path that does not exist will prevent NGINX from starting.
Always check syntax before reloading:
sudo nginx -t
sudo nginx -s reloadRun the reload only after nginx -t reports a successful test. If validation fails, read the file and line number in the error output, correct that issue, and test again. A failed reload does not replace the running configuration, but repeatedly issuing reload commands will not fix a syntax or module mismatch.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Define the RTMP application
Add an rtmp block at the top level of nginx.conf, alongside the http block rather than inside it. This is a conceptual baseline:
rtmp {
server {
listen 1935;
application live {
live on;
record off;
allow publish <TRUSTED_SOURCE_IP>;
deny publish all;
}
}
}Replace <TRUSTED_SOURCE_IP> with the public address from which the encoder publishes. The allow publish and deny publish all pattern is shown in the OBS private RTMP server guide. It is practical when the source address is stable. If the encoder’s address changes, an allowlist can lock out legitimate broadcasts; use a stronger authentication or private-network design instead of weakening the rule to allow every address.
The application name, live, becomes part of the OBS destination. Keep record off unless you have deliberately planned recording storage and retention. If you need more than one channel, define separate application names or an application-level naming policy and apply the same publishing restrictions to each one.
A stream key is normally sent as the stream name after the application path. Use a high-entropy value and do not paste it into public chat, screenshots, support tickets, or source-control files. Rotate it immediately if it is exposed. The key helps identify the intended feed, but IP controls or an explicit authentication mechanism are still needed when the server must reject unauthorized publishers.
Recommended Free Tools
After saving the configuration, test and reload:
sudo nginx -t
sudo systemctl reload nginxIf the module is missing, NGINX will report an unknown rtmp directive. If the module path is wrong, it will report a failure to load the shared object. Resolve those package or path errors before troubleshooting OBS.
Configure OBS to publish to the VPS
The OBS private-hosting instructions describe the Custom service workflow. In OBS, open Settings, select Stream, choose Custom… as the service, enter the RTMP server address, and place the secret in the stream-key field.
- Set the server to
rtmp://<VPS_ADDRESS>/live, replacing the address with the VPS hostname or public IP andlivewith the application name in your NGINX configuration. - Enter the high-entropy stream key that you created for this channel. Do not append the key to the server URL when OBS provides a separate stream-key field.
- Apply the settings and start streaming. Watch OBS’s connection status and the NGINX logs at the same time.
- Stop the broadcast before changing the key or application. Restart OBS after a material connection-setting change so that an old session is not mistaken for the new one.
The OBS workflow is documented in the OBS private stream hosting wiki. Codec, resolution, and bitrate choices are encoder decisions; this setup guide does not establish a viewer limit or a safe bitrate for a particular VPS. Select settings your uplink, CPU, and intended audience can sustain, then monitor the host while broadcasting.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Add HLS for browser playback
Enable HLS in the RTMP application
RTMP clients can connect directly to the ingest endpoint, but a browser usually needs an HLS playlist and media segments delivered over HTTP. Add the HLS directives supported by your installed module inside the same application. A minimal pattern is:
Free tools Windows power users keep installed
One-click scans. No signup required.
application live {
live on;
record off;
allow publish <TRUSTED_SOURCE_IP>;
deny publish all;
hls on;
hls_path /var/www/hls;
}The exact HLS directives and defaults can vary with the module version. Confirm them against the documentation for the package you installed before adding segmentation, playlist-length, or cleanup settings. Create the path and make sure the NGINX worker can write segment files there; the worker account is commonly named differently across distributions.
Expose the generated files through HTTP
Add an HTTP location in the http server that will serve the HLS directory. This example uses an alias and explicitly declares the common HLS MIME types:
server {
listen 80;
server_name <PLAYBACK_HOSTNAME>;
location /hls/ {
alias /var/www/hls/;
types {
application/vnd.apple.mpegurl m3u8;
video/mp2t ts;
}
add_header Cache-Control no-cache;
add_header Access-Control-Allow-Origin *;
}
}Use a real hostname or address in place of <PLAYBACK_HOSTNAME>. The trailing slashes on both location /hls/ and alias /var/www/hls/ keep URL-to-file mapping predictable. The playlist URL will follow the form http://<PLAYBACK_HOSTNAME>/hls/<STREAM_NAME>.m3u8, where the stream name is the name OBS publishes.
A wildcard CORS header allows any web origin to request the media. That may be suitable for a public stream but is too broad for private content. Replace it with the specific playback origin or remove cross-origin access when all viewers use the same origin. If you expose HLS publicly, prefer HTTPS and configure the certificate and redirect policy before distributing the playback URL.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Some browsers need a JavaScript HLS player, while others can play an HLS URL directly. The server’s responsibility is to return the playlist and segment files with correct MIME types and permissions; player compatibility remains a client-side concern.
After changing either the RTMP or HTTP configuration, run nginx -t and reload only after a successful test. A directory permission problem will usually appear as missing segments or permission errors in the NGINX error log rather than as an RTMP connection failure.
Verify the complete path
- Run
sudo systemctl status nginxand confirm that the service is active. - Run
sudo nginx -tand save the successful result in your deployment notes. - Start OBS and confirm that it reports a connected, actively streaming session.
- Watch the NGINX error and access logs while publishing. Look for connection resets, denied publish attempts, missing files, or permission errors.
- If HLS is enabled, request the generated
.m3u8URL from a separate client after the stream starts. A playlist should not be expected before a publisher has produced segments. - Stop OBS and verify that the playlist and segments are removed or retained according to the module’s cleanup and recording behavior you selected.
Do not call the deployment tested merely because NGINX started. A complete check covers the OBS-to-RTMP connection, publish authorization, segment generation, HTTP delivery, and playback from outside the VPS. The documented procedures above do not constitute an independent capacity or latency test.
Security and ongoing operations
Protect credentials and publishing
- Store the stream key as a credential and rotate it after exposure or staff changes.
- Keep source-IP allowlisting when the encoder address is stable. For mobile or changing addresses, design authentication and network controls that do not rely on a permanent IP.
- Restrict TCP 1935 at the provider and host firewalls. If ingest is idle, close the port rather than leaving it broadly reachable.
- Do not confuse playback authorization with publish authorization. A public HLS URL can coexist with a private publishing path.
Monitor resources and egress
Track CPU, memory, disk space, network egress, and dropped packets. NGINX RTMP forwards or packages streams; it does not automatically provide transcoding, adaptive-bitrate ladders, viewer authentication, or CDN reach. A single encoded feed may be easy to ingest while direct delivery to many viewers consumes substantial outbound bandwidth. No universal viewer limit, latency figure, or bitrate guarantee applies to every VPS, NGINX build, and network path.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsKeep versions aligned
Update NGINX and the RTMP module through a compatible repository and test the configuration after updates. Third-party packages can lag behind or differ from the official NGINX Plus package. Keep a copy of the known-good configuration, document the module package and version, and have a rollback or provider-console recovery method before applying upgrades.
Control storage and privacy
If you turn recording on, set an explicit retention and deletion policy, monitor disk thresholds, and protect recorded files as private data. HLS segment directories also consume storage while a stream is active; ensure cleanup behavior matches your intended replay and compliance requirements.
Troubleshoot common failures
| Symptom | Likely cause | Checks and fix |
|---|---|---|
unknown directive rtmp |
The RTMP module is not installed or not loaded. | Confirm the package, verify the load_module directive is in the top-level context, and run nginx -t. Do not place the directive inside http. |
| NGINX will not start after adding the module | Wrong shared-object path, incompatible module build, or duplicate load. | Read the exact error from nginx -t, compare the module with the installed NGINX version, and remove any second automatic or manual load. |
| OBS cannot connect | Port 1935 is blocked, the address or application path is wrong, or NGINX is not listening. | Check systemctl status nginx, the RTMP listen value, provider and host firewall rules, and the server URL rtmp://<VPS_ADDRESS>/live. |
| OBS connects but publishing is denied | The source address does not match the allowlist. | Inspect the actual public address used by the encoder, update the allow rule, or replace fixed-IP authorization with an authentication design suitable for dynamic addresses. Keep deny publish all after the approved rule. |
| Connection succeeds but viewers receive no HLS | HLS is not enabled, the path is unwritable, or the HTTP location maps to the wrong directory. | Check the application for hls on, verify directory ownership and permissions, inspect the error log, and compare the alias path with the configured hls_path. |
| The playlist loads but segments fail in a browser | Incorrect MIME types, CORS restrictions, HTTPS mixed content, or a stale URL. | Confirm m3u8 and ts MIME mappings, set a deliberate CORS policy, serve the page and media over compatible HTTPS paths, and request the current playlist generated by the active stream name. |
| Dropped packets or unstable output | Insufficient uplink, CPU, memory, or network capacity. | Check host metrics and OBS connection statistics, reduce encoder load or output complexity, and review VPS network limits. Do not assume installing NGINX alone increases capacity. |
| Disk usage keeps increasing | Recording is enabled or segment cleanup is not behaving as intended. | Review record settings, HLS cleanup behavior, retention rules, and filesystem alerts. Delete files only according to your privacy and replay policy. |
When a managed streaming platform is a better fit
Self-hosting is useful when you need control of the server, application path, firewall, and data location and are prepared to maintain packages, security, monitoring, and bandwidth. A managed platform can be preferable when you need built-in transcoding, adaptive-bitrate delivery, viewer authentication, global CDN reach, or an operations team that does not want to maintain an ingest server.
| Decision factor | Self-hosted NGINX RTMP on a VPS | Managed streaming service |
|---|---|---|
| Operational control | Direct control of Linux, NGINX, firewall, files, and update schedule | Provider controls the infrastructure and service lifecycle |
| Ingest and playback | You configure RTMP and optional HLS or DASH output | Protocols and player endpoints are supplied by the service |
| Authentication | You design stream-key, IP, network, and playback controls | Common controls may be integrated, subject to the provider’s product |
| Transcoding and adaptive bitrate | Not automatic; additional software and capacity are required | Often available as a managed feature, but exact formats and limits vary |
| Distribution | Direct VPS egress unless you add a CDN | May include distributed delivery and monitoring |
| Maintenance burden | You patch NGINX and the module, monitor resources, and respond to failures | The provider operates the service, while you manage account and content settings |
| Cost profile | VPS, storage, and outbound bandwidth are your responsibility | Pricing and usage limits depend on the selected service; no comparative price is established here |
Choose the VPS route when its control and predictable architecture outweigh the work of operating it. Choose managed infrastructure when delivery features and reduced maintenance matter more than direct system access.
A repeatable deployment checklist
- Supported Linux image selected and administrator access secured.
- Provider and host firewalls permit only required SSH, RTMP, HTTP, and HTTPS paths.
- NGINX installs and responds locally.
- RTMP module package matches the NGINX build and is loaded once.
rtmpapplication useslive on, an intentional recording policy, and a publishing restriction.- OBS uses the matching application path and a private, high-entropy stream key.
- HLS is enabled only if browser playback is needed, with writable output and a correct HTTP location.
nginx -tpasses before every reload.- Logs, resource metrics, disk retention, key rotation, and recovery access are documented.
That sequence gives you a controlled RTMP ingest server without implying a performance guarantee. Expand it with transcoding, authentication, CDN delivery, or redundancy only when your audience and operating requirements justify the additional components.
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.
