413 Request Entity Too Large (nginx/1.6.2)

Have a check of the client_max_body_size as the default is 1MB. /etc/nginx/nginx.conf

Syntax: client_max_body_size size;
Default:    client_max_body_size 1m;
Context:    http, server, location

Sets the maximum allowed size of the client request body, specified in the “Content-Length” request header field. If the size in a request exceeds the configured value, the 413 (Request Entity Too Large) error is returned to the client. Please be aware that browsers cannot correctly display this error. Setting size to 0 disables checking of client request body size.

http://nginx.org/en/docs/http/ngx_http_core_module.html

I normally set mine to

client_max_body_size 100M;

And to check PHP settings

grep -E "upload_max_filesize|memory_limit|post_max_size" /etc/php5/fpm/php.ini

Thanks for quick response , Let me try and I'll respond soon

No problem, kinda live on this forum :P

No reason why it shouldn't work!

Hey bashy , I was working on the issue and here is where I got stuck ,First, i couldn't find the line "client_max_body_size " in my conf file and so I had to add it within http context, but still getting the same error. Also I can only see event, http, and mail context , neither server nor location in my config file. Not sure if am adding the line where it is supposed to be. Please help

BTW am new to command line editor like vim so I had to read tutorial on how to use it :D , that's why I respond late

I normally just use nano for quick edits. Here's an example of my nginx.conf file https://bashy.im/o/nginx.txt

This is how it looks like : http://abdullahtaher.com/wp-content/uploads/2015/02/error.png

I don't think if the problem is because of MB's I gave to each line

Seems fine. Have you restarted nginx and php5-fpm?

When I reload nginx I got this error : "client_max_body_size" directive invalid value in /etc/nginx/nginx.conf . That is the line I have added.

Screenshot of conf seems to have 404'd so can't see it. Copy the line you added here again? Might be missing a semicolon.

Screenshot ; http://abdullahtaher.com/content/uploads/2015/02/error.png

Semicolon is there.

I have changed "MB to M" i.e.50MB to 50M and now it is working...Really appreciate your help @bashy

Oh right, yeah it's just M, no B needed :)

No problem, enjoy Laravel and Linux!

Hello Everyone,

So i have the same problem. i use Forge with a load balancer. I changed the php.ini settings on both nodes and added client_max_body_size 10M in the http part of both nginx.conf After a restart i still get 413 (Request Entity Too Large) on my POST.

Has this method changed in 5 months because i'm clueless i hope someone can help :)

@tsm200 No it has not and it could be another setting stopping you. What exactly are you uploading/sending in the form? (Sizes/amount of fields etc).

@bashy I'm trying to upload 1 image at the time, when the size is above 1.5 MB i get the 413

@tsm200 Could be because of something else then. Can you show me both the PHP settings and Nginx?

@bashy https://s3.eu-central-1.amazonaws.com/siteopslag/oshu/php.ini https://s3.eu-central-1.amazonaws.com/siteopslag/oshu/nginx.conf

@tsm200 By the way, post_max_size should be larger than upload_max_filesize since you should be able to upload a file and allow for other POST data. Other than that I'm not sure why it's not working.

@bashy Finally it hit me! I set everything fine on my nodes but i forgot to set client_max_body_size 10M to my loadbalancer :S Thanks for the help!

@jclermont how do you set it up in forge?

Server Details -> Meta. You can specify a max file size in megabytes. This updates PHP and nginx.

thanks

One bit of info on this - if you went ahead and tried to manually change this on nginx.conf and php.ini - don't just go and try it on forge. It will cause a duplicate client_max_body_size directive, causing your nginx service to fail on startup because the conf file tests will fail due to that duplicate directive.

This seems to be because, at the time of writing this, Forge updates a different conf file uploads.conf. I did not bother to look for the location of this file, however I quickly undid my edit of the nginx.conf and simply resolved the issue by managing this from forge like the rest of the stuff i normally do on the server.

It seems to have resolved the 413 error for now, as I have gotten no new reports of it and my tests couldn't replicate any new 413 errors.

Forge really needs to add a note to the "Max File Upload Size" form clearly stating that it changes nginx config too.

I found the setting on Forge under Server Details > PHP

Flawless!