Http код ошибки 413

Ошибка HTTP 413 Request Entity Too Large появляется, когда пользователь пытается загрузить на сервер слишком большой файл. Размер определяется относительно лимита, который установлен в конфигурации. Изменить его может только администратор сервера. 

Что делать, если вы пользователь

Если вы видите ошибку 413, когда пытаетесь загрузить файл на чужом сайте, то вам нужно уменьшить размер передаваемых данных. Вот несколько ситуаций.

• Если вы пытались загрузить одновременно несколько файлов (форма позволяет так делать), попробуйте загружать их по одному.
• Если не загружается изображение, уменьшите его размер перед загрузкой на сервер. Можно сделать это с помощью онлайн-сервисов — например, Tiny PNG.
• Если не загружается видео, попробуйте сохранить его в другом формате и уменьшить размер. Можно сделать это с помощью онлайн-сервисов — я использую Video Converter.
• Если не загружается PDF-документ, уменьшите его размер. Можно сделать это с помощью онлайн-сервисов — я обычно использую PDF.io.

Универсальный вариант — архивация файла со сжатием. Ошибка сервера 413 появляется только в том случае, если вы пытаетесь одновременно загрузить слишком большой объем данных. Поэтому и выход во всех ситуациях один — уменьшить размер файлов.

Исправление ошибки сервера 413 владельцем сайта

Если вы владелец сайта, который при загрузке файлов выдает ошибку 413, то необходимо изменить конфигурацию сервера. Порядок действий зависит от используемых технологий.

Чтобы понять, что стало причиной ошибки, нужно посмотреть логи. Это поможет сэкономить время. Вот подробная инструкция, которая рассказывает, как посмотреть логи в панели управления Timeweb. В зависимости от того, какая информация будет в логах, вы поймете, как исправлять ошибку 413.

Увеличение разрешенного размера для загрузки файлов на Nginx и Apache

На Nginx максимально допустимый размер файла задан в параметре client_max_body_size. По умолчанию он равен 1 МБ. Если запрос превышает установленное значение, пользователь видит ошибку 413 Request Entity Too Large. 

Параметр client_max_body_size находится в файле nginx.conf. Для его изменения нужен текстовый редактор — например, vi.

Подключитесь к серверу через SSH и выполните в консоли следующую команду:

Во встроенном редакторе vi откроется файл nginx.conf. В разделе http добавьте или измените следующую строку:

client_max_body_size 20M;

Сохраните и закройте файл. Затем проверьте конфигурацию файла:

Перезагрузите сервер следующей командой:

После перезагрузки будет действовать новая конфигурация с увеличенным лимитом на размер загружаемого файла.

На Apache опция, устанавливающая максимально допустимый размер загружаемого файла, называется LimitRequestBody. По умолчанию лимит не установлен (равен 0). 

На CentOS главный конфиг располагается по адресу /etc/httpd/conf/httpd.conf. На Debian/Ubuntu — по адресу /etc/apache2/apache2.conf. 

Значение задается в байтах:

LimitRequestBody 33554432

Эта запись выставляет максимально допустимый размер 32 МБ.

Изменить конфиги можно также через панель управления. Я пользуюсь ISPmanager, поэтому покажу на ее примере.

1. Раскройте раздел «Домены» и перейдите на вкладку «WWW-домены».
2. Выберите домен, на котором появляется ошибка, и нажмите на кнопку «Конфиг».

Появится вкладка с конфигами Apache и Nginx. Вы можете редактировать их вручную, устанавливая лимит на размер загружаемого файла.

Исправление ошибки на WordPress

На WordPress ошибку можно исправить двумя способами.

Способ первый — изменение разрешенного размера в файле functions.php. Этот файл отвечает за добавление функций и возможностей — например, меню навигации.

1. Откройте файловый менеджер.
2. Перейдите в папку public.html.
3. Откройте директорию wp-content/themes.
4. Выберите тему, которая используется на сайте с WordPress.
5. Скачайте файл functions.php и откройте его через любой текстовый редактор.

В панели управления на Timeweb можно также воспользоваться встроенным редактором или IDE — путь будет такой же, как указан выше: public.html/wp-content/themes/ваша тема/functions.php. 

В конце файла functions.php добавьте следующий код: 

@ini_set( 'upload_max_size' , '256M' );

@ini_set( 'post_max_size', '256M');

@ini_set( 'max_execution_time', '300' );

Сохраните изменения и загрузите модифицированный файл обратно на сервер. Проверьте, появляется ли ошибка 413. 

Второй способ — изменение файла .htaccess. Это элемент конфигурации, который способен переопределять конфигурацию сервера в плане авторизации, кэширования и даже оптимизации. Найти его можно через файловый менеджер в папке public.html.

