How to fix 413 Request Entity too Large with WordPress and Nginx

This brief tutorial shows students and new users steps to resolve a common error with WordPress when trying to upload files, media and other data and get shown an error the says “413 Request Entity Too Large” via Nginx.

This error, 413 request entity too large occurs when you try to upload or make a client request that is too large to be processed by the web server, in the case a Nginx HTTP server.

If the server setting has a request size limit that is too small, your users / clients may come across this error a lot. So you will probably want to adjust the web server settings to allow larger requests.

One of the common issues webmasters encounter when managing WordPress is allow the server to allow file upload via WordPress media library.

WordPress allows users to upload new themes and plugins files, however, if your Nginx powered website isn’t configured to allow large file to be uploaded, the upload process will fail always.

Some common errors user get when dealing with file uploads with WordPress are:

  • Http error attempting to upload media
  • the uploaded file exceeds the upload_max_filesize directive in php.ini
  • maximum execution time exceeded
  • allowed memory size exhausted and many more.

Before continuing with the steps below, please make sure to backup your system.

Configure WordPress directory permissions

First, make sure the directory WordPress is running in has the correct permission for Nginx webserver to operate. On Ubuntu systems, the root directory is almost always at /var/www/html.

So, run the commands below give Nginx web server full access to that directory.

sudo chown -R www-data:www-data /var/www/html/
sudo chmod -R 755 /var/www/html/

Adjust PHP-FPM settings

Next, adjust PHP-FPM settings to allow larger file uploads. By default, PHP-FPM is only allowed to uploaded a certain file size, so there’s a limit. Adjust the file upload size limit and other directives in PHP-FPM.

On Ubuntu 18.04 and up, the default PHP-FPM configuration file are stored in the the file below:


The x in the line above can either be a 0 or 1, 2, 3 or 4

So, open PHP-FPM configuration file by running the commands below and adjust the settings to suit your environment.

sudo nano /etc/php/7.2/fpm/php.ini

Then scroll down the file line by line and adjust each directive with the value below:

memory_limit = 256M
post_max_size = 32M
upload_max_filesize = 100M
file_uploads = On
max_execution_time = 600
max_input_time = 600

Save your changes.

If the file size you’re uploading is greater than 100MB, then adjust the upload_max_filesize to be greater than the file size.

Adjust Nginx configurations

Nginx also has its own limit definitions.

If you don’t define the size limit in Nginx configuration, whatever you do in the PHP configuration file may not apply to Nginx. To allow Nginx to also upload larger file, open Nginx configuration and add the values as defined below:

On Ubuntu systems, Nginx default site configuration files are stored at /etc/nginx/sites-available/default

If you have a custom file in there, adjust the highlighted values also.

server {
    listen 80;
    listen [::]:80;
    root /var/www/html/wordpress;
    index index.php index.html index.htm;

    client_max_body_size 100M;

location / {
    try_files $uri $uri/ /index.php?$query_string;

location ~ \.php$ {
      include snippets/fastcgi-php.conf;
      fastcgi_pass unix:/var/run/php/php7.1-fpm.sock;
      fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
      include fastcgi_params;
      fastcgi_connect_timeout 300s;
      fastcgi_read_timeout 300s;
      fastcgi_send_timeout 300s;

Save the file and continue

Finally, restart Nginx and PHP-FPM for the new settings to take effect

sudo systemctl reload nginx.service
sudo systemctl reload php7.2-fpm.service

Now go and try to upload the file you want with the size smaller than 100MB

This should do it.


  1. good tutorial and this is working great.
    please update command for reload nginx, use service not serive.
    btw sorry for my bad english.

Leave a Comment

Your email address will not be published.