Restart NGINX with the command:Īt this point, if anyone attempts to upload a file size larger than 100 MB, they’ll receive a 413 error (Request Entity Too Large). Run the NGINX configuration test with the command: Of course, your uploads directive will probably be a bit more complex than the basic one I’ve illustrated, but you get the point. In that same file, locate the location section you’ve configured for site uploads and add the same line ( Figure C).įigure C Adding the configuration line in the locations directive. In that file, look for the server section and add the same line as you did in the nf file ( Figure B).įigure B Adding the configuration line in the server section of your site config file. Sudo nano /etc/nginx/sites-available/default If you’re using the default, you would open that file with the command: Next, open the config file for your website. Look for the http section and add the following line ( Figure A):įigure A Adding the configuration to NGINX config file. The first thing we’re going to do is change the upload limit to 100MB in the nf file.
CANON IMAGE GATEWAY FILE SIZE LIMIT HOW TO
SEE: How to become a network administrator: A cheat sheet (TechRepublic) How to configure nf With those at the ready, let’s configure. I’ll be demonstrating on Ubuntu Server 18.04, but this process should work on any platform that supports NGINX. You’ll also need a user with sudo privileges. In order to make this work, you’ll need NGINX installed and configured to run your website. You certainly don’t want that.īut what can you do when you need to allow users to upload more than a single MB to your NGINX site? You control it with the client_max_body_size directive. However, if you open the floodgates too wide, you run the risk of ne’er-do-wells hitting you with Denial-of-Service (DoS) attacks. For some platforms, that might be considerably too low, especially for sites that allow users to upload items like images and video.
Out of the box, NGINX sets a limit of 1MB for file uploads.
0 kommentar(er)
