Issue Plesp-PHP Update to 7.3.20 breaks Nextcloud

[maybeageek]

Hi all,

I am having an issue, and I am not alone.

I'm on Ubuntu 16.04, but this happens to other Distributions, too.
After Plesk 17.8.11 updated my PHP installation from 7.3.19 to 7.3.20, Nextcloud login page still shows, but a login just results in a "503 service unavailable".

This issue does not appear with NON-Plesk PHP 7.3.20

Where could this come from and what could be done?

This is one issue I found: First

Any help appreciated.

 

[maybeageek]

I dug around a little more, and it seems that nextcloud is missing opcache from PHP.
However, the settings haven't changed, the module is installed, at least that is what apt list shows me.

But somehow, nextcloud can't use opcache anymore. Anybody any ideas?

 

[IgorG]

Question - I want to downgrade from php7.3.20 to 7.3.19

I updated to PHP 7.3.20 and faced an issue with Nextcloud not working and I did. The user can log in to Nextcloud, but immediately after that a 502 error occurs. [error] 21578#0: *2 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: IP-ADDRESS...

talk.plesk.com

 

[maybeageek]

Question - I want to downgrade from php7.3.20 to 7.3.19

I updated to PHP 7.3.20 and faced an issue with Nextcloud not working and I did. The user can log in to Nextcloud, but immediately after that a 502 error occurs. [error] 21578#0: *2 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: IP-ADDRESS...

talk.plesk.com

Thanks for the hint.
However, I can't install PHP 7.4, Plesk doesn't offer it to me. And I can't upgrade to Obsidian as my hoster won't give me a new license.
So there must be a fix.

Over at the nextcloud forum several people have the same problem, all with Plesk and PHP 7.3.20

 

[bac1x]

same problem here

 

[IgorG]

Please submit detailed report here Reports I will forward it to developers for the further investigation.

 

[bac1x]

After Plesk 17.8.11 updated my PHP installation from 7.3.19 to 7.3.20, Nextcloud login page still shows, but a login just results in a "503 service unavailable".

I have exactly the same problem here Im on Ubuntu 16.04.6 LTS Kernel Version 4.4.0-1062.12.1.vz7.131.10 (SMP) x86_64
tried php version 7.2.32 with the same problems

 

[Bitpalast]

CentOS 7.8, Plesk PHP 7.3.20, latest Plesk MU
I am unable to reproduce the issue. Is there anything specific that I can do to reproduce it, e.g. click on certain icons, upload or download certain files, wait for a certain amount of time?

 

[bac1x]

immediately after the login page
Plesk shows me on Protokoll

2020-07-21 16:07:46 Error 503 POST /index.php/login HTTP/1.1 Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0 1.22 K SSL/TLS-Zugriff für Apache
2020-07-21 16:07:46 Access 200 GET /error_docs/styles.css HTTP/1.1 https://xxxx.xxxxx.xxx/index.php/login Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0 3.00 K SSL/TLS-Zugriff für Apache
2020-07-21 16:07:46 Access 200 GET /index.php/login HTTP/1.1 Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0 15.2 K SSL/TLS-Zugriff für Apache
2020-07-21 16:07:46 Error AH01067: Failed to read FastCGI header Apache-Fehler
2020-07-21 16:07:46 Error (104)Connection reset by peer: AH01075: Error dispatching request to :

 

[Bitpalast]

I am still unable to reproduce the issue. I had created a Nextcloud installation on an Onyx system that is in production, set to PHP 7.3.20 PHP-FPM this morning. It seems that it was running without issues during the day, I can still login and do all kinds of things in it, logout, login again etc.

"2020-07-21 16:07:46 Error AH01067: Failed to read FastCGI header Apache-Fehler
2020-07-21 16:07:46 Error (104)Connection reset by peer: AH01075: Error dispatching request to : "

is a common issue with many websites. I'd start of by creating a phpinfo() file in the directory where Nextcloud is installed and try to open that file in that directory from the web.
File with this content:

<?php phpinfo(); ?>

If it displays the PHP information page, the issue is most likely with the Nextcloud installation and not with PHP.

I have seen the "Error dispatching request to:" error most frequently when websites end up in infinite while...next loops, never delivering a result to the upstream (Nginx) or never completing a PHP operation (timeout of PHP). This can happen for issues with rewrite rules or for a website waiting on input from external sources that never arrives. I cannot rule out issues with opCache as someone suggested here or in the other thread, but that would be something very new that was never before seen (here on this forum in connection with the "Error dispatching...").

 

[bac1x]

can i switch back to PHP 7.3.19 FPM or reverse the plesk update?

 

[Bitpalast]

Not that I'd know. You can install your own PHP if you like.

Adding Custom PHP Versions (Linux)

On Linux systems, you can install any PHP version you need and then make it available in Plesk by registering it with...

docs.plesk.com

 

[bac1x]

i send u later the php output information
must first see if personal data is visible

 

[bac1x]

do u need complete output of it ?

 

[bac1x]

here

 

[maybeageek]

Hi,

somehow I did not get a notification that this thread had answers.

It is interesting that it is so many people having this exact problem, even over in the nextcloud forums, and only with plesk.
But it might be that it is some kind of opcache issue, at least that is what the current working hypothesis over there. And this would then be ok on newly installed systems.

I haven't found a way to reset my opcache files yet.

 

[maybeageek]

The reason why we tend towards the opcache is that my nextcloud instance can be logged in sometimes (seldom) but only for about a minute or two. Then it is back to the 503.
But when I can, I get this message:

• Das PHP-OPcache-Modul ist nicht geladen. Für eine bessere Leistung empfiehlt es sich das Modul in Deiner PHP-Installation zu laden.

(Rough translation: The PHP-OPcache module is not loaded. For better performance, load the module in your PHP installation.

However, the module is loaded and in the config enabled. Always was. opcache can cause the 503, and this happened specifically with the PLesk PHP-7.3 update.

 

[maybeageek]

I just created an info.php and a reset.php.
The first shows the php infos, and the other one is supposed to reset opcache.

However, I can't access them. I immediately get the 503 again.

 

[maybeageek]

I just opened an official report for the plesk devs: Nextcloud gives 503 error after Plesk-PHP Upgrade to 7.3.20