Resolve an error related to resource limitations

This guide details resource overrun errors that can be obtained by managing and visiting a website.

Preamble

• Resource limits are put in place to maintain the integrity, stability and performance of the shared server, while ensuring a fair experience for all users.
• If a website or application requires significantly higher resources, it may be necessary to move to a Cloud Server or other type of virtual hosting where resources are allocated more flexibly.

Origin of errors

Fatal error: Maximum execution time of 30 seconds exceeded

This error occurs when the server has set a time limit for scripts, usually to avoid tasks that take too long. P.e. if a script attempts to resize many large images in one operation, this may exceed the allowed time limit. The server imposes this limit to ensure a quick response to user queries. The path often mentioned in the error may indicate a more precise origin (e.g. Fatal error: Maximum execution time of 30 seconds exceeded in /home/www/1234567abc/web/wp-includes/media.php on line 123)

memory_limit exceeded

This error occurs when the script or application uses more memory than is allocated to it. This can occur when a script processes a large volume of data or when there is a memory leak. For example, an image management script can consume more memory than is allowed, resulting in this error.

Resolution tracks

Some ways to solve these errors:

• Check scripts that make multiple connections to the server to view data.
• Optimize the script(s) concerned so that they require less resources.
• Increase the limits the site concerned to allow the script to do everything it has to do and/or limit the number of simultaneous connections (especially on a Cloud Server where the limits - live memory, running time, simultaneous connections - can be significantly increased).
• Migrate your accommodation on Cloud Server.

Also take note of this other guide.