HTTP Error 413 in Chrome: What is it & 4 Ways to Fix it

by Tashreef Shareef
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
Affiliate Disclosure
  • The HTTP error 413 in Google Chrome occurs due to incorrect server configuration or browser issue.
  • Clearing your browsing data is a great way to fix to fix this issue.
  • In some instances, you can solve this problem by resetting your network configuration.
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. This isn’t the only error that you can get, and many reported This site is not secure message as well.

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.

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

What is a HTTP 413 error?

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.

Corrupted cache can sometimes cause this error, but sometimes you need to fix the issue with web sockets in order to resolve this error.

Quick Tip:

Try opening the web with another browser. Built on Chromium as well, Opera is a great alternative to Chrome, being lighter and having a lower error rate.

You may not have an HTTP error in this browser and be able to get back to your tasks quickly. It includes performance-oriented features like hardware acceleration, a battery saver, and an adblocker.

Opera

Display webpages with no errors with this lightweight browser built to perform well!

How do I fix Error 413 on Chrome?

1. Check the Chrome browser for issues

Clear browsing data 

  1. Launch Google Chrome and click the three-dots button. Select More tools. Next, select Clear browsing data.
  2. Select a time range and select the browsing data you want to clear.
  3. Click the Clear data button.
  4. 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. In Chrome, navigate to 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.

Expert Tip: Some PC issues are hard to tackle, especially when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may be partially broken. We recommend installing Restoro, a tool that will scan your machine and identify what the fault is.
Click here to download and start repairing.

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.

2. Reset Chrome to factory default

  1. Launch Google Chrome.
  2. Click Menu (three dots) and select Settings.
  3. Select Reset and clean up.
  4. Click Restore settings to their original defaults.

  5. Read the description carefully and click on Reset settings.
  6. 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.

This is a quick and easy solution, so try it if you’re getting Request entity too large on Chrome.

3. 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.

This is a simple solution, but it might help you with 413 that’s an error, your client issued a request that was too large that’s all we know error message.

4. Modify the PHP.ini and Nginx.Conf file

Modify PHP.ini 

  • Login to your PHP server.
  • Enter the following command to access the php.ini file:
    nano /etc/php.ini
  • If you are using PHP_FPM, use the following command:
    nano /etc/php5/fpm/php.ini
  • Find the path for these files:
    upload_max_filesize
    post_max_size
  • Once we have the file, increase its limit to 100M. It will look something like this:
    upload_max_filesize = 100M
    post_max_size = 100M
  • 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

This is a quick and easy solution and it should help you with 413 error code on Nginx, so be sure to give it a try.

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 isn’t the only error, and many reported that HTTPS is not working in Chrome, but we covered that in a separate guide.

Did you find a different solution for this problem? Let us know in the comments below.

idee restoro Still having issues? Fix them with this tool:
  1. Download this PC Repair Tool rated Great on TrustPilot.com (download starts on this page).
  2. Click Start Scan to find Windows issues that could be causing PC problems.
  3. Click Repair All to fix issues with Patented Technologies (Exclusive Discount for our readers).

Restoro has been downloaded by 0 readers this month.

This article covers:Topics: