What is the 413 Request Entity Too Large Error, How to Fix It and Avoid It

Home » How-Tos » Learning and Resources » What is the 413 Request Entity Too Large Error, How to Fix It and Avoid It

The “413 Request Entity Too Large” error occurs when the size of your request exceeds the server’s file size limit. If you are experiencing a 413 error, the good news is that this issue can be resolved quickly with some server reconfigurations. And you do not need to be a technical expert. In this article, we will discuss “413 Request Entity Too Large” and how to fix this error.

What is a “413 Request Entity Too Large” Error?

A 413 error happens when the server cannot handle a user request because the file, data, or group of files being sent is too large to process. This error often occurs when you try to upload a file that is bigger than the limit set by the website owner. These limits are usually in place for security or other reasons.

Why Does a 413 Error Occur?

As mentioned before, the HTTPS 413 error shows up when you try to upload a file bigger than the maximum size allowed by the web server. In other words, you get this error when the server cannot handle the file, so it sends back an error message saying, “413 Request Entity Too Large.”

Depending on the web server and the browser you are using, the error message might look slightly different. Here are some common versions of the 413-error message:

Error 413
HTTP Error 413
HTTP Code: 413
Request Entity Too Large
413. That is an error

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

Here are some ways in which you can fix the HTTPS 413 error:

1. Re-access File Permissions

Incorrect file or folder permissions on your server can restrict your upload functionality, leading to the HTTPS 413 error. Re-accessing and resetting the file permissions can resolve the issue. If you are using a cPanel or any other control panel, you can reset the file permissions by:

Clicking on the ‘Website’ option in your cPanel. Then, navigate to the ‘Advanced’ option and choose the ‘Fix File Ownership’ option
Then, check the box to confirm the changes in file permissions

You can also use an FTP client or your hosting provider’s file manager to reset permissions.

Here is how you can reset file permissions using an FTP client or file manager:

Open your root directory (public_html) and right-click on ‘Permissions’
Then, use the 755 commands to update the folder’s access permissions and the 644 commands to reset the file access permissions. For the unversed, in file system permissions, command 644 means only the server owner has the right to read and write files, and command 755 denotes that the owner can read, write, and execute folders.

2. Increase Upload File Size

Most modern hosting providers allow you to adjust PHP settings, which are responsible for the file upload size, from the hosting account itself. You just need to log into your hosting account. Then, go to the ‘Websites’ options, and click on the ‘Advanced’ option, and locate PHP configuration. After locating the PHP configuration, you need to change the memory limit, post size, and upload size. This will enable you to upload files of any size.

3. Modify Application Settings

Sometimes, applications like WordPress may block larger file uploads because of its default settings. To fix this, you need to change the application’s configuration files. Here is how you can modify your application settings:

Step 1: Identify the File to Edit

Applications like WordPress have pre-set upload limits. So, you need to modify the pre-set upload limit. You can do that by identifying the file that restricts larger file uploads. For instance, in WordPress, locating the wp-config.php file enables you to make changes to your WordPress file directory.

Step 2: Find the Relevant Settings

After locating the file, look for parameters like upload size, memory limits, and post size that control file upload size.

Step 3: Update the Values

Increase the limits to allow larger files. For instance, in WordPress, you can use codes like @ini_set(“upload_max_size”, “530M”) to increase the upload limit.

Step 4: Save the Changes

Once you have updated the file, save it, and upload it back to your server.

Step 5: Test the Upload

Try uploading a large file to make sure the changes worked. If you are still facing issues, contact your hosting provider.

4. Update the .htaccess File (For Apache Servers)

If you are using the Apache server, updating the .htaccess file can help you solve this error. For the unversed, the .htaccess file is a configuration file used to manage server authorization, server optimization, and data caching, among others.

Follow these steps to resolve the 413 error via the .htaccess file:

Step 1: Navigate to your WordPress or any other application’s root directory. You can use a file manager or an FTP client to reach your root directory.
Step 2: Then, double-click on the ‘.htaccess’ file. This will allow you to edit the .htaccess file.
Step 3: After that, insert these codes—php_value post_max_size 496M, php_value max_execution_time 900, and php_value max_input_time 754—to increase the upload and input processing limits. Then, save these changes and check whether you can upload larger files.

5. NGNIX Configuration for 443 error

If your website is hosted on a Virtual Private Server (VPS) and uses the NGINX web server, you might need to adjust its settings using an SSH client like PuTTY. However, first, you will have to contact your hosting provider for the SSH client login credentials. Then, you need to go to the /etc/nginx/ directory to find the file configuration that will allow you to increase your upload size. Once you have located the configuration file that increases your upload size, restart your web server and check if the error persists.

How to Prevent 413 Status Code

There are ways by which you can prevent the 413 error. Here, we have listed four ways to avoid this error.

Compress large files like images and videos before uploading to avoid exceeding server limits.
Adjust server configurations to accommodate larger file requests.
Break large files into smaller parts.
Use a content delivery network to reduce server load and avoid large request errors.

Summing Up

While the “413 Request Entity Too Large” error can be annoying, it is relatively easy to resolve. Addressing this issue early can save time and ensure a smoother experience when building or updating your website. If you have questions, please check out our FAQs.

Frequently Asked Questions (FAQs)

What causes the 413 Request Entity Too Large error?

The 413 error happens when a file or data exceeds the server’s upload size limit. It can also be triggered by incorrect file permissions, low server resources, or improper server settings.