Use NGINX on a VPS in one of three ways: serve MP4 files directly, provide HLS playlists and segments for on-demand playback, or accept a live RTMP feed and publish it as HLS. Choose MP4 for straightforward prerecorded video, HLS for broad browser/device support and adaptive renditions, and RTMP-to-HLS when an encoder is sending a live event. The correct setup depends more on the source and playback target than on the VPS provider.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
Choose the NGINX streaming architecture first
NGINX is the HTTP delivery layer in all three designs, but the media workflow is different. A prerecorded MP4 already contains its audio and video, so NGINX can deliver it without transcoding. HLS breaks compatible MP4 or MOV media into a playlist and media fragments. A live workflow adds an ingest protocol, usually RTMP, and then creates HLS output for viewers.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Architecture | Input | What viewers request | Best fit | Operational cost |
|---|---|---|---|---|
| Direct MP4 | Finished MP4 file | One .mp4 URL |
Simple video-on-demand, downloads, small audiences | Lowest; no segmentation or transcoding |
| MP4 pseudo-streaming | Finished MP4 file | MP4 URL with time-range seeking | On-demand playback where viewers need to jump into a file | Low, but metadata placement and file layout matter |
| HLS video on demand | MP4 or MOV containing H.264 video and AAC or MP3 audio | An .m3u8 playlist plus media fragments, commonly .ts |
Browser/device compatibility, segmented delivery, multiple renditions | More files, storage management and playlist handling |
| RTMP ingest to HLS | Live encoder publishing RTMP | HLS playlist and live fragments over HTTP(S) | Live events where viewers use an HLS-capable player | Highest; ingest, segment rotation and often transcoding |
These capabilities come from separate NGINX modules. The MP4 pseudo-streaming module is ngx_http_mp4_module; HLS support for MP4 and MOV is provided by ngx_http_hls_module; and RTMP, HLS and DASH ingest/output are supplied by an additional RTMP module. Check what your distribution packages and build actually include before writing a configuration.
Prepare the VPS
Use a supported Linux image and a verified NGINX package
Start with a current Ubuntu, Debian or another Linux release supported by your NGINX package source. Installing from verified official packages reduces the chance of receiving an old binary without the module you need. The official installation process includes importing the NGINX signing key and repository when the distribution package is not sufficient.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
A Debian/Ubuntu-style installation begins with the distribution’s normal package commands:
sudo apt update
sudo apt install nginx
sudo systemctl enable --now nginx
nginx -v
nginx -V 2>&1Use the output of nginx -V to inspect compile-time options. A package can have NGINX itself but omit the MP4 or HLS module, and RTMP is commonly delivered as a separate dynamic package or requires a custom build.
Open only the ports you need
- SSH: Keep the administration port reachable only from the networks or addresses that need it where possible.
- HTTP (80) and HTTPS (443): Use these for media delivery and, if required, the HLS playlist and fragments.
- RTMP (normally 1935): Open this only when an encoder must publish directly to the VPS. If ingest is handled elsewhere, do not expose it.
Do not assume that a high-speed VPS network makes every stream viable. Outbound traffic grows with the number of simultaneous viewers and the bitrate of each rendition. Transcoding adds a separate CPU and memory load, while HLS retains many small files that consume storage and inode capacity.
Separate upload, source and playback paths
Create a source directory that publishers or your conversion process can write to, and a playback directory that NGINX can read. Do not make the entire home directory or a writable upload directory web-accessible. Assign ownership and permissions so the NGINX worker can read media but cannot modify application files.
sudo mkdir -p /srv/media/vod /srv/media/hls
sudo chown -R root:nginx /srv/media
sudo find /srv/media -type d -exec chmod 750 {} ;
sudo find /srv/media -type f -exec chmod 640 {} ;The group name differs by distribution; some systems use www-data instead of nginx. Confirm the worker user in the NGINX configuration before applying permissions.
Serve a prerecorded MP4
Basic static delivery
For a file that only needs progressive download, an ordinary HTTP location is enough. A minimal server block might look like this:
server {
listen 80;
server_name media.example.test;
location /video/ {
alias /srv/media/vod/;
types { video/mp4 mp4; }
add_header Accept-Ranges bytes;
}
}Place a file such as /srv/media/vod/episode-01.mp4 in the directory, then test the URL with a browser or:
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
curl -I http://media.example.test/video/episode-01.mp4The alias path and URL prefix must end consistently with a slash. If a request returns 404, check the resolved filesystem path, permissions and the active server block selected by the Host header.
Enable MP4 pseudo-streaming for time-based seeking
The ngx_http_mp4_module provides pseudo-streaming for MP4 files. A compatible player can ask for a time range with start and end query parameters, allowing a viewer to seek without downloading the entire file first.
location /video/ {
alias /srv/media/vod/;
mp4;
mp4_buffer_size 1m;
mp4_max_buffer_size 5m;
}The buffer directives are optional examples; tune them only after observing memory use. The module is not built by default and requires NGINX to be compiled with --with-http_mp4_module. If nginx -V does not show that option, install a package containing the module or rebuild NGINX before adding mp4;.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A player may generate a request conceptually like /video/episode-01.mp4?start=60&end=120. The exact request format is controlled by the player. The MP4 module parses the file’s metadata and prepares the requested portion; it is not a replacement for true segmented streaming.
Put the MP4 metadata where startup can use it
MP4 files contain a metadata structure commonly called the moov atom. If it is at the end of a large file, NGINX may need to read and rewrite the entire file before serving a requested range. That increases CPU, memory and disk I/O and can make startup appear stalled. Prepare files with metadata positioned for fast startup before putting them in the playback directory. Verify the result with the media-processing tools used by your workflow rather than assuming every export has the same layout.
Generate HLS for prerecorded video
What the HLS module delivers
The ngx_http_hls_module provides server-side HLS support for MP4 and MOV media. HLS playback uses a text playlist ending in .m3u8 and media fragments, commonly ending in .ts. The documented module supports H.264 video and AAC or MP3 audio. Files encoded with other codecs must be converted before this workflow can work.
HLS is useful when a single MP4 URL is not enough: players can fetch small pieces, recover from an interrupted request, and select among separate renditions if you create them. It also gives you a common HTTP(S) delivery path for prerecorded and live output.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows 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 reinstallRank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Map an HLS location
Enable the module available in your build, then define a media location. A representative server block is:
server {
listen 80;
server_name media.example.test;
location /hls/ {
alias /srv/media/vod/;
hls;
hls_fragment 5s;
types {
application/vnd.apple.mpegurl m3u8;
video/mp2t ts;
}
add_header Cache-Control no-cache;
}
}The official example uses a five-second fragment. That number is a configuration example, not a measured performance guarantee. Shorter fragments can reduce the amount of media a player waits for, but they create more requests and more filesystem activity; longer fragments reduce request overhead but can increase the time before a new segment is available. Choose a duration based on the latency and request-rate goals of your service.
Directive names and the way a build maps source files can differ between the packaged HLS module and other HLS implementations. Run nginx -t after adding the location. If NGINX reports an unknown hls directive, the required module is absent or not loaded; do not leave the directive in a production configuration hoping it will be ignored.
Test the playlist and fragments
- Place a compatible MP4 or MOV in the directory visible to the HLS location.
- Request the generated
.m3u8URL from a client that supports HLS. - Inspect the playlist text and confirm that every referenced fragment URL resolves with an HTTP success response.
- Test seeking, a slow connection and a player restart. A playlist that loads while fragments return 404 usually indicates a path, permission or retention problem rather than a codec problem.
For public delivery, serve the playlist and fragments over HTTPS. If a page on HTTPS requests an HTTP playlist, browsers can block it as mixed content.
Recommended Free Tools
Accept a live RTMP feed and publish HLS
Install or build the RTMP module
RTMP is not part of the standard NGINX HTTP core. The RTMP dynamic module enables streaming in several formats, including RTMP, HLS and DASH. Depending on the Linux distribution, you may find a separately packaged dynamic module. Otherwise, compile NGINX with the third-party RTMP module as a statically linked module using the --add-module configure option.
For a dynamic module, load the file near the top of the main configuration, before the events block. The filename and directory are distribution-specific:
load_module modules/ngx_rtmp_module.so;Use the path installed by your package, not a path copied from another operating system. For a source build, the important part of the configure invocation is the module option:
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
MODULE_DIR=/opt/nginx-rtmp-module
./configure --add-module="$MODULE_DIR" <other-options-used-by-your-build>
make
sudo make installA source build must preserve the modules and paths required by your existing installation. Replacing a distribution binary without copying its service file, configuration path and log locations can make routine updates harder.
Configure an ingest application
A typical RTMP configuration has a server listening for publishers and an application that turns the incoming stream into HLS files:
rtmp {
server {
listen 1935;
application live {
live on;
hls on;
hls_path /srv/media/hls/live;
hls_fragment 5s;
}
}
}
http {
server {
listen 80;
server_name media.example.test;
location /live/ {
alias /srv/media/hls/live/;
types {
application/vnd.apple.mpegurl m3u8;
video/mp2t ts;
}
add_header Cache-Control no-cache;
}
}
}This is a pattern, not a universal drop-in file. RTMP module builds expose different directives and defaults, and the HLS directory must exist and be writable by the NGINX worker. Keep the ingest application and the HTTP playback location aligned: if HLS files are written to one directory but the alias points to another, the publisher can connect while every viewer receives 404 responses.
Publish with a protected stream key
An encoder normally publishes to an RTMP application URL such as rtmp://media.example.test/live with a stream name or key. Treat that key as a credential. Use an unguessable value, rotate it when a publisher changes, and restrict who can reach port 1935. The RTMP guide documents module configuration but does not prescribe one authentication design, so test the authorization method you add with both valid and invalid keys.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Do not expose a writable HLS directory as an upload endpoint. Publishers should write through the RTMP application, while viewers receive only generated playlists and fragments over HTTP(S).
Handle codecs and transcoding deliberately
The RTMP module can package a compatible incoming stream, but it does not make every codec playable in every browser. HLS output for the documented module expects H.264 video and AAC or MP3 audio. If the encoder sends another codec, use a media processor such as FFmpeg to transcode or re-encode before packaging. The correct command depends on the source codec, frame rate, audio layout, keyframe interval, target resolutions and the number of renditions; there is no single command that is correct for every live input.
Transcoding can dominate VPS resource use. Measure CPU, memory and thermal behavior under the maximum number of simultaneous outputs, and leave headroom for NGINX, the operating system and traffic spikes. If you need adaptive bitrate, create separate renditions and a master playlist, then test that the player can switch between them without broken segment references.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Validate and reload every configuration change
- Check syntax and module directives:
sudo nginx -t. - Fix every error before touching the running service. An unknown directive usually means a missing module; a permission error usually points to the media or HLS directory.
- Reload without dropping existing connections:
sudo nginx -s reloador the equivalent service-manager reload command. - Watch the error log while making a test request. Record the exact URI, HTTP status and filesystem path so a 404 can be distinguished from a codec or player failure.
Never skip the syntax test. A failed reload leaves the old configuration running, which can look like a successful change until a new worker or a new stream exposes the error.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteSecure browser delivery and publishing
Use TLS for viewer traffic
Serve the website, MP4 files, playlists and fragments over HTTPS. Install a certificate for the media hostname and redirect ordinary HTTP requests where appropriate. Besides protecting traffic in transit, HTTPS avoids mixed-content blocking when the player page is also HTTPS.
Protect ingest separately from playback
- Keep RTMP ingest closed unless a publisher needs it.
- Use a per-channel or per-event stream key and do not place it in public documentation or client-side playback code.
- Separate the RTMP publishing hostname or firewall rule from the viewer hostname when that makes access control easier.
- Limit write permissions to the RTMP/HLS directories and periodically remove abandoned segment files.
HTTP authentication for a playlist does not automatically authenticate RTMP publishing, and a stream key does not automatically protect the viewer URL. Treat those as separate control planes.
Operate the stream after launch
Monitor the four resources that fail first
- Outbound bandwidth: Watch sustained egress and peaks. Every additional viewer consumes the bitrate of the selected rendition, plus protocol and encryption overhead.
- CPU and memory: Observe NGINX and any transcoder separately. A server can deliver a prerecorded file comfortably but fail when live encoding starts.
- Disk and inodes: HLS produces many short-lived files. Monitor both free bytes and inode usage, and enforce a retention policy.
- Worker and application errors: Alert on NGINX error-log growth, failed reloads, repeated 404s and publisher disconnects.
NGINX documentation describes the modules’ functionality but does not provide a universal VPS bandwidth or sizing formula. Estimate demand from the number of concurrent viewers and the bitrate of each rendition, then validate that estimate with load and soak tests for your actual encoders and audience geography.
Keep HLS retention bounded
Live HLS should retain enough recent fragments for a player to recover from a brief delay, but not every segment ever created. Configure the module’s deletion and playlist behavior for the version you installed, and verify that old files disappear. If disk usage rises continuously, inspect the HLS directory, the configured playlist window and any process that may be keeping files open.
Patch the operating system and NGINX
Keep the VPS kernel, NGINX package, modules and media tools current. NGINX release notes include security fixes that can affect media modules; check the current release and advisory before pinning a version-specific installation command. Test a package upgrade on a staging VPS because a module built for one NGINX version may not load into another.
Troubleshoot by symptom
| Symptom | Likely causes | Checks and fixes |
|---|---|---|
nginx -t says “unknown directive mp4” or “unknown directive hls” |
The module is not installed, loaded or compiled into this binary | Inspect nginx -V, verify the dynamic-module file and load_module path, then install or rebuild the required module. |
| MP4 plays but seeking fails | The MP4 module is absent, the player does not send time parameters, or metadata is poorly placed | Confirm --with-http_mp4_module, test a known compatible player and prepare the file with startup metadata positioned correctly. |
| Playlist loads but fragments return 404 | Wrong alias, missing permissions, stale playlist references or premature deletion |
Compare the fragment URI with the actual HLS directory, inspect ownership and logs, and check segment retention. |
| Publisher cannot connect | Port 1935 is blocked, the RTMP module is not loaded, the application name is wrong or the stream key is rejected | Check the firewall, module load, RTMP log and exact publish URL. Test from an allowed network. |
| Viewers see a black screen or unsupported media | Input codec or audio format is outside the HLS module/player’s supported set | Inspect the source stream and transcode to H.264 video with AAC or MP3 audio as required by the selected workflow. |
| Live playback falls further behind | Transcoding is overloaded, fragments are too long for the latency target, or the VPS is bandwidth-constrained | Measure encoder CPU, segment availability and egress; reduce unnecessary renditions, adjust fragment policy and move to a larger or better-connected VPS when measurements justify it. |
Decide between MP4, HLS and RTMP-to-HLS
Choose direct MP4 or pseudo-streaming when
- Your source is prerecorded and already encoded in a format your audience can play.
- You want the smallest configuration and do not need adaptive renditions.
- Time-based seeking is important but a playlist-and-segment workflow would add unnecessary storage and complexity.
Choose HLS video on demand when
- You need playlist-based delivery for a wider range of clients or a segmented cache-friendly workflow.
- Your source is MP4 or MOV with H.264 video and AAC or MP3 audio, or you are prepared to transcode it.
- You can manage generated fragments, playlist URLs, HTTPS and storage cleanup.
Choose RTMP ingest to HLS when
- A camera, encoder or production system must publish a live feed to your VPS.
- Viewers should consume HTTP(S) HLS rather than connect directly to an RTMP endpoint.
- You can secure the publishing key, monitor segment generation and budget for transcoding when the input does not match the delivery codec.
The practical sequence is: identify whether the source is live, select the playback protocol, verify the corresponding NGINX module, configure the smallest working path, run nginx -t, reload, and then test with real media under expected traffic. MP4 pseudo-streaming, HLS and RTMP-to-HLS are complementary tools, not interchangeable switches.
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.
