Record the application error and current setting. Confirm the domain handler, available memory and subscription resource limits. A PHP memory limit is not additional physical RAM, and a web-server timeout can still interrupt a request even after the PHP execution limit is raised.

1. Open the domain PHP Settings page and record the existing values.
2. Identify the setting that matches the failure. For an upload, compare upload_max_filesize and post_max_size; the total request limit must accommodate the upload and request overhead.
3. For an exhausted-memory error, measure the workload and choose a justified value within the service allocation. Do not set every limit to unlimited.
4. Save the smallest necessary adjustment and repeat one controlled version of the failing operation. Avoid repeated production imports or payment operations that could duplicate data.
5. Review additional directives only when the application needs a setting not exposed in the form and your permissions allow it. Preserve valid INI syntax and keep a record of the change.

Check the effective value in the same request environment used by the application. Confirm the operation finishes and that concurrent requests remain healthy. Remove any temporary diagnostics containing environment details.

If the value has no effect, check whether CloudLinux, a different handler, an application setting or a proxy limit controls the operation. A timeout accompanied by slow database queries needs query investigation, not just a longer timeout. Restore the previous value if the change destabilizes other work and send support the exact error and test time.

• Choosing and changing a domain PHP handler in Plesk
• Finding PHP errors for a Plesk website
• Checking disk space and traffic usage in Plesk
• Restoring one Plesk database without replacing the whole subscription

• Plesk: Customer Guide
• PHP: Ini.core