Ask the provider which PHP mode applies and record the current effective values. Back up any existing .user.ini and check the application’s actual requirement rather than raising limits arbitrarily.

1. For PHP-FPM, open File Manager, choose the domain and enter its actual public html directory.
2. Open the existing .user.ini or create a file with that exact name. The word user is literal, not a placeholder for the account username.
3. Add only supported per-directory directives in INI syntax. Coordinate related values, such as an upload limit and the total request-body limit.
4. Save and allow the runtime’s configuration refresh interval. Verify the effective setting through a protected diagnostic or application status view.
5. Test the affected action and remove temporary diagnostic output. Retain the previous file for a controlled reversal.

For an application whose approved requirement is a single file up to 16 MiB, these are illustrative entries in the existing .user.ini:

upload_max_filesize = 16M
post_max_size = 24M

Use only values permitted by the hosting service. The request allowance must also fit all submitted files and form fields; several 16 MiB files would exceed this example. Preserve unrelated existing directives and allow the PHP configuration refresh interval before checking the application effective values.

Test a small permitted file and the intended representative upload, then confirm the saved file is intact. If PHP reports the old values, investigate the handler, file location and provider restrictions. An upstream HTTP 413 response or application-specific rejection can require a separate fix.

The permitted setting should apply to the intended domain and solve the measured requirement without exceeding the service’s resource limits.

Some directives are administrator-only or locked by the provider. A SuPHP configuration uses a different supported procedure and may require provider assistance; do not paste old handler-specific .htaccess directives into a PHP-FPM site.

No. It changes an application limit within the available service capacity. Excessively high values can worsen resource pressure, so base the change on the workload and plan allowance.

• Selecting a PHP version for a SiteWorx domain
• Following SiteWorx web-server logs during a reproducible error
• Changing SiteWorx file permissions for a specific application
• Controlling which file extensions SiteWorx treats as PHP

• InterWorx: Set Individual Domain PHP Ini Configurations PHP Fpm
• PHP: Configuration.file.per User