Скачайте файл на компьютер, на всякий случай сделайте резервную копию. Затем откройте .htaccess в текстовом редакторе и после строчки #END WORDPRESS вставьте следующий код:

php_value upload_max_filesize 999M

php_value post_max_size 999M

php_value max_execution_time 1600

php_value max_input_time 1600

Сохраните файл и загрузите его обратно на сервер с заменой исходного файла. То же самое можно сделать через встроенный редактор или IDE в панели управления Timeweb.

Исправление ошибки при использовании PHP-скрипта

Если файлы загружаются с помощью PHP-скрипта, то для исправления ошибки 413 нужно отредактировать файл php.ini. В нем нас интересуют три директивы.:

• upload_max_filesize — в ней указан максимально допустимый размер загружаемого файла (значение в мегабайтах);
• post_max_size — максимально допустимый размер данных, отправляемых методом POST (значение в мегабайтах);
• max_execution_time — максимально допустимое время выполнения скрипта (значение в секундах).

Например, если я хочу, чтобы пользователи могли загружать файлы размером до 20 МБ, то я делаю так:

max_execution_time = 90

post_max_size = 20M

upload_max_filesize = 20M

Если все значения указаны верно, то файлы с допустимым размером будут загружаться на сервер без ошибок.

То же самое можно сделать через панель управления. Например, в ISPmanager порядок будет такой:

1. Авторизуйтесь с root-правами.
2. В левом меню раскройте раздел «Настройки web-сервера» и перейдите на вкладку «PHP».
3. Выберите используемую версию и нажмите на кнопку «Изменить».

На экране появится список параметров. Они отсортированы по алфавиту. Установите необходимые значения для параметров max_execution_time, post_max_size и upload_max_filesize. Изменения применяются автоматически.

When building and maintaining a website, you’re bound to encounter some unexpected HTTP errors here and there. Problems like these are tough to avoid, and some are trickier to resolve than others.

If you’re experiencing a «413 Request Entity Too Large» error, the good news is that this issue is quick and simple to address — you just need to do a bit of server reconfiguration. And no, you don’t need to be a technical expert. Let’s learn how.

Web servers place size limits on uploads to prevent users from overwhelming the server and exceeding storage permissions. This limit usually isn’t an issue, and common website files should stay well under it. However, especially large file uploads may occasionally exceed the limit, resulting in a message like this:

While you can reduce the size of your upload to get around the error, it’s also possible to change your file size limit with some server-side modification.

Why does the «413 request entity too large» error happen?

The «413 Request Entity Too Large» error occurs when the size of a client’s request exceeds the server’s file size limit. This error typically happens if you attempt to upload an overly large file. The server responds with a 413 error message to indicate that the entity being sent is too large.

Here are a few examples:

• Uploading large media files, such as images, videos, or audio files
• Submitting form data with large file attachments
• Making API requests with large payloads
• Using content management systems like WordPress with default size limits

The «413 Request Entity Too Large» error is also known by different names, such as:

• Status Code 413
• Error 413
• HTTP Error Code: 413
• 413 Request Entity Too Large
• 413 Payload Too Large
• Entity Too Large 413
• 413 Request Entity Too Big
• HTTP Error 413

Keep in mind that you can only fix this error if you own the website where the error happened. If it happened on an external website or app you’re using, you should try to reduce your file size or reach out to their owner or customer support team. 

How to Fix a “413 Request Entity Too Large” Error

Let’s go over some ways you can resolve HTTP error 413. First, we’ll go over some device-agnostic, server-agnostic, and hosting-agnostic methods. We’ll then walk you through how to fix a 413 error on your WordPress website and on Nginx and Apache servers specifically.

1. Reset File permissions

In some cases, the «413 Request Entity Too Large» error can be caused by incorrect file permissions on your server, so resetting these permissions could help. Here’s how to do it (some technical expertise recommended):

• Access your server files: Depending on your hosting provider, you can access your server files in different ways. Common methods include using an FTP client or accessing the file manager through your hosting control panel (such as cPanel).
• Locate the root directory: Navigate to the root directory of your website where the server files are stored. This is typically named public_html or www.
• Select the files and folders: Select all the files and folders within the root directory.
• Change permissions: Right-click on the selected files and folders and choose the «Permissions» or «Properties» option. This may open a dialog box where you can modify the permissions, depending on your specific server.
• Set permissions: Set the permissions to the appropriate values. You can either manually enter these values (like 644 or 755) or use checkboxes or dropdown menus depending on your file manager.

After resetting the file permissions, try uploading the file again. If the permissions were the cause of the issue, the error should no longer occur.

