CODEWITHSUNDEEP
nginx
q_no
q_no

Reputation: 2829

nginx - client_max_body_size has no effect

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).

Upvotes: 282

Views: 499582

Answers (17)

YAGOUBI A.E.K
YAGOUBI A.E.K

Reputation: 121

Don't forget to reload nginx :

For RHEL/CentOS/Debian/Ubuntu Linux, try:
service nginx reload

Upvotes: 1

AdamPal
AdamPal

Reputation: 111

Warning for Cloudflare

Posting this as a warning for other Cloudflare users because I went through the Nginx docs and all the other answers here thoroughly before I finally figured out the issue.

Cloudflare free and Pro plans limit you to 100MB file upload size (reference).

So if the file size is over 100MB Cloudflare will return a 413 response and the request won't ever hit your server.

The solutions suggested are to either use a subdomain that is not proxied through Cloudflare for your upload endpoint or break the file up into chunks that are smaller than 100MB.

Hope this saves someone else some time!

Upvotes: 5

birgersp
birgersp

Reputation: 4966

The following config worked for me. Notice I only set client_max_body_size 50M; once, contrary to what others are saying...

File: /etc/nginx/conf.d/sites.conf

server {
    listen 80 default_server;
    server_name portal.myserver.com;
    return 301 https://$host$request_uri;
}

server {
    resolver 127.0.0.11 valid=30s;
    listen 443 ssl default_server;
    listen [::]:443 ssl default_server;
    ssl_certificate /secret/portal.myserver.com.crt;
    ssl_certificate_key /secret/portal.myserver.com.pem;
    access_log /var/log/nginx/access.log;
    error_log /var/log/nginx/error.log;
    server_name portal.myserver.com;
    client_max_body_size 50M;
    location /fileserver/ {
        set $upstream http://fileserver:6976;
        proxy_pass $upstream;
    }
}

Upvotes: 1

Esteban Gatjens
Esteban Gatjens

Reputation: 5101

In case you are using Kubernetes, add the following annotations to your Ingress:

annotations:
  nginx.ingress.kubernetes.io/client-max-body-size: "5m"
  nginx.ingress.kubernetes.io/client-body-buffer-size: "8k"
  nginx.ingress.kubernetes.io/proxy-body-size: "5m"
  nginx.ingress.kubernetes.io/proxy-buffer-size: "8k"

Confirm the changes were applied:

kubectl -n <namespace> describe ingress <ingress-name>

References:

Upvotes: 7

developer_009
developer_009

Reputation: 367

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.

  <security>
    <requestFiltering>
      <requestLimits maxAllowedContentLength="2147483648" />
    </requestFiltering>
  </security>

Upvotes: 0

Adri&#225;n Molčan
Adri&#225;n Molčan

Reputation: 139

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.

Upvotes: 7

pangpang
pangpang

Reputation: 8831

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.

Upvotes: 6

Jeramiah Harland
Jeramiah Harland

Reputation: 864

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.

Upvotes: 3

P-Didz
P-Didz

Reputation: 61

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.

Upvotes: 5

J.J
J.J

Reputation: 3607

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 :)

Upvotes: 82

nathan.xu
nathan.xu

Reputation: 211

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.

Upvotes: 0

Qorbani
Qorbani

Reputation: 5905

You need to apply following changes:

  1. 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```

  2. 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;
    ...
}

  3. 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

Upvotes: 34

digitaltoast
digitaltoast

Reputation: 689

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";
    (...)
}

Upvotes: 14

nembleton
nembleton

Reputation: 2502

Following nginx documentation, you can set client_max_body_size 20m ( or any value you need ) in the following context:

context: http, server, location

Upvotes: 167

jadik
jadik

Reputation: 1946

NGINX large uploads are successfully working on hosted WordPress sites, finally (as per suggestions from nembleton & 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 & 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

Upvotes: 153

Philippe Gerber
Philippe Gerber

Reputation: 17896

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.

Upvotes: 1

rjha94
rjha94

Reputation: 4318

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

Upvotes: 17

Related Questions