How to Check Joomla PHP Limits and Server Settings

Joomla's System Information screen lets you inspect the PHP and server environment that is actually handling Joomla requests. Use it before changing limits: first identify the effective value, then determine which hosting or PHP configuration layer controls it.

Before increasing a PHP limit or changing a server setting, identify the effective value used by Joomla and match it to the symptom. Joomla's System Information area gives you a practical view of the PHP and server environment serving the site, while hosting and server tools control most changes.

Open Joomla System Information

  1. Sign in to Joomla Administrator.
  2. Open System → Information Panel → System Information.
  3. Review System Information for Joomla, PHP, database, and web-server versions.
  4. Review PHP Settings for summarized PHP status.
  5. Open PHP Information for detailed runtime values.

Record the starting values before changing anything so you can prove whether a server-side adjustment took effect.

Match common PHP limits to the failure

  • memory_limit matters when PHP exhausts memory.
  • upload_max_filesize and post_max_size both affect uploads.
  • max_execution_time can affect long-running web requests.
  • max_input_vars can affect very large forms or configuration screens.

Do not assume PHP is the only limit. Web servers, proxies, PHP-FPM, security layers, and hosting plans can impose independent request, body-size, or timeout limits.

Check required PHP extensions and runtime features

Use PHP Information to confirm the modules required by your Joomla release and by the extension involved in the problem. A missing extension is different from a low numeric limit. Verify the exact web runtime because a module enabled for command-line PHP may still be absent from the PHP-FPM pool serving Joomla.

Separate filesystem problems from PHP limits

Use Joomla's folder-permission information when an operation cannot write files. Increasing memory or execution time will not fix an unwritable log, cache, temporary, or media directory. Correct ownership, permissions, ACLs, or hosting restrictions for the affected path without making the whole site world-writable.

Change, verify, and retest one layer at a time

  1. Record the failing action and current effective value.
  2. Change the relevant setting using the host's supported method.
  3. Reload PHP or the applicable service if required.
  4. Return to Joomla PHP Information and confirm the new effective value.
  5. Repeat the original action and check Joomla, PHP, and server logs if it still fails.

This approach distinguishes a setting that failed to apply from a setting that changed successfully but was not the real cause.


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.

Open a Support Ticket