Troubleshooting Common PHP Resource Limits (Memory, Execution Time)

PHP resource limits control how much memory, CPU time, and upload bandwidth a single PHP request can consume. When your application exceeds one of these limits, the result is typically a fatal error, a blank page, a 504 gateway timeout, or an upload that silently fails. This guide covers the four most common PHP directives involved, how to diagnose which one is causing the problem, and the two primary paths for adjusting them on INNOVATECH GROUP hosting.

Prerequisites

• An active hosting service with INNOVATECH GROUP (shared, cloud, or dedicated)
• Access to cPanel via the portal's Login to cPanel SSO button (navigate to My Services → hosting service → Quick Access → Login to cPanel)
• Familiarity with PHP error messages and basic server log reading
• For dedicated/VPS servers with root access: SSH access and comfort editing configuration files

The Four Key PHP Resource Directives

memory_limit

Controls the maximum amount of RAM a single PHP script can allocate. When exceeded, PHP terminates the script with a fatal error.

Default: Typically 128M or 256M depending on hosting plan.

Symptoms when exceeded:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 65536 bytes)

Common triggers: Large dataset processing, image manipulation with GD or Imagick, importing CSV files, complex WordPress/WooCommerce operations with many plugins active.

max_execution_time

Controls the maximum number of seconds a PHP script can run before the server terminates it. This does not include time spent on system calls, database queries, or sleep operations — only active PHP execution time.

Default: Typically 30 or 60 seconds.

Symptoms when exceeded:

Fatal error: Maximum execution time of 30 seconds exceeded

Common triggers: Large database migrations, bulk email sending, external API calls that block, plugin/theme updates on WordPress, WooCommerce product imports.

upload_max_filesize

Controls the maximum size of a single uploaded file. Uploads larger than this value are rejected silently — PHP does not process the file at all.

Default: Typically 2M to 64M depending on hosting plan.

Symptoms when exceeded: The upload form appears to succeed but no file is received. PHP's $_FILES array will contain an error code (UPLOAD_ERR_INI_SIZE, value 1).

post_max_size

Controls the maximum size of the entire POST request body, which includes all uploaded files plus form data. This value must be equal to or larger than upload_max_filesize.

Default: Typically 8M to 128M depending on hosting plan.

Symptoms when exceeded: The entire $_POST and $_FILES arrays are empty — PHP discards the request body entirely. This can appear as a blank form submission or a "token mismatch" / CSRF error in frameworks like Laravel.

Step 1: Identify Which Limit Is Being Hit

Check PHP Error Logs

The fastest way to identify a resource limit issue is to read the PHP error log.

Via cPanel:

1. Log in to cPanel via the portal SSO button.
2. Navigate to Metrics → Errors to view the most recent Apache/PHP error log entries.
3. Look for lines containing Allowed memory size, Maximum execution time, or upload-related errors.

Via SSH (dedicated/VPS only):

# Common log locations
tail -100 /var/log/apache2/error.log
tail -100 /usr/local/apache/logs/error_log

# Or check the domain-specific log
tail -100 ~/logs/yourdomain.co.za-error.log

Check Current PHP Configuration Values

To see the active values for all four directives:

1. Create a temporary file named phpinfo.php in your site's document root:

   <?php phpinfo();
   

2. Visit https://yourdomain.co.za/phpinfo.php in a browser.
3. Search for memory_limit, max_execution_time, upload_max_filesize, and post_max_size.
4. Note both the Local Value (active for your site) and the Master Value (server default).
5. Delete phpinfo.php immediately after checking — it exposes sensitive server configuration to anyone who can access the URL.

Distinguish Between 504 Gateway Timeout and PHP max_execution_time

A 504 Gateway Timeout error can look similar to a max_execution_time error but has a different cause:

• max_execution_time — PHP itself terminates the script. You will see the fatal error in PHP error logs.
• 504 Gateway Timeout — the web server (Nginx or Apache reverse proxy) terminates the connection because it waited too long for PHP-FPM to respond. This is a server-level timeout that is separate from PHP's max_execution_time and cannot be changed via cPanel or .htaccess.

If you see 504 errors but no PHP fatal error in the logs, the issue is likely the web server's proxy timeout, not PHP's execution time limit. This requires a support ticket.

Step 2: Adjust Limits via cPanel MultiPHP INI Editor

This is the recommended path for shared and cloud hosting plans.

1. Log in to cPanel via the portal SSO button.
2. Navigate to Software → MultiPHP INI Editor.
3. Select Basic Mode for a simplified interface, or Editor Mode if you prefer to edit the raw INI directives.
4. In Basic Mode, select the domain you want to configure from the dropdown.
5. Locate and adjust the relevant directives:
   • memory_limit — increase to 256M or 512M as needed
   • max_execution_time — increase to 120 or 300 for long-running operations
   • upload_max_filesize — increase to 64M or 128M as needed
   • post_max_size — set equal to or larger than upload_max_filesize
6. Click Apply to save.

Changes take effect immediately for new PHP requests. Existing long-running processes are not affected.

Limits You May Encounter

Hosting plans may impose soft ceilings on these values. If cPanel allows you to enter a value but the change does not take effect (the phpinfo() Local Value remains unchanged), the hosting server has a system-level maximum that overrides your setting. In this case, open a support ticket to request an increase.

Step 3: Alternative — Adjust Limits via .htaccess

If cPanel's MultiPHP INI Editor is unavailable or gives unexpected results, you can set PHP directives via your site's .htaccess file. This works on Apache-based hosting with mod_php or when PHP is running as an Apache module.

Add the following lines to the .htaccess file in your site's document root:

php_value memory_limit 256M
php_value max_execution_time 120
php_value upload_max_filesize 64M
php_value post_max_size 128M

Important caveats:

• The php_value directive only works when PHP is running as an Apache module. On servers using PHP-FPM (increasingly common), .htaccess PHP directives are silently ignored. Use the MultiPHP INI Editor or a custom php.ini file instead.
• If you see a 500 Internal Server Error after adding these lines, your server likely uses PHP-FPM. Remove the php_value lines and use the cPanel INI editor.

Step 4: Validate the Change

After making adjustments:

1. Revisit your phpinfo.php page (create it again temporarily if deleted).
2. Confirm that the Local Value for each directive matches your new setting.
3. Test the operation that was previously failing (file upload, long-running import, etc.).
4. Delete phpinfo.php again after verification.

Common Failure Modes

Security Considerations

• Setting memory_limit extremely high (e.g. 4G) on shared hosting can affect other tenants on the same server. Use the minimum value that resolves the issue.
• Very long max_execution_time values (e.g. 600) increase the window for resource-exhaustion attacks. Only increase this for specific use cases and consider using background job processing (Laravel queues, WP-Cron, or WP-CLI) for long-running tasks instead.
• Never leave a phpinfo.php file accessible in production. It exposes PHP version, loaded extensions, environment variables, and server paths.

When to Contact INNOVATECH GROUP Support

Open a support ticket if:

• Your cPanel INI editor changes are being silently overridden by a server-level maximum
• You are experiencing 504 Gateway Timeout errors that are not caused by PHP's max_execution_time
• You need resource limits raised beyond your hosting plan's soft ceiling
• You have root SSH access on a dedicated server and need guidance on editing the system-wide php.ini
• You are unsure which PHP handler your server uses (Apache module, PHP-FPM, CGI) and which configuration method applies