Nick Howitt wrote:

You just have to remember that each version of PHP has its own php.ini file. I think you can also do the change in a .htaccess file, but I'd need to research it. If you can, that would work irrespective of the version of PHP.

I get where you're coming from, but htaccess doesn't appear to work - certainly not in a virtual website. I'd prefer to set it there as it's then only applicable to the individual website, but I really can't be ar*ed to try and figure out why it doesn't work! - changing it in php.ini works. - and there are other posts saying '.htaccess doesn't work' so I'm not prepared to waste any more time trying to figure out why; I've already wasted a couple of hours on it. I've tried the AllowOverride (nope), SymLinks (nope). It's obviously something buried in the Apache configuration that's blocking their use.

You just have to remember that each version of PHP has its own php.ini file. I think you can also do the change in a .htaccess file, but I'd need to research it. If you can, that would work irrespective of the version of PHP.

Tyler Randolph wrote:

Yes, it is using PHP 7.1 although doing that command that you mentioned still causes the message to show up: "The current PHP memory limit is below the recommended value of 512MB."

Is there another place that we would have to change memory_limit other than in /etc/php.ini?

That's all I changed (in the relevant /etc/opt/rh/php7.xx/php.ini)

Perhaps restarting httpd would also help. Other than that, ask Nextcloud. I have no idea about PHP.

Yes, it is using PHP 7.1 although doing that command that you mentioned still causes the message to show up: "The current PHP memory limit is below the recommended value of 512MB."

Is there another place that we would have to change memory_limit other than in /etc/php.ini?

Which version of PHP is nextcloud using? Is it by any chance 7.1? If so, edit /etc/opt/rh/rh-php71/php.ini then perhaps something like:

systemctl restart rh-php71-php-fpm

I changed memory_limit in /etc/php.ini to 512M and then restarted httpd, but I still got the message: "The current PHP memory limit is below the recommended value of 512MB."

I can't find any reference to memory in my logs. I've tired enabling nextcloud logging and I could not get that to work either. Perhaps you can roll back your VM and try changing memory_limit to 512M then restart httpd then perform the upgrade and see if the message goes away.

I'm out atm but iirc you can adjust it in /etc/php.ini. Mine was set to 128M. Then I guess you need to restart httpd but i don't know what to do to test it is then OK.

Thanks Nick. I added in that missing part to the command.

I'm still trying to figure out the PHP Limit message it is giving, but it doesn't appear to affect it in any harmful way. Let me know if you see anything there.

@Tyler,
It looks like you also need to add:

--enablerepo=clearos-contribs-testing

or it does not pick up nextcloud-16.0.4.

When it runs the nextcloud upgrade script I get (among the long list up upgrading log messages):

The current PHP memory limit is below the recommended value of 512MB.

Other than that, it looks like the upgrade has gone OK.

I believe you will need SDN 1.4, but I'm not sure. It would be best if you could test using app-nextcloud or app-nextcloud-business. I can give a 30-day trial license to the people who want to test it out so they can have access to the repos.

Then you can run the following commands.

sed -i -e 's/^jws_version.*/jws_version = 1.4/' /etc/product

ENABLE_BETA=True yum --enablerepo=clearos-contribs-testing --disablerepo clearos-centos-verified-testing,clearos-epel-verified-testing install app-nextcloud nextcloud

The sed command changes the jws version to 1.4 so that the repos work.

The ENABLE_BETA turns on the testing repos.

I volunteer!

I can help. Do I need SDN 1.4 to pick up app-nextcloud from clearos-paid-testing or can I do it from 1.2? Do I even need app-nextcloud?