Changing the PHP upload_max_filesize limit with CloudLinux in DirectAdmin

upload_max_filesize sets the maximum size of an individual uploaded file accepted by PHP. The complete upload path also depends on the request-size limit, temporary storage, application settings and any web server or proxy limit.

Prepare for the change

Check the size and type of the file, your available disk space and the application's own upload policy. Back up important data before using a large import file. Prefer the application's supported CLI or staged import process when browser uploads are unsuitable.

01 Change the setting

  1. In DirectAdmin, open the appropriate user account and domain, then search for Select PHP Version. In Evolution it may appear under Extra Features. Open the CloudLinux selector, not an unrelated server administration page.
  2. Check the active PHP version and which websites the selector change will affect. DirectAdmin can expose both its native PHP selection and CloudLinux PHP Selector. The selected domain in DirectAdmin does not by itself prove that an Alt-PHP change is isolated to that domain. Check the selector scope before applying an account-wide change.
  3. Open Options and locate upload_max_filesize. Choose the required value within your service's limits and save.
  4. Set post_max_size high enough for the whole request, including all files and form overhead. For example, a permitted 32 MB file needs a request allowance greater than 32 MB. These are examples, not plan allowances.
  5. Check application-level limits, then upload a small test file and a representative larger file. Use non-sensitive test material and remove it afterward.

Confirm the expected result

Confirm that the application reports the expected permitted size and that the upload reaches its destination intact. Compare the saved file size with the source and test that the application can open or process it.

Why can an upload still fail after I raise upload_max_filesize?

An HTTP 413 response can come from a web server, proxy or CDN before PHP receives the request. Empty form data can indicate a request larger than post_max_size. Check temporary storage, timeout and quota errors before increasing values again. Ask support about restrictions that are not exposed to your account.

  • 0 Users Found This Useful
  • control-panels, development
Was this answer helpful?

Related Articles

Changing the PHP version with CloudLinux in DirectAdmin

A PHP version change can make an application compatible with current dependencies and security...

Managing PHP extensions with CloudLinux in DirectAdmin

Extensions add capabilities such as database access, multibyte text handling, image processing...

Configuring allow_url_fopen with CloudLinux in DirectAdmin

allow_url_fopen controls whether PHP file functions can use supported URL wrappers, such as...

Configuring PHP error display and logging with CloudLinux in DirectAdmin

PHP errors are useful for diagnosis, but displaying them on a public site can expose filesystem...

Adjusting the PHP memory limit with CloudLinux in DirectAdmin

memory_limit limits memory available to an individual PHP script. Increasing it can help a...