How to adjust max_execution_time in cPanel MultiPHP INI Editor

Category: cPanel

max_execution_time defines how many seconds a PHP process can run before the server stops it. On shared hosting, adjusting it from MultiPHP INI Editor can help when a CMS import, update, backup, or admin task stops because it runs too long.

Use it as a specific, gradual adjustment. If the process needs much more time than your plan allows, it is better to optimize the task or ask for help before raising values at random.

Before you start

  • Have cPanel access for the account where the affected domain is hosted.
  • Write down the action that fails and the exact message, for example Maximum execution time exceeded.
  • Confirm the correct domain if you manage several sites in the same account.
  • Avoid changing account-wide values if only one site is failing.

Adjust the execution time

  1. Log in to cPanel and open MultiPHP INI Editor. In some themes it may appear as Editor INI de MultiPHP.
  2. In Basic Mode, select the affected domain from the location menu.
  3. Find max_execution_time. If it does not appear in basic mode, review Editor Mode only if you know which domain you are editing.
  4. Change the value gradually, for example from 30 to 60 or 90 seconds, depending on what your plan allows.
  5. Save with Apply or Save, depending on the mode you are using, and wait for the confirmation.
  6. Repeat the action that failed without modifying other parameters at the same time.

Verify the change

  • max_execution_time shows the new value for the correct domain.
  • The action that failed goes further or finishes without showing the timeout error.
  • Errors or your CMS log no longer repeats the same message when you test again.
  • The site keeps loading normally after the test.

Common errors

  • The error stays the same → another domain or location was edited → return to MultiPHP INI Editor and confirm the selector.
  • The value saves, but does not go past the limit → the plan has a maximum allowed value → use a moderate value and contact support if you need more time.
  • The import stops again → the file or process is too heavy → split the import, optimize the plugin, or use a method recommended by support.
  • The site becomes slow during the test → the process consumes resources for longer → review Resource Usage before repeating it many times.

When to ask for help

Open a ticket if the limit does not change even after saving correctly, if the process needs very high times, or if the error appears together with CPU, memory, or I/O usage. Include the domain, approximate time, configured value, and full message so support can review the case without guessing.

Still need help?

If this guide didn’t solve your issue, our team can help you via ticket.

Open ticket Go to my account