In the context of your mybox server, max_execution_time is the “stopwatch” that the server uses to monitor every PHP script. If a script-like an image processor or a data importer-takes too long to finish its job, the server kills it to prevent it from hogging resources indefinitely.
In April 2026, as we integrate more complex AI processing and heavy data syncing into our websites, the default 30-second limit is often the first hurdle developers encounter.
Table of Contents
When is an Increase Necessary?
You will know you need to adjust this when you see the error: “Fatal error: Maximum execution time of X seconds exceeded.” Common scenarios on mybox include:
- Heavy WordPress Updates: Large theme or core updates that require significant file unzipping and database rewriting.
- E-commerce Imports: Syncing product stock from an external XML or CSV feed into PrestaShop or WooCommerce.
- Backup Generation: Creating a full site archive where the compression process takes several minutes.
- Image Optimization: Running a batch process to convert hundreds of images to WebP format.
How to Increase the Limit on mybox
Since you cannot modify the global server configuration, you apply this change at the site level.
The .htaccess Method (Global for the site)
- Connect to your mybox account via FTP.
- Navigate to your
public_htmlfolder. - Edit your
.htaccessfile and add this line:php_value max_execution_time 300(This sets the limit to 5 minutes. While the example text suggests 5000, it is safer to start lower to prevent runaway scripts from crashing your Elastic resources.)
The wp-config.php Method (WordPress specific)
Alternatively, you can sometimes set this within WordPress by adding this line:
set_time_limit(300);
Recommended Time Limits for 2026
| Task | Recommended Time | Why? |
| Standard Browsing | 30 – 60s | Keeps the server snappy and kills “stuck” scripts. |
| Plugin Updates | 120 – 300s | Allows enough time for large file extractions. |
| Large Data Imports | 600 – 1200s | Necessary for processing thousands of products/rows. |
| Emergency Tasks | 0 (Unlimited) | Not recommended; only use temporarily for massive migrations. |
A Word of Caution: Performance vs. Stability
Increasing the max_execution_time is a “fix,” but it can also be a “symptom-hider”:
- Infinite Loops: If a script has a bug that makes it run forever, a high limit means it will consume your mybox CPU resources for a longer time, potentially increasing your costs.
- Slow Queries: Sometimes a script is slow because the database is unoptimized. Fixing the database query is always better than just giving the script more time to run poorly.
- The 504 Gateway Timeout: If you set PHP to run for 5000 seconds, but your browser or a proxy (like Cloudflare) is set to 60 seconds, you will still see a “Timeout” error in your browser even if the script is still running in the background.
Summary
The max_execution_time is a safety valve. For most intensive tasks on mybox, increasing this to 300 or 600 seconds via .htaccess provides a perfect balance between allowing your tasks to finish and keeping your server resources protected.