Nginx Server Errors
Nginx 416 Range Not Satisfiable
Range Not Satisfiable
What 416 Means
The 416 error on the Nginx Server Errors indicates range not satisfiable. This typically occurs due to requesting bytes beyond the file length.
The 416 error occurs when a client requests a specific portion of a file (using the Range header), but that portion technically falls outside the actual file dimensions.
Technical Background
HTTP Range requests are beautiful for streaming video and resuming downloads. Nginx supports this natively.
However, if the client sends a mathematically impossible range, Nginx responds with 416, letting the client know to rethink its math.
Common Causes
- Requesting bytes beyond the file length
- Corrupted download manager seeking a bad offset
- Empty file requested with a byte slice
Typical Scenarios
- A video player tries to skip to byte 5000 of a video, but the video itself is only 3000 bytes long.
- A download accelerator tries to resume a file that was shrunk fully on the server.
What to Know
Clearing the browser or application cache forces a fresh request from the start of the file, resetting the byte range.
Frequently Asked Questions
Common questions about Nginx 416 error
The video player requested a part of the video file that doesn't exist anymore, usually because the file changed on the server.