Payload Too Large
What 413 Means
The 413 error on the Nginx Server-Errors indicates payload too large. This typically occurs due to file upload exceeds client_max_body_size.
Nginx returns a 413 error (historically Request Entity Too Large) when an incoming request body heavily exceeds the server's configured maximum size limit.
Technical Background
This is one of the most common Nginx misconfigurations. By default, Nginx enforces a tiny `client_max_body_size` to instantly drop malicious massive payloads.
When the limit is breached, the server forcibly severs the connection and issues the 413 response.
Common Causes
- File upload exceeds client_max_body_size
- Excessively massive JSON payload
- Streaming a very large log file as a single request
Typical Scenarios
- A user tries to upload a 50MB video file, but Nginx is configured to only allow 1MB (the default).
- A massive base64 encoded image crashes the form submission.
What to Know
Increase the `client_max_body_size` directive inside your Nginx `nginx.conf`, block, or server block.
Frequently Asked Questions
Common questions about Nginx 413 error
Add or increase the 'client_max_body_size' parameter in your Nginx configuration file, then reload the Nginx service.