Word of warning: Be careful when modifying file permissions, as setting incorrect permissions can potentially compromise the security and functionality of your website. This is especially critical if you’re running a WordPress website, because WordPress is known to have some security vulnerabilities.

2. Manually Upload the File through FTP

Uploading the file via FTP (File Transfer Protocol) can be a good approach, but I recommend it as a last resort if you’re running a WordPress website, or if you have access to your Apache and Nginx servers. I offer several solutions below for those use cases.

But if those don’t apply to you, or you’ve already tried various methods, FTP is worth trying. It’ll allow you to circumvent restrictions imposed by web interfaces or form submissions. Plus, it will allow you to transfer the file to the server and manually control the upload. That said, this method won’t work if uploads are subject to server-imposed limits.

Otherwise, let’s try it. Here’s how:

• Obtain your FTP credentials: This will probably be the hardest part, but it’s also the most important. First, you need your server address, username, password, and port number, which will allow you to transfer files later.
• Install an FTP client: Then, choose an FTP client that best suits your needs. Popular options include FileZilla, Cyberduck, or WinSCP.
• Launch the FTP client: Open your FTP client and enter the FTP server address, username, password, and port number you obtained earlier.
• Connect to the FTP server: Click on the «Connect» or «Quick Connect» button to connect to the FTP server. The FTP client will connect to your website’s server if you’ve provided the correct credentials.
• Navigate to the target directory: Once connected, the FTP client will display the directories and files on your server. Navigate to the folder where you want to upload the file. This could be the root directory or a specific folder.
• Upload the file: Drag and drop the file from your computer into the FTP client’s remote server directory. The file transfer will begin.

I also recommend setting file permissions, if it’s not done automatically. Right-click on the uploaded file in the FTP client and select «Properties» or «Permissions.» Make sure the file permissions are correct to allow access only to the right users.

If you’re running on an Unix-like system, permissions are typically number 644 for files. «644» is a common default permission that allows you, the owner, to read and modify the file, while group members and other users can read it. (Here’s what the numbers mean, if you’re curious.)

Once the file is uploaded via FTP, access your website and see if the uploaded file works as intended without triggering the «413 Request Entity Too Large» error.

3. Contact Your Hosting Provider

If you’ve tried several methods or you’d prefer to not mess with server files or FTPs, reach out to your hosting provider. They have control over the server settings that may be causing the error. They also have the technical expertise to make changes without harming your website, a huge plus.

If you’ve exceeded the file size limit imposed by your hosting plan without realizing it, they can confirm the limits or increase the size limit if necessary (by upgrading your plan, for instance).

Your hosting provider may also be using a content delivery network (CDN) to enhance your website’s performance. The problem is that CDN servers may have their own file size limits, which could trigger a 413 error. Your website host could help you navigate these limitations or even adjust the CDN settings for you.

Next, we’ll show you how to fix a 413 error by increasing your size limit with a WordPress setup, as well as with an Apache or Nginx server configuration.

All methods require some edits to your server files, so we recommend creating a backup before attempting the steps below.

How to Fix Error 413 in WordPress

Themes and plugins are common causes of the 413 error with the WordPress content management system. Fortunately, there are several ways to increase your WordPress upload size limit enough to let these larger files through. As long as you do not exceed the limits of your hosting plan, you can try any of the following:

Method 1: Modify PHP.ini

The easiest method to increase your upload limit is by modifying your server’s PHP.ini file. Here, you can change your limit through the cPanel interface without any coding. To do this:

1. In your cPanel menu, select MultiPHP INI Editor under Software.

2. In the window that appears, choose your domain from the dropdown menu.

3. Change the values of the following parameters to your preference:

• max_execution_time (maximum time to upload, in seconds)
• upload_max_filesize (maximum upload size, in megabytes)
• post_max_size (maximum post size, in megabytes)

4. When finished, click Apply.

Method 2: Modify .htaccess

If your WordPress site is hosted on an Apache server, it’s also possible to increase your server’s limit via .htaccess, a file that contains many directives for the server. See the solution below.

Method 3: Modify functions.php

You can also try increasing your size limit via the functions.php file of your current WordPress theme.

If you want to make this change permanent, we recommend trying the above approaches first. With this approach, you’ll need to update functions.php whenever you update or change your current theme.

1. In your cPanel menu, select File Manager under Files.

2. Navigate to the folder of your current theme inside your root WordPress directory (public_html by default). Open this theme file.

3. Select functions.php and click the Edit icon.

4. Copy the code below and paste it at the end of the file

 
@ini_set( ‘upload_max_size’ , ’64M’ );
@ini_set( ‘post_max_size’, ’64M’);
@ini_set( ‘max_execution_time’, ‘300’ );

5. Click Save.

