How to fix request entity too large chrome

The 413 Request Entity Too Large error occurs when you try to upload or make a client request that is too large to be processed by the web server. It also indicates that the web server is configured to restrict large file sizes.

At Cloudways, Nginx is the upstream web server and sets the HTTP request size. By default, the size of the client request body in Nginx is set to 10 MB. If the request exceeds the configured value, the 413 (Request Entity Too Large) error is returned to the client. Therefore, we need to tweak the web server settings to allow larger client requests.

In this tutorial, we will show how to fix the 413 Request Entity Too Large error using the Cloudways Platform.

Fix 413 Request Entity Too Large Error — Navigate to Server Settings

Log in to your Cloudways Platform using your email address and password.

1. From the top menu bar, open Servers.

2. Then, choose your desired server.

3. Under Server Management, select Settings & Packages.

Fix 413 Request Entity Too Large Error — Modifying Upload Size

1. Modify the Upload Size value (in Megabytes) to your preference.

2. Finally, click Save Changes.

Tip

If the file size you want to allow is greater than what we have set, adjust the Upload Size to be greater than the file size.

That’s it! We hope this tutorial was helpful. If you need any help, then feel free to search your query on Cloudways Support Center or contact us via chat (Need a Hand > Send us a Message). Alternatively, you can also create a support ticket.

• Sounds like an issue on the sear site - vs an in-house issue. The only recommendation I have it to either revert to IE 8 and try again, attempt with FireFox or another browser, or try the compatibility view in IE9

  Good luck

  Spice (1) flagReport
  Was this post helpful? thumb_up thumb_down

• Ok thank you.  I would prefer FF or Chrome but nobody wants to change.  I'm thinking it might have to do with their site also, strange that it does work with a reset. 

  thanks

• Probably due to a cached cookie with an identifier that fails on refresh. Just a thought.

• I am surprised that changing stuff on the browser helps. It's a server side error message. (Although it's possible that the user data is what is causing the error and resetting it clears it out). I'd be surprised if this worked with another browser.

• Malware maybe?
  Else it has to be a server error. Email the errorcode to the website?

• I am also having this identical issue pulling up diagrams in sears. It is completely sporadic, and affects all browsers. I made sure everything was updated (hoping for the "mystical" fix) and on FF 17.0.1, we can access diagrams but not individual parts. However, in MOST cases, once you find the part number, you can google search the number and get in that way. 

  PS - I checked for malware, and nothing. Also cleared cache, and nothing. I definitely think it is a server issue, especially since I am not the only one haha.

• Sorry i know this is an old thread but haven't logged in for a long time.  Thanks for all of the responses but it must have been something with the servers on sears's end.  everything began working ok eventually but it was frustrating for quite some time!

by Tashreef Shareef

Tashreef Shareef

Windows & Software Expert

Tashreef Shareef is a software developer turned tech writer. He discovered his interest in technology after reading a tech magazine accidentally. Now he writes about everything tech from... read more

Published on October 29, 2020

• The HTTP error 413 in Google Chrome occurs due to incorrect server configuration or browser issue.
• This article explores a few quick ways to help you resolve this error in no time.
• Have more issues with Chrome? Explore our dedicated Chrome section to find detailed troubleshooting guides.
• Are you looking for a Chrome alternative? Find excellent Chrome alternatives by exploring our Browsers page.

Instead of fixing issues with Chrome, you can try a better browser: OperaYou deserve a better browser ! 350 million people use Opera daily, a fully-fledged navigation experience that comes with various built-in packages, enhanced resource consumption and great design. Here's what Opera can do:

• Easy migration: use the Opera assistant to transfer exiting data, such as bookmarks, passwords, etc.
• Optimize resource usage: your RAM memory is used more efficiently than Chrome does
• Enhanced privacy: free and unlimited VPN integrated
• No ads: built-in Ad Blocker speeds up loading of pages and protects against data-mining
• Download Opera

The HTTP error 413 in Google Chrome usually occurs when loading webforms or accessing background server-side services. Interestingly, the error seems to happen only on the Google Chrome browser and does not affect other browsers like Edge and IE.

The full error reads:

HTTP Error 413. That’s an error. Your client issued a request that was too large. That’s all we know.

The HTTP error 413 usually occurs if the request was larger than the server can handle due to incorrect configuration. However, the error can also occur due to browser issues.

This article explores a few troubleshooting steps to help you resolve the HTTP error 413 on the Chrome browser.

How do I fix the HTTP error 413 in Google Chrome?

Clear browsing data 

1. Launch Google Chrome and click the three-dots button.
2. Select Settings.
3. Scroll down to the Privacy and security section.
4. Click on Clear browsing data.
5. Open the Advanced tab.
6. Select a time range and select the browsing data you want to clear.
7. Click the Clear data button.
8. Once done, relaunch Chrome and check for any improvements.

Clearing the browser data reportedly has fixed the error from many users. If the issue persists, proceed with other steps below.

Flush the Socket Pools from your browser 

1. Open Chrome browser and enter the following in the address bar and hit enter:
   chrome://net-internals
2. From the left pane, click on Sockets.
3. Click the Flush socket pools button. It may break pages with active connection; make sure you don’t have an active connection.
4. Once done, close the tab and relaunch Chrome.

Flushing the socket pool can quickly fix the error 413 is triggered due to a browser issue. If the problem persists, try resetting the browser to factory default.

Reset Chrome to factory default

1. Launch Google Chrome.
2. Click Menu (three dots) and select Settings.
3. Scroll down and click on expand the Advanced section.
4. Scroll down to the Reset and clean up section.
5. Click Restore settings to their original defaults.
6. Read the description carefully and click on Reset settings.
7. The process may take some time; wait till it is completed and then relaunch the browser.

Resetting the browser to factory default will reset your startup page, new tab page, search engine, and pinned tabs. It will also disable all extensions and clear temporary data like cookies. Other data, like bookmarks, history, and saved passwords, will not be cleared.

If you don’t want to reset your Chrome browser yet, skip this step and proceed with the next steps.

Reset the network adapter

1. Press the Windows key, type cmd, then click on Run as Administrator for Command Prompt.
2. In the Command Prompt window, type the following command and hit enter to execute:
   netsh Winsock reset
3. Once done, close the Command Prompt and then restart the computer.
4. Launch the browser and check for any improvements.

Modify the PHP.ini and Nginx.Conf file

Modify PHP.ini 

1. Login to your PHP server.
2. Enter the following command to access the php.ini file:
   nano /etc/php.ini
3. If you are using PHP_FPM, use the following command:
   nano /etc/php5/fpm/php.ini
4. Find the path for these files:
   upload_max_filesize
   post_max_size
5. Once we have the file, increase its limit to 100M. It will look something like this:
   upload_max_filesize = 100M
   post_max_size = 100M
6. Save the file and exit.

Make sure to restart PHP to apply the changes.

Modify Nginx.conf

1. Login to your cloud server.
2. Enter the following command to access the Nginx.conf file:
   nano /etc/Nginx/nginx.conf
3. Find the following variable:
   client_max_body_size
4. Increase the size limit to 100M. It will look something like this:
   client_max_body_size 100M;
5. Once done, restart Nginx to apply the changes:
   sudo service Nginx restart

If the HTTP error 413 occurs only on your Chrome browser, you can mostly fix the issue by clearing the browser cache, flushing the socket pool, or resetting the browser default.

However, if the issue persists, try increasing the file size limit by following the article’s steps.

This article covers:Topics:

Was this page helpful? 3

Start a conversation