WordPress errors are available in all shapes and sizes. In most circumstances, they are simple to understand; for example, the accessibility of WordPress’ error reporting. Although, if the “413 Request Entity Too Large” error surfaces, you may be bewildered.
Without you realising it, you already have all of the information you need to recognise and diagnose the mistake in its name. Fortunately all you’ll require is an ordinary Secure File Transfer Protocol (SFTP) client and head admittance to your server.
We’ll look at how to fix the “413 Request Entity Too Large” problem in this post. We’ll also provide you with a brief checklist of tasks to complete before you begin troubleshooting the mistake to make the process as simple as possible.
What Is the “413 Request Entity Too Large” Error All About? (As Well As Why It Exists)
We observed that the mistake call carries a touch as to what the answer and trouble are. But, before you start sleuthing, we’ll give you a hint: it’s in the term “big.”
You can also watch the video tutorial for this article:
In a nutshell, the “413 Request Entity Too Large” mistakes is as a result of a trouble with length. It occurs when a client sends a request that is too massive for the end server to handle. Contingent upon the idea of the issue, the server might disengage the association with forestall extra demands.
We should part down the mix-up into its constituent parts:
- “413” is one of the 4xx mistake codes, showing an issue between the server and the program.
- “Request Entity”: In this situation, the “entity” is the information payload requested by the client from the server.
- “Too Large” implies that the entity is bigger than the server is willing or ready to serve.
In reality, the name of this mistake has been modified from what it was initially to be more explicit and provide more clarification. It’s currently recognised as the “413 Payload Too Large” error, however in fact, the earlier moniker is much more common.
The basic answer for why the error occurs is because the server is configured to reject explicit uploads that are too big. Consider the following situations when you are uploading a file and there is a maximum file size limit:
TinyPNG’s main page, with the maximum upload size of 5mb indicated.
TinyPNG’s main page.
In most circumstances, some validation will be in place to prevent the mistake… If you receive the “413 Request Entity Too Large” error, your validation attempts may not be as effective as you believe.
Now, let’s get started with how to fix the HTTP 413 Too Large Error.
FIRST METHOD: Fix the issue using Select PHP Version.
- Go to your CPanel.
- Type in php and then click on Select PHP Version.
- Scroll down to upload max file size and increase the values in Upload Next File Size.
- The post max size needs to be more than the file that you are trying to upload.
(Essentially, this is the maximum file size that will be uploaded.)
- Return to your WordPress dashboard once you’ve finished.
- When you refresh the page, you’ll notice that the maximum file size has been raised to 64 mb.
- Now you can easily upload your files according to your needs.
SECOND METHOD: Using .htaccess file.
- Navigate to your CPanel.
- Then, select File Manager.
- Now navigate to your public_HTML folder, or wherever you installed WordPress.
- You must make changes to your.htaccess file.
- If you don’t see your.htaccess file, you need to click the checkbox beside Show Hidden Files as dot files are hidden by default in CPanel.
- Now, you need to edit the .htaccess file.
- Right click on it and select the edit option.
- Now, click on edit agan.
NOTE: Make sure you keep a backup of this file before editing it.
- Finally, you must include some code here.
php_value upload_max_filesize 64M php_value post_max_size 64M php_value max_execution_time 300 php_value max_input_time 300
- As you must see, the maximum file size limit must be 64MB.
- You can modify it to meet your specific needs.
- Don’t forget to save the changes.
- Once the changes have been saved, go back to your WordPress dashboard.
- The changes in the maximum file size limit will be visible when you refresh the page.
You should have been able to fix the 413 ‘Request Entity’ error as long as you followed the instructions correctly.
Please visit our website or contact Digital Suncity if you have any more queries or require assistance.