- 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.
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?
Check the Chrome browser for issues
Clear browsing data
- Launch Google Chrome and click the three-dots button.
- Select Settings.
- Scroll down to the Privacy and security section.
- Click on Clear browsing data.
- Open the Advanced tab.
- Select a time range and select the browsing data you want to clear.
- Click the Clear data button.
- 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
- Open Chrome browser and enter the following in the address bar and hit enter:
- From the left pane, click on Sockets.
- Click the Flush socket pools button. It may break pages with active connection; make sure you don’t have an active connection.
- 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
- Launch Google Chrome.
- Click Menu (three dots) and select Settings.
- Scroll down and click on expand the Advanced section.
- Scroll down to the Reset and clean up section.
- Click Restore settings to their original defaults.
- Read the description carefully and click on Reset settings.
- 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
- Press the Windows key, type cmd, then click on Run as Administrator for Command Prompt.
- In the Command Prompt window, type the following command and hit enter to execute:
netsh Winsock reset
- Once done, close the Command Prompt and then restart the computer.
- Launch the browser and check for any improvements.
Modify the PHP.ini and Nginx.Conf file
- Login to your PHP server.
- Enter the following command to access the php.ini file:
- If you are using PHP_FPM, use the following command:
- Find the path for these files:
- 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.
- Login to your cloud server.
- Enter the following command to access the Nginx.conf file:
- Find the following variable:
- Increase the size limit to 100M. It will look something like this:
- 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.