How to Fix Joomla Installation Memory Limit Problems
A memory-limit failure during Joomla installation occurs when the PHP process reaches its allowed memory before the current request finishes. Joomla 6.x currently recommends a PHP memory limit of at least 256 MB. Fix the effective limit for the website, then confirm the failure is truly memory exhaustion rather than a timeout or unrelated fatal error.
1. Confirm the error really is memory exhaustion
Check the PHP or web-server error log immediately after reproducing the failure. A PHP message such as “Allowed memory size ... exhausted” identifies a memory problem and usually shows the attempted allocation and file. A gateway timeout, maximum execution time error, or blank generic 500 page needs different troubleshooting.
2. Check the effective web PHP memory_limit
Use the hosting PHP configuration screen or a temporary PHP information page to inspect memory_limit for the Joomla domain. The command php -i checks CLI PHP and may not match the web server. Joomla 6.x's official technical requirements recommend at least 256 MB, so a materially lower limit should be corrected for a Joomla 6 installation.
3. Change the limit in the configuration that actually controls the site
On shared hosting, use the provider's PHP options editor. On a self-managed server, update the appropriate PHP-FPM pool or php.ini/conf.d configuration and reload the relevant service. Hosts can impose a ceiling that local files cannot override; if your change does not affect the effective value, ask the provider.
4. Avoid unlimited memory as a permanent workaround
Setting an unlimited or extremely high memory limit can hide runaway code and allow one request to consume excessive server memory. Raise the limit to a sensible supported value for the workload and hosting plan. If installation still consumes abnormal amounts of memory, investigate the error trace, package integrity, PHP extensions, and server environment rather than continually increasing the ceiling.
5. Confirm you are installing a clean Joomla package
For a new installation, use a current official Joomla Full Package in a clean target directory. Do not mix unrelated third-party bootstrap code into the installation path while diagnosing memory use. If the package was transferred file-by-file and may be incomplete, replace it from a clean archive before assuming Joomla itself requires an unusual memory limit.
6. Check competing per-request limits
After correcting memory, a long request can still fail because of PHP execution time, PHP-FPM request timeouts, proxy/gateway timeouts, or hosting limits. If the error changes from memory exhaustion to a timeout, troubleshoot that new limit separately. Do not describe every failed long request as a memory problem.
7. Verify the new value before retrying
- Save the PHP configuration change.
- Reload/restart the relevant PHP service if required.
- Verify the effective
memory_limitthrough the web runtime. - Retry Joomla installation once.
- Check the log again if it fails.
If the effective value refuses to change, the most likely causes are editing the wrong PHP configuration, a host-enforced ceiling, or a different PHP-FPM pool serving the domain.
When to involve the host
Ask the hosting provider for help when the plan does not permit the Joomla-recommended memory level, when the domain's effective value differs from the panel setting, or when a server-level policy resets the value. Give them the exact memory exhaustion message and timestamp; that is much more actionable than reporting that Joomla “ran out of memory.”
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.