Clear the ownCloud PHP Memory Warning in the Correct Runtime

Set the memory_limit for the PHP runtime that serves ownCloud to at least the value named in the warning—commonly 512M—then restart that PHP service and reload the admin overview. Editing the CLI configuration alone will not fix a warning generated by Apache or PHP-FPM. Also, a 512 MB per-process PHP limit is not the same as adding 512 MB of physical RAM to the server.

What the warning means—and what it does not

memory_limit is PHP’s maximum memory allowance for an individual request or script. It is a cap, not a guarantee that PHP will use that much memory, and raising it does not reserve that amount for every visitor. However, several PHP workers can run at once, so set the value with your server’s available RAM and worker count in mind. If the host is small or busy, increasing the limit may make resource pressure worse; check capacity before raising it.

The value commonly associated with this warning is 512 MB. The ownCloud Server 10.16 configuration guide separately says that post_max_size should be at least 512 MB, but that is a different PHP setting: it controls the maximum size of POST request data, not PHP’s memory ceiling. Do not change post_max_size expecting it to clear a memory_limit warning. Use the exact value shown by your ownCloud admin page or hosting provider, and treat server requirements as version- and deployment-dependent.

One common false fix is changing /etc/php/[version]/cli/php.ini because it is easy to inspect with a terminal command. ownCloud’s documentation distinguishes that file from the web-server configuration. A CLI value can affect occ and cron jobs while the website continues to use Apache’s or PHP-FPM’s separate configuration. Confirm which PHP handler serves your site before editing.

Find the active web PHP configuration

  1. Record the current state. Note the full warning and value displayed in ownCloud’s Administration settings. Identify your ownCloud version, PHP version, web server, and whether PHP runs through Apache or PHP-FPM. If you use a hosting panel or managed package, check its PHP settings first; it may generate or override configuration files.
  2. Locate the web-server PHP configuration. On Debian or Ubuntu, common paths are /etc/php/8.1/apache2/php.ini for Apache’s PHP module or /etc/php/8.1/fpm/php.ini for PHP-FPM. Replace 8.1 with the installed PHP version. Other distributions use different paths. The CLI file, often under /etc/php/8.1/cli/, is separate. For PHP-FPM, pool-level settings or a hosting control panel may override the main FPM file.
  3. Change only the relevant value. Back up the configuration file, then set or update the active web PHP directive, for example:
memory_limit = 512M

Use the number in your own warning if it differs. PHP accepts shorthand such as M for megabytes; use the format supported by your PHP configuration. If the directive appears more than once, confirm which file and later override are active rather than appending duplicate values at random.

  1. Restart the matching service. For PHP-FPM on Debian or Ubuntu, an example is sudo systemctl restart php8.1-fpm; restart the web server too if your setup requires it. For Apache’s PHP module, restart Apache, for example sudo systemctl restart apache2. Substitute the actual service names for your distribution and PHP version. On managed hosting, apply the setting in the provider panel and use its restart or reload control if available.

Verify the web value, not just the CLI value

Refresh the ownCloud administration overview and check whether the warning is gone. If it remains, the web process is probably reading another configuration or a later override is taking precedence. A terminal check such as php -i reports the CLI runtime by default, so it cannot prove what Apache or FPM uses. Prefer your hosting panel’s web-PHP information or ask the administrator to inspect the active web SAPI. If you create a temporary PHP information page to check the web runtime, restrict access to it and delete it immediately afterward; a publicly accessible configuration report can disclose sensitive server details.

Also confirm the service restart succeeded and that the value is adequate for the workload without exhausting system memory. If ownCloud is running in Docker, a snap, a hosting panel, or another managed package, do not edit host paths by guesswork: use the deployment’s documented PHP configuration method. ownCloud’s published guidance notes that shared hosting and PHP-FPM installations can keep settings in nonstandard locations or separate files.

When the warning does not clear

  • The admin page still shows the old number: verify the PHP version and handler used by the website, inspect FPM pool overrides or panel-level settings, then restart the correct service.
  • The warning clears but requests fail or the host becomes unstable: review available RAM, PHP worker count, and web-server logs. A higher per-request cap does not create physical memory.
  • Only uploads fail: review upload-specific limits separately, including upload_max_filesize and post_max_size. ownCloud’s 10.16 guide calls out a 512 MB minimum for post_max_size; other limits and proxy settings may also apply.

After verification, remove any temporary diagnostic file and keep a note of the PHP version, handler, configuration file, and value you changed. That makes future upgrades or PHP version switches easier to troubleshoot.

Official references

Leave a Comment

Clear the ownCloud PHP Memory Warning in the Correct Runtime

Set ownCloud’s web PHP memory limit, restart the matching service, and verify the active value without confusing it with CLI settings or upload limits.

Troubleshoot ownCloud 10 MySQL Connection Failures

Find out whether MySQL, PHP, socket settings, or database permissions are blocking ownCloud 10, then verify a safe fix.

Set a Firm Expiration Limit for ownCloud Public Links

Set a Firm Expiration Limit for ownCloud Public Links

Make public link expiration mandatory in ownCloud Classic, set a maximum lifetime, and check existing shares that may need separate cleanup.

Add TOTP Two-Factor Login to ownCloud Infinite Scale with Keycloak

Add TOTP Two-Factor Login to ownCloud Infinite Scale with Keycloak

Enable TOTP through Keycloak, enroll users safely, and understand when Infinite Scale’s route-level MFA settings apply.

Restore ownCloud Sync by Matching the Client to Your Server

Check whether the issue is an OC10 and 7.x compatibility break or a damaged CSync journal, then apply the right fix without deleting synced files.

Put ownCloud on HTTPS with Let’s Encrypt and Nginx

Put ownCloud on HTTPS with Let’s Encrypt and Nginx

Choose HTTP-01 or DNS-01, configure an ownCloud reverse proxy, and verify Certbot renews HTTPS certificates automatically.

Connect ownCloud Infinite Scale to LDAP for User Sign-In

Configure oCIS LDAP sign-in, align user and group lookups, and verify TLS and schema settings before rollout.

Connect an S3 Bucket to ownCloud 10 as External Storage

Connect an S3 Bucket to ownCloud 10 as External Storage

Add an Amazon S3 bucket to ownCloud 10, prepare compatible credentials and endpoints, and check access without confusing a mount with primary storage.

Automate ownCloud Database Dumps with a Safe Nightly Cron Job

Automate ownCloud Database Dumps with a Safe Nightly Cron Job

Schedule protected MariaDB dumps for ownCloud Server, handle maintenance mode safely, and verify each backup before relying on it.

Move ownCloud Classic to oCIS with a Supported Migration

Plan an ownCloud 10 to oCIS migration with the supported app, ordered commands, identity checks, and a clear list of data that needs separate handling.