How to fix the "413 request too large" error on a WordPress website
WordPress errors come in various shapes and sizes. In most cases, it is easy to decipher them; thus access the WordPress error report. In addition, when the "413 Request too large" error occurs, it may give you a headache.
Before you know it, you already have everything you need to understand and diagnose the wrong name. The good news is that you don’t need the standard Secure File Transfer Protocol (SFTP) and administrators to access your server.
In this article, we will look at how to solve the "413 Request Too Large" error. Before starting to resolve the error, we will also provide you with a quick overview of the steps that need to be taken so that the process is very simple.
contents
1. What is (and why) the "413 Request Too Large" error
2. What is needed to solve the "413 Request Too Large" error
3. Three "pre-steps" before winning the "413 Big Need" award
4. How to solve "413 Big Bad Request" on WordPress website (3 ways)
What is the "413 Request Too Large" error (and why it exists)
We have noticed that in the wrong name, there is an indication of the solution and the problem. However, before you go to check, we will surprise you: it is "big" in color.
In short, the error of "413 Too Request Too Large" is a big problem. This happens when the request from the client is too large for the later server process. Depending on the nature of the error, the server may completely interrupt the connection to prevent further requests.
Let's break down the error:
• "413": This is one of the 4xx error codes, indicating that there is a problem between the server and the browser.
• "Request statement": In this case, the "instruction" is the upload of information requested by the client from the server.
• "Too big": It's simple: the organization is bigger than the server wants or can provide.
In fact, this error has changed its name, and it was originally intended to be more specific and clearer. It is now called the "413 Payload Too Large" error, although in practice you will find older names.
The simple explanation for the error is that the server is set to reject an apparently excessive load. When you think of files with maximum file size limits, consider:
TinyPNG homepage.
In most cases, there will be some approvals to prevent errors. If you see a "413 big request" error, these approval attempts may not be as strict as you think.
What you need to do is to resolve the "413 Request Too Large" error
To correct this error is to increase the maximum file size of the specified server. Once it gets out of the way, you should no longer see the error.
Therefore, to correct the "413 Request Too Large" error, you need to do the following:
• Your server access manager.
• A suitable SFTP client (we have received a lot).
• SFTP usage information-There is a good basic guide on WordPress.org, you don't need more.
• A text editor, although it doesn't need anything too complicated.
• Provide clean and existing support when the worst happens.
In addition, we use SFTP instead of FTP throughout this article. In short, the former is safer than the latter (hence the name). In other words, although you need to explore other differences, for most users, this feature remains the same.
In addition, it is worth mentioning that the MyAtakdomain dashboard has many features to help you navigate the server. For example, each site provides easy-to-understand SFTP connection information:
The SFTP panel in the MyAtakdomain dashboard.
This can help you easily access your website. In some cases, you can extract credentials directly from your preferred SFTP client.
3 "steps" you can take before winning the "413 Big Need" award
Before breaking the device box, you can take some steps to resolve the "413 request too large" error. There are two-each can provide you with a way to get rid of the wrong charity.
1. Try to upload large files to your server via SFTP
Since the problem is related to the size of the files stored on the server, it is better to bypass the first connection and upload large files to the server itself. The best method is SFTP.
This is because protocols like SFTP are almost "near sensitive", so you can respect the way you access the server. At the same time, you can also identify front-end issues that may cause errors.
To do this, log in to your website via SFTP and find the wp-content folder. There will be an upload folder.
View the upload folder from the SFTP client.
Next, upload your files to this server folder and see how it turns out. If the upload is successful, we recommend that you send an email to the website developers, as they may wish to investigate the issue further in the future.
2. Check for server permission errors
Of course, authorization errors will stop every server request. Therefore, you should ensure that users have sufficient permissions to download files of any size. Once the sorting is complete, the error will disappear.
The first step is to determine whether this is a single user problem (in this case, it may be restricted for some reason). If too many users get the "413 Request Too Large" error, you can be more confident than when you log in.
We will propose two "first fixes" here:
• Double check your WordPress file permissions, only if something goes wrong.
• Delete and recreate your SFTP user (general research is a good idea).
Although they may not fix the error in the first place, you will at least know that your user files and structure should be.
How to solve the "413 Big Bad Request" for your WordPress website (3 methods)
After taking the first step, you can resolve the error yourself.
The following three methods are listed from the easiest to the most difficult. Understanding it is the best way to get the least resistance.
1. Modify the WordPressfunctions.php file
First, you can use your functions.php file to help increase the file upload size of your website. To do this, first log in to your website via SFTP using the credentials in the hosting control panel.
After entering it, you will need to search for the file itself. The functions.php file must be located in the root directory of the server. In most cases, this root is called www or public_html, or it may be the abbreviated name of your site.
Once you find it, you can open it in your favorite text editor. If you don't see the file, you can use a text editor to create it.
With our simplified website management, spend less time solving problems and more time developing your business. Try Atakdomain for free.
After opening the file, type the following:
@ini_set( '_max_size' , '64M' );
@ini_set( 'post_max_size', '64M');
@ini_set( 'max_execution_time', '300' );
In short, it increases the maximum file size of messages and uploads when the server tries to track requests. The numbers here can be any numbers you want, but they must be large enough for the error to disappear. In fact, 64 MB is enough for all tasks, but for the heaviest tasks.
Function file .php.
When you are ready, save the file and upload it back to the server. Next, check if the "413 Request Too Large" error still exists. If so, please try another method.
2. Modify the WordPress.htaccess file
Like your functions.php file, your .htaccess file is located on your server. The difference here is that .htaccess is the configuration file of the Apache server. If you are a Atakdomain client, you will know that we are running an Nginx server, so you will not see this file during the installation.
Nonetheless, for those who have an Apache server, this is the method you need. As with the functions.php directory, first log in to your server via SFTP, and then check your root folder as before.
The .htaccess file should be included in this directory, but if it is missing, we recommend that you contact your host to determine its location and whether your server is running instead of Nginx.
When you see it, open it again. You will find some tags, the most important one here is #END WordPress. You want to write the following 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, the code it adds is almost the same as the code you will add to the functions.php file, but it looks like a direct server directory.
.htaccess file.
When you are done, make changes, upload files, and check your site again. If you still encounter problems, we will again recommend that you contact your host because they need to correct some aspects of your installation that are not within the scope of this article.
3. Configure your Nginx server
My last method is specifically for the Nginx server used on Atakdomain. When you use .htaccess files, the goal is the same because you are talking to the server, not switching to WordPress.
We said that for the Apache server, you will use .htaccess. However, for Nginx servers, you may want to view the nginx.conf file. Instead of traversing the entire chain at every step, we went through all the details in our post about changing the maximum load size of WordPress.
Please note that you also need to modify the php.ini file according to the changes made to nginx.conf. We also included it in the blog post above, so please review the actual steps.
compilation
Although WordPress is a reliable platform, over time you will find many different WordPress errors. The "413 Request Too Large" error is related to your server, but not WordPress. Therefore, the solution to this error is different from other platform-specific issues.
If you have SFTP capabilities, there is no reason why this error cannot be fixed quickly. This depends on the upload size specified in the server configuration file, so the .htaccess or nginx.config file needs to be extracted. It is a good idea to break your text editor and edit these files, if you are a Atakdomain customer, we are ready to support you in the process.
_______________________________________
Save time, money, and improve website performance by:
• Instant help from WordPress hosting experts, 24/7.
• Cloudflare Enterprise integration.
• Reach global audiences through data centers around the world.
• Use our built-in application performance monitor for optimization.