This code sets the maximum allowed size of your WordPress uploads and posts to 64 megabytes. You can change this number to something larger or smaller if you need, as long as you do not exceed your hosting plan’s storage limit.

It also sets the maximum period your uploads can take to 300 seconds. Feel free to change this as well.

How to Fix 413 Request Entity Too Large in Nginx

Nginx server settings can be modified inside the file nginx.conf. Open this file and check for the directive client_max_body_size. Then, change the value (in megabytes) to your maximum file size preference.

If you do not see this directive in nginx.conf, you can add it to the end of a server, location, or http block like so:

 
server {
...
client_max_body_size 64M;
}

This allows for a 64-megabyte upload. Set this number to your preference, save the file, then reload Nginx for the change to take effect.

How to Fix Error 413 in Apache

Change the size limit on an Apache server by updating your .htaccess file like so:

1. In your cPanel menu, select File Manager under Files.

2. In your root WordPress directory (public_html by default), locate .htaccess. Depending on your settings, the .htaccess file may be hidden.

3. Select .htaccess and click the Edit icon.

4. Copy and paste the code below at the bottom of your .htaccess file:

 
php_value upload_max_filesize 64M
php_value post_max_size 64M
php_value max_execution_time 300
php_value max_input_time 300

5. Click Save and reload Apache.

Doing this sets the maximum allowed size of your WordPress uploads and posts to 64 megabytes and sets the maximum file upload time to 300 seconds. You can change both of these values to your preference.

Still getting a 413?

After trying one or more of the solutions above, you still may encounter a 413 error when uploading large files, even if these files are below your new size limit.

In this case, the issue may stem from your CDN’s servers or some other restriction set by your hosting provider. As mentioned, reach out to your hosting support, detailing the problem and the steps you’ve taken so far to resolve it. It may be that you’ve exceeded your plan’s file size limit without realizing. Or, your configurations may have inadvertently caused another error.

If you use a CDN to improve your site’s performance, this may also be the cause of your issue — the CDN servers you’re using may impose file size limits that are too small. Since you probably can’t modify these servers’ files directly, you should consult the documentation for your CDN provider or contact product support to resolve the error.

If all else fails, consider uploading alternative files, reducing the size of your current file, or upgrading your storage plan. If you find yourself needing to upload a massive amount of data, more likely than not there’s a workaround.

Fixing a 413 Error

While HTTP errors can be frustrating, many are quickly solvable including a 413. By finding and tackling this issue now, you’ll have one less thing to worry about while building out your website. If your site allows users to upload their own content, changing your upload size limit solves this problem too — just make sure you’re not exceeding the limits set by your hosting plan.

As for the best option, we recommend WordPress users modify their server’s PHP.ini file first if possible, since this can easily be done through your hosting panel. Otherwise, choose the option that matches your server software.

This post was originally published in January 2021 and has been updated for comprehensiveness.

This article was written by a human, but our team uses AI in our editorial process. Check out our full disclosure to learn more about how we use AI.

Приходилось ли вам сталкиваться с сообщением об ошибке 413 request entity too large при работе в интернете? Эта ошибка довольно распространена и может быть вызвана несколькими различными причинами. В этой статье мы рассмотрим её значение, способы устранения проблем и случаи, когда она может возникнуть.

Что означает ошибка 413 Request Entity Too Large

Ошибка 413 — это код состояния http, который указывает на то, что у сервера не получилось обработать запрос, поскольку объект запроса (данные, отправленные клиентом) слишком велик. Другими словами, когда вы пытаетесь получить доступ к веб-сайту или веб-странице, ваш браузер отправляет запрос с изображениями или видео, размер которых превышает возможности сервера.

Наиболее распространенной причиной её возникновения является то, что на сервере установлено ограничение на величину загружаемых файлов. Оно нужно для того, чтобы предотвратить одновременную отправку слишком большого количества данных любым пользователем, а также в целях безопасности. Этот лимит можно регулировать в зависимости от ваших конкретных потребностей, но если он слишком мал, то вы можете часто сталкиваться с этой ошибкой.

Исправление ошибки сервера 413: для владельцев сайта

Для начала стоит изучить логи сервера – файлы, в которых записываются происходящие на нём события. Они содержат сведения о запросах к серверу и его ответы.  

Логи также могут содержать информацию об ошибках и других проблемах, возникших на веб-сервере во время его работы. Они предоставляют бесценную информацию о работе вашего сайта и полезны для выявления проблем или потенциальных угроз безопасности. Анализируя их, вы можете улучшить производительность или усилить безопасность.

Когда определите причину неисправности, можете выбрать соответствующий способ решения проблемы.

Увеличение лимита размера для загрузки файлов на Apache, Nginx

