NextCloud PHP memory limit set to 2 MB for CLI commands
Description
Problem/Justification
Impact
Activity

Maximilian Doerr October 28, 2021 at 6:12 PM
And what about HSTS? That’s not addressed.

Maximilian Doerr October 28, 2021 at 6:10 PM
the php Memory limit will still be an issue though. As it is right now occ can’t be run at all since it’s set too low. Raising the limit to 2 GB would be better and allow occ to be run.

Bug Clerk October 28, 2021 at 2:05 PM
22.02-RC.2 PR: https://github.com/truenas/charts/pull/214

Waqar Ahmed October 28, 2021 at 1:45 PM
i have been discussing this with a nextcloud developer and he has made the attached notes ( please see uploaded screenshot ).
Based on those, we would be for now making sure that we are adding localhost to trusted proxy - about disabling Apache IP re-write, that's already being done. Thank you for letting us know about this!

Maximilian Doerr October 24, 2021 at 1:47 AM
The reverse proxy issue is easily fixed by adding localhost as a trusted proxy and disabling Apache IP rewriting in config.php via trusted_proxies and apache_disable_rewrite_ip.
HSTS needs an Apache config change in the image itself.
No idea how to rectify php-imagick
Details
Details
Assignee

Reporter

There are multiple issues with the NextCloud app. The first issue is that PHP on the CLI is apparently restricted to just 2 MiB which is not enough to get anything running in PHP frankly.
The second issue is that there is no way to customize PHP in a persistent manner. It would be great if the PHP install could load in the mounted data volume I set under a php folder or something.
The container is missing nano and sudo. Nano is useful for obvious reasons, and the occ module only works under www-data user, not root. So being able to change users in the pod's shell is useful, though this is easily worked around with a simple apt update && apt install nano sudo
I'm not attaching a debug here since the problems have been pretty much laid out already and solutions are easy.