Show
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 SettingsLog in to your Cloudways Platform using your email address and password.
3. Under Server Management, select Settings & Packages. Fix 413 Request Entity Too Large Error — Modifying Upload Size
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.
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:
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
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
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
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
Modify the PHP.ini and Nginx.Conf fileModify PHP.ini
Make sure to restart PHP to apply the changes. Modify Nginx.conf
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.
Was this page helpful? 3
Start a conversation |