Одним из наиболее распространенных ограничений на хостинге является лимит на величину загружаемых файлов. Если сайт требует от пользователей загрузки больших файлов, то может понадобиться оптимизировать параметры на серверах apache и nginx.

Процесс включает в себя внесение изменений в конфигурационных файлах, поэтому действовать будем в текстовом редакторе.

Выполняем подключение по SSH, пишем команду, чтобы открыть нужный файл.

vi /etc/nginx/nginx.conf

Находим раздел http и меняем строку

client_max_body_size 20M;

Если этой строки нет, её нужно вписать.

Сохраняем изменения и закрываем файл, после чего выполняем проверку.

$ sudo nginx -t

Затем отправляем сервер на перезагрузку, после чего изменения вступят в силу

# nginx -s reload

На Apache лимит обычно отсутствует вообще, то есть равен 0. Нам нужна опция, определяющая максимальную величину для файлов, которые загружают администраторы или пользователи, она называется «LimitRequestBody». Ищем его в главном конфигурационном файле.

Теперь выражаем значение в байтах. В данном случае мы указали лимит в 32 МБ.

LimitRequestBody 33554432

Также изменения можно провести в панели управления. Рассмотрим, как исправить ошибку 413 в ISPmanager.

В вертикальном меню слева ищем раздел «Домены», в нём кликаем на вкладку «WWW-домены».

Кликаем на домен, который выдаёт ошибку, нажимаем кнопку «Конфиг».

Откроются поля с конфигами Apache и Nginx, где мы можем устанавливать подходящие значения.

Исправление ошибки 413 на WordPress

Если вы используете WordPress, то существуют плагины, позволяющие увеличить максимальный размер загружаемых файлов, чтобы избежать этой проблемы в будущем. 

Предусмотрено два варианта действий.

1. В functions.php

• Заходим в файловый менеджер и открываем папку public.html. 
• Открываем директорию wp-content/themes.
• Выбираем тему, применяемую на рассматриваемой странице.
• Скачиваем файл functions.php, открываем его в текстовом редакторе. 
• Добавляем в конце его следующие значения.

@ini_set( ‘upload_max_size’ , ‘256M’ );

@ini_set( ‘post_max_size’, ‘256M’);

@ini_set( ‘max_execution_time’, ‘300’ );

Сохраняем изменения, выходим и выполняем проверку.

1. Редактирование .htaccess.

Этот файл расположен в той же папке, скачиваем его на ПК. 

Открываем в редакторе и находим строку #END WORDPRESS. После неё добавляем строки.

php_value upload_max_filesize 999M

php_value post_max_size 999M

php_value max_execution_time 1600

php_value max_input_time 1600

Сохраняем изменения, файл загружаем обратно. 

Изменения также можно внести через панель управления или встроенный редактор.

Исправление ошибки 413 при использовании PHP-скрипта

Если на вашем сайте используются php-скрипты, то регулировка лимита также поможет уменьшить количество ошибок, связанных с загрузкой больших файлов.

Нам требуется внести изменения в файл php.ini.

Находим соответствующие директивы и меняем параметры, как в примере.

max_execution_time = 90

post_max_size = 20M

upload_max_filesize = 20M

Второй способ редактирования – через панель управления.

• Заходим и авторизовываемся как суперпользователь.
• В вертикальном меню кликаем на «Настройки web-сервера», а в правой части окна выбираем «PHP».
• Открываем нужную версию, нажимаем кнопку «Изменить». 

Вы увидите перечень параметров в алфавитном порядке для удобного поиска. Поставьте значения, аналогичные примеру выше. 

Исправление ошибки сервера 413: для пользователя

По сути, рекомендация для пользователей одна – необходимо сделать файлы для загрузки маленькими. А способы для разных форматов могут отличаться. 

1. Когда требуется загрузка сразу нескольких файлов, загружать их следует по очереди, даже если функционалом предусмотрена возможность массовой загрузки.
2. Сжимайте картинки перед загрузкой, это можно сделать практически в любом редакторе или онлайн-сервисе.
3. Измените формат видео и тоже попробуйте его сжать. 
4. Для загрузки документов актуальна архивация с сжатием. 

Использование сжатых форматов, таких как zip, также может помочь значительно уменьшить общий размер файлов, сохраняя при этом одинаковый уровень качества для всех типов данных, упомянутых выше, тем самым устраняя шансы столкнуться с ошибкой 413 в будущем.

WordPress errors come in all shapes and sizes. In most cases they’re easy to decipher; such is the accessibility of WordPress’ error reporting. Even so, when the “413 Request Entity Too Large” error pops up, it can leave you scratching your head.

Without realizing it, you already have everything you need to understand and diagnose the error within its name. The good news is you won’t need more than a standard Secure File Transfer Protocol (SFTP) client and administrator access to your server.

In this post, we’ll take a look at how to solve the “413 Request Entity Too Large” error. We’ll also give you a quick list of steps to take before you begin to solve the error, to make the process super straightforward.

Check out our video guide to fixing the “413 Request Entity Too Large” Error

What the “413 Request Entity Too Large” Error Is (And Why It Exists)

We noted that there’s a clue in the error name as to what the solution and problem are. Before you go sleuthing yourself, though, we’ll spoil the surprise: it’s in the adjective “large.”

In a nutshell, the “413 Request Entity Too Large” error is a size issue. It happens when a client makes a request that’s too large for the end server to process. Depending on the nature of the error, the server could close the connection altogether to prevent further requests being made.

Let’s break the error down into its parts:

• “413”: This is one of the 4xx error codes, which mean there’s a problem between the server and browser.
• “Request Entity”: The “entity” in this case is the information payload being requested by the client from the server.
• “Too Large”: This is straightforward: the entity is bigger than the server is willing or able to serve.

In fact, this error has changed its name from what it originally was to be more specific and offer more clarity. It’s now known as the “413 Payload Too Large” error, although in practice, you’ll see the older name a lot more.

As for why the error occurs, the simple explanation is that the server is set up to deny explicit uploads that are too large. Think of times when you upload a file where there’s a maximum file size limit:

In most cases, there will be some validation in place to stop the error… if you’re seeing the “413 Request Entity Too Large” error, those validation efforts may not be as watertight as you think.

What You’ll Need to Resolve the “413 Request Entity Too Large” Error

Fixing this error is all about raising the maximum file size for the server in question. Once that’s out of the way, you shouldn’t see the error anymore.

As such, to fix the “413 Request Entity Too Large” error, you’ll need the following:

• Administrator access to your server.
• A suitable SFTP client (we’ve covered many of these in the past).
• The know-how to use SFTP — there’s a good guide to the basics on WordPress.org, and you won’t need more than that.
• A text editor, though there’s no need for anything too complex.
• A clean and current backup in case the worst happens.

As an aside, we mention SFTP throughout this article as opposed to FTP. In short, the former is more secure than the latter (hence the name). That said, while there are other differences you should investigate, the functionality remains the same for the vast majority of uses.

Also, it’s worth noting that the MyKinsta dashboard has plenty of functionality on hand to help you get onto your server. For example, each site displays SFTP connection information that’s easy to understand:

This can help you get into your site without fuss. In some cases, you may be able to import the credentials straight to your chosen SFTP client.

3 “Pre-Steps” You Can Take Before Rectifying the “413 Request Entity Too Large” Error

Before you crack open your toolbox, there are some steps you can take to help resolve the “413 Request Entity Too Large” error. Here are two — and each one may give you a welcome workaround to the error.

1. Try to Upload a Large File to Your Server Through SFTP

Because the issue is related to the file sizes hitting your server, it’s a good idea to circumvent the frontend interface and upload a large file to the server yourself. The best way to do this is through SFTP.

This is because protocols such as SFTP are almost as “close to the bone” as you can get with regards to the way you access your server. Also, you can simultaneously rule out any issues with the frontend that may be causing the error.

To do this, log into your site through SFTP and find the wp-content folder. In here will be the uploads folder.

Next, upload your file to this folder on the server and see what the outcome is. If the upload is successful, we suggest sending an email to the site’s developer, as they may want to investigate the issue further on the frontend.

2. Check for Server Permissions Errors

Of course, permissions errors will stop any server request from running. As such, you should check whether the user has sufficient permissions to upload files of any size. Once this is sorted, the error should disappear.

The first step is to determine whether this is an issue with a single user (in which case they may be restricted for a reason). If the “413 Request Entity Too Large” error is happening for multiple users, you can be more sure of something that needs your input.

We’d suggest two “pre-fixes” here:

• Double-check your WordPress file permissions, just in case there’s an issue.
• Remove and re-create your SFTP user (a general investigation is a great idea).

While they may not solve the error in the first instance, you’ll at least know that your file and user structure is as it should be.

How to Solve the “413 Request Entity Too Large Error” for Your WordPress Website (3 Ways)

Once you’ve gone through the pre-steps, you’re ready to tackle the error head-on.

The following three methods are listed from easiest to toughest, with the understanding that that the path of least resistance is the best one to take.

1. Edit Your WordPress functions.php File

First off, you can work with your functions.php file to help bump up the file upload size for your site. To do this, first log into your site through SFTP using the credentials found within your hosting control panel.

When you’re in, you’ll want to look for the file itself. The functions.php file should be in the root of your server. In many cases, this root is called www or public_html, or it could be the abbreviated name of your site.

Once you’ve found it, you can open it in your text editor of choice. If you don’t see the file, you can create it using your text editor.

Once you have a file open, enter the following:

@ini_set( '_max_size' , '64M' );
@ini_set( 'post_max_size', '64M');
@ini_set( 'max_execution_time', '300' );

In short, this increases the maximum file size of posts and uploads while boosting the time the server will spend trying to process the request. The numbers here could be anything you wish, but they should be large enough to make the error disappear. In practice, 64 MB is enough for all but the most heavy-duty of tasks.

When you’re ready, save your file and upload it to the server again. Then, check whether the “413 Request Entity Too Large” error still exists. If it does, head onto the next method.

2. Modify Your WordPress .htaccess File

Much like your functions.php file, your .htaccess file sits on your server. The difference here is that .htaccess is a configuration file for Apache servers. If you’re a Kinsta customer, you’ll know we run Nginx servers, so you won’t see this file in your setup.

Still, for those with an Apache server, this is the approach you’ll need. Much like with the guidance for functions.php, first log into your server through SFTP, then look in your root folder as before.

The .htaccess file should be within this directory, but if it’s missing, we suggest you get in touch with your host to determine where it is, and whether your server runs on Nginx instead.

Once you’ve found it, open it up again. You’ll see some tags, and the most important here is # END WordPress. You’ll want to paste the following after this line:

php_value upload_max_filesize 64M
php_value post_max_size 64M
php_value max_execution_time 300
php_value max_input_time 300

In short, this does almost the same thing as the code you’d add to the functions.php file, but it’s akin to giving the server direct instructions.

When you’ve finished, save your changes, upload the file, and check your site again. If you’re still having trouble, we’d again suggest contacting your host, as they will need to verify some aspects of your setup that lie beyond the scope of this article.

3. Change Your Nginx Server Configuration

Our final method is specific to Nginx servers — those used at Kinsta. The purpose is the same as when working with the .htaccess file, in that you’re talking to the server, rather than going through WordPress.

We mentioned that for Apache servers you’ll use .htaccess. For Nginx servers, though, you’ll want to find the nginx.conf file. Rather than walk you through every step in the chain, we’ve gone over the full details in our post on changing the WordPress maximum upload size.

Remember that you’ll need to also alter the php.ini file based on the changes you make to nginx.conf. We’ve covered that in the aforementioned blog post too, so take a look there for the exact steps.

Summary

Despite WordPress being a rock-solid platform, you’ll see a lot of different WordPress errors over time. The “413 Request Entity Too Large” error is related to your server, though — not WordPress. As such, there’s a different approach to solving this error than other platform-specific issues.

If you have SFTP skills, there’s no reason you can’t fix this error quickly. It relates to the upload size specified in your server configuration files, so digging into your .htaccess or nginx.config files will be necessary. It’s a breeze to crack open your text editor and make the changes to these files, and if you’re a Kinsta customer, we’re on hand to support you through the process.

HTTP Error 413 indicates that the server cannot manage the request made, and this is because it involves a file or a block of data or, again, a group of files that are too large compared to the maximum limit that the server can manage.

The browser window generally displays the message “413 Request Entity Too Large”. This problem can occur if you try to upload too large files via the browser, exceeding the limits imposed by the webmaster for security reasons or others.

Why Does the “413 Request Entity Too Large” Error Occur?

Error 413 Request Entity Too Large occurs when you try to upload a file that exceeds the maximum upload limit set on your web server. In other words, when you try to upload a file that is too large, the web server returns an error message informing the user that “413 Request Entity Too Large”.

The message shown to the user may vary depending on the web server and the client. The following are the most common messages that indicate the occurrence of this error:

• Error 413
• HTTP Error 413
• HTTP Code: 413
• Request Entity Too Large
• 413. That’s an error.

Fixing the “413 Request Entity Too Large” Error in WordPress

As you know, error 413 usually occurs when you upload a large file to your web server and your hosting provider has set a limitation on file size.

One of the common problems webmasters encounter when managing WordPress is allowing the webserver to allow file uploads via the Media Library. However, if your Nginx-powered website is not configured to allow the uploading of large files, the upload process will mostly fail.

I will show you some of the easiest methods to increase the file upload size and fix the 413 Request Entity Too Large error in WordPress.

1. Reset File Permissions
2. Manually Upload the File via FTP
3. Increase Upload File Size
4. Modify Your Functions.php File
5. Modify Your .htaccess File
6. Modify Your nginx.conf File
7. Contact Your Hosting Provider

1. Reset File Permissions

It might be possible that you are encountering this error due to limited access to a file and upload permission. So, it would be great to check the WordPress file/folder permissions and set the recommended permission, then try uploading the file to your site.

You can set the permissions from an FTP Client like FileZilla, and if your hosting provider offers any file permission reset option, then you can fix it from there.

2. Manually Upload the File via FTP

It’s a good idea to consider FTP to upload your large file, but please note that if you are uploading a file via FileZilla, it takes more time.

Here, you will need to access your web server and upload the file by drag and drop. Therefore, first, you need to check whether your hosting provider offers server credentials or SFTP access to your web server.

Now, you need the FileZilla FTP Client to access your web files, so download it if you don’t have one. Then, open FileZilla and fill the respective fields; Host, Username, Password, and Port. You can see in the below screenshot that I pasted my server IP, Username, Password, and 22 as a port number.

Next, drag the file you want to upload to your website from your local desktop (left-side) and drop it into your web server’s folder. In my case, the webserver folder path is /applications/dbname/public_html/wp-content/uploads. If you want to upload any plugin then the folder path is /applications/dbname/public_html/wp-content/plugins.

3. Increase Upload File Size

Many good WordPress hosting providers offer the file size settings feature on their platform that lets users increase the maximum upload size value, maximum execution time, post max size, and more.

Now, let’s look at how you can increase your upload file size from the hosting dashboard. Cloudways offers application and server settings from which you can increase your file upload settings. From the Application Management panel, I have to remove comment “;” from three values and increase the upload and post max size to 256M & execution time to 300.

php_admin_value[post_max_size] = 256M

php_admin_value[upload_max_filesize] = 256M

php_admin_value[max_execution_time] = 300

To check whether the file size value is updated or not, you need to create an info.php file on your desktop and upload it to your website folder via FileZilla. Now, open any file editor like Notebook, paste the following code, and save it as info.php.

<?php

phpinfo();

?>

Now, upload it to your site’s public_html folder.

In the next step, open your browser and run this URL “www.yoursite.com/info.php”. In my case, the URL is https://wordpress-675386-2363839.cloudwaysapps.com/info.php. Search for the PHP admin values that you updated; if the values are changed, you have successfully increased the file size. After this, try to upload your file and check whether the issue has been resolved or not.

If your hosting provider doesn’t offer any feature to modify the file upload size, move to the next method.

4. Modify Your Functions.php File

You can edit your theme’s functions.php file and increase the file upload size. But before that, you will need to create a backup of your entire WordPress site for data recovery. Backups help you recover your web files if something goes wrong.

You need an FTP Client like FileZilla to access your site’s file. So, connect your server via FileZilla and go to your active theme folder. You will find the theme files in the wp-content folder and in my case, the source path is “/applications/enxybqgzgy/public_html/wp-content/themes/twentynineteen”. Next, find the functions.php and click View/Edit.

Next, paste the following lines of code into your file and save it. This will define the max upload size in Megabytes. Replace the numbers as per your requirement.

@ini_set( 'upload_max_size' , '256M' );

@ini_set( 'post_max_size', '256M');

@ini_set( 'max_execution_time', '300' );

After this, check open info.php on your browser “www.yoursite.com/info.php” and check whether the values are updated or not, then try uploading your file.

In case this doesn’t work, then move to the next method.

5. Modify Your .htaccess File

If your website is hosted on LAMP Stack (using Apache web server and PHP), you can increase the max upload size from your .htaccess file.

Again, you need to access your .htaccess file from an FTP client like FileZilla and go to the public_html folder. Search for the .htaccess file, and if you do not see the .htaccess file, it’s probably hidden. Hence, navigate to FileZilla menus > Server and click Force Showing Hidden Files.

Now View/Edit the .htaccess file in a code editor or Notepad and add the following lines.

php_value post_max_size 256M

php_value memory_limit 256M

php_value max_execution_time 300

Choose a number and size that is suitable for your site and file. Next, open info.php ““www.yoursite.com/infor.php”” on your browser to check the updated sizes as we did in the previous step.

6. Modify Your nginx.conf File

The above troubleshooting method is for Apache web server, but if you are running your website on LEMP (NGINX as a web server and PHP), you need to edit nginx.conf i.e., located in /etc/nginx/ and add the following line of code to the file.

http {

client_max_body_size 100M;

}

7. Contact Your Hosting Provider

If you tried all the above and are still facing the issues, then it would be good to contact your hosting support and ask them to fix this issue ASAP. Several hosting providers offer 24/7 support chat and ticket assistance to help their customers.

Summary

Error 413 Request Entity Too Large is related to the size of the client request. There are multiple ways to fix this error you have read in this article. The most common way is to reduce the file size or to change the web server settings to increase the upload file size. If you know any other methods that can help fix the HTTP 413 Error, then please comment in the section below.

Frequently Asked Questions