nginx - client max body size has no effect

Question

nginx keeps saying client intended to send too large body  Googling and RTM pointed me to client max body size  I set it to 200m in the nginx conf as well as in the vhost conf  restarted Nginx a couple of times but I m still getting the error message   Did I overlook something  The backend is php-fpm  max post size and max upload file size are set accordingly

User · Answer

I meet the same problem  but I found it nothing to do with nginx  I am using nodejs as backend server  use nginx as a reverse proxy  413 code is triggered by node server  node use koa parse the body  koa limit the urlencoded length      formLimit  limit of the urlencoded body  If the body ends up being larger than this limit  a 413 error code is returned  Default is 56kb    set formLimit to bigger can solve this problem

User · Answer

I had a similar problem recently and found out  that client max body size  0  can solve such an issue  This will set client max body size to no limit  But the best practice is to improve your code  so there is no need to increase this limit

User · Answer

Please see if you are setting client max body size directive inside http    block and not inside location    block  I have set it inside http   block and it works

User · Answer

Following nginx documentation  you can set client max body size 20m   or any value you need   in the following context   context  http  server  location

User · Answer

Assuming you have already set the client max body size and various PHP settings  upload max filesize   post max size   etc  in the other answers  then restarted or reloaded NGINX and PHP without any result  run this     nginx -T  This will give you any unresolved errors in your NGINX configs   In my case  I struggled with the 413 error for a whole day before I realized there were some other unresolved SSL errors in the NGINX config  wrong pathing for certs  that needed to be corrected   Once I fixed the unresolved issues I got from  nginx -T   reloaded NGINX  and EUREKA   That fixed it

User · Answer

I m setting up a dev server to play with that mirrors our outdated live one  I used The Perfect Server - Ubuntu 14 04  nginx  BIND  MySQL  PHP  Postfix  Dovecot and ISPConfig 3   After experiencing the same issue  I came across this post and nothing was working  I changed the value in every recommended file  nginx conf  ispconfig vhost   sites-available default  etc    Finally  changing client max body size in my  etc nginx sites-available apps vhost and restarting nginx is what did the trick  Hopefully it helps someone else

User · Answer

If you tried the above options and no success  also you re using IIS  iisnode  to host your node app  putting this code on web config resolved the problem for me  Here is the reference  https   www inflectra com support knowledgebase kb306 aspx Also  you can chagne the length allowed because now I think its 2GB  Modify it by your needs     lt security gt       lt requestFiltering gt         lt requestLimits maxAllowedContentLength  quot 2147483648 quot    gt       lt  requestFiltering gt     lt  security gt

User · Answer

Someone correct me if this is bad  but I like to lock everything down as much as possible  and if you ve only got one target for uploads  as it usually the case   then just target your changes to that one file  This works for me on the Ubuntu nginx-extras mainline 1 7  package   location    upload php       client max body size 102M      fastcgi param PHP VALUE  upload max filesize 102M  n post max size 102M

User · Answer

NGINX large uploads are successfully working on hosted WordPress sites  finally  as per suggestions from nembleton  amp  rjha94   I thought it might be helpful for someone  if I added a little clarification to their suggestions   For starters  please be certain you have included your increased upload directive in ALL THREE separate definition blocks  server  location  amp  http    Each should have a separate line entry   The result will like something like this  where the     reflects other lines in the definition block     http               client max body size 200M           in my ISPconfig 3 setup  this block is in the  etc nginx nginx conf file   server               client max body size 200M     location                 client max body size 200M        in my ISPconfig 3 setup  these blocks are in the  etc nginx conf d default conf file   Also  make certain that your server s php ini file is consistent with these NGINX settings   In my case  I changed the setting in php ini s File Uploads section to read    upload max filesize   200M   Note  if you are managing an ISPconfig 3 setup  my setup is on CentOS 6 3  as per The Perfect Server   you will need to manage these entries in several separate files   If your configuration is similar to one in the step-by-step setup  the NGINX conf files you need to modify are located here     etc nginx nginx conf  etc nginx conf d default conf    My php ini file was located here    etc php ini   I continued to overlook the http    block in the nginx conf file   Apparently  overlooking this had the effect of limiting uploading to the 1M default limit   After making the associated changes  you will also want to be sure to restart your NGINX and PHP FastCGI Process Manager  PHP-FPM  services   On the above configuration  I use the following commands    etc init d nginx restart  etc init d php-fpm restart

User · Answer

As of March 2016  I ran into this issue trying to POST json over https  from python requests  not that it matters    The trick is to put  client max body size 200M   in at least two places  http    and server      1  the http directory   Typically in  etc nginx nginx conf   2  the server directory in your vhost    For Debian Ubuntu users who installed via apt-get  and other distro package managers which install nginx with vhosts by default   thats  etc nginx sites-available mysite com  for those who do not have vhosts  it s probably your nginx conf or in the same directory as it    3  the location   directory in the same place as 2     You can be more specific than    but if its not working at all  i d recommend applying this to   and then once its working be more specific    Remember - if you have SSL  that will require you to set the above for the SSL server and location too  wherever that may be  ideally the same as 2    I found that if your client tries to upload on http  and you expect them to get 301 d to https  nginx will actually drop the connection before the redirect due to the file being too large for the http server  so it has to be in both   Recent comments suggest that there is an issue with this on SSL with newer nginx versions  but i m on 1 4 6 and everything is good

User · Answer

If you are using windows version nginx  you can try to kill all nginx process and restart it to see  I encountered same issue In my environment   but resolved it with this solution

User · Answer

You need to apply following changes    Update php ini  Find right ini file from phpinfo     and increase post max size and upload max filesize to size you want   sed -i  s post max size     post max size   200M g   etc php5 fpm php ini sed -i  s upload max filesize     upload max filesize   200M g   etc php5 fpm php ini     Update NginX settings for your website and add client max body size value in your location  http  or server context   location         client max body size 200m             Restart NginX and PHP-FPM    service nginx restart service php5-fpm restart    NOTE  Sometime  In my case almost every time  you need to kill php-fpm process if it didn t refresh by service command properly  To do that you can get list of processes  ps -elf   grep php-fpm  and kill one by one  kill -9 12345  or use following command to do it for you   ps -elf   grep php-fpm   grep -v grep   awk    print  4      xargs kill -9

User · Answer

Had the same issue that the client max body size directive was ignored   My silly error was  that I put a file inside  etc nginx conf d which did not end with  conf  Nginx will not load these by default

[nginx] nginx - client_max_body_size has no effect

Examples related to nginx