You may also want to check the php.ini file and alter the global default. See:
After configuration changes in either place, we recommend clearing the application cache and restarting PHP-FPM. See:
Keep in mind that the command for restarting PHP-FPM varies per PHP version. The documentation link above will default to displaying the most recent stable version docs (i.e. 2.6). If you are not using AtoM 2.6, be sure to look up the correct documentation link for your AtoM version.
Despite all this, please remember that for large files, uploads via the command-line will succeed where they may fail if you attempt to perform them via the user interface.
This is because digital object upload in AtoM's UI is still a synchronous process that happens on-demand (and not an asynchronous job performed in the background, as with some of AtoM's other long-running processes). This means that for large uploads, you will likely reach the web browser's built-in timeout limit (usually about 1 minute) before the object is finished uploading. Instead, we recommend using some of the command-line options available in AtoM:
If you want to create new descriptions and attach large digital objects to them at the same time, you can use the digital object columns in the archival description CSV templates. See:
If you have existing descriptions and want to attach large digital objects to them, the command-line Digital object load task can be used. See:
Cheers,
@accesstomemory