Forwarded to devs Nextcloud gives 503 error after Plesk-PHP Upgrade to 7.3.20

[maybeageek]

User name: maybeageek

TITLE

Nextcloud gives 503 error after Plesk-PHP Upgrade to 7.3.20

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Onyx 17.8.11, Ubuntu 16.04, x86-64

PROBLEM DESCRIPTION

After Plesk installed the update to Plesk-PHP 7.3.20, Nextcloud login is not possible anymore. Instead, a 503 Error message is given.

STEPS TO REPRODUCE

Go to login page, enter username/password, see error message.

ACTUAL RESULT

Error Message 503

EXPECTED RESULT

Logged in Nextcloud

ANY ADDITIONAL INFORMATION

There are multiple threads in the nextcloud forum. People with different Linux Distributions (CentOS, Debian, Ubuntu) are having this problem.

I had this nextcloud instance for years and it always worked fine.
This problem only started after the recent PHP Update.

Some people reported that it works when switching to PHP 7.4, but this is not possible with Onyx and Ubuntu 16.04. And I can't go up to Obsidian because my Hoster does not include this license.

Example threads:

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

Issue - Plesp-PHP Update to 7.3.20 breaks Nextcloud

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...

talk.plesk.com

After update to PHP 7.3.20 I can't login anymore

Nextcloud version: 18.0.6 -> 18.0.7 Operating system and version: Ubuntu 16.04 Apache or nginx version: Apache 2.4.18 (backported patched, built 2020-06-15) PHP 7.3.20 The issue you are facing: After plesk updated my PHP Version to PHP 7.3.20 login wouldn’t work anymore. I stumbled upon a...

help.nextcloud.com

After loginscreen a 503

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out

 

[ruiterples]

Hi

I have ubuntu 16.04 with Plesk obsidian 18.0.28 just after the latest (automatic) update
Nextcloud (15) running on PHP 7.3 was broken.
A downgrade to PHP7.1 solved the problem.

the errors were
nextcloud
" 503 ## Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."


php error_log:
[Tue Jul 21 19:37:15.797037 2020] [proxy_fcgi:error] [pid 1526:tid 140627782113024] [client xx.xxx.xxx.xxx:40684] AH01067: Failed to read FastCGI header


Regards,
Jan

 

[tmuka]

For what it's worth, I'm observing the same symptoms with phpBB forum login on plesk php fpm 7.3.20 and 7.2.32. Downgrading to 7.1.32 resolved the issue in the Apache error log. AH01067: Failed to read FastCGI header. I wish I would have found this before I spent hours failing to fix with a fresh phpbb install.

 

[IgorG]

Developers informed me that bugreport PPPM-12210 was confirmed and submitted.

 

[bac1x]

some news ?

 

[IgorG]

Plesk Help Center

support.plesk.com

 

[IgorG]

Change Log for Plesk Obsidian

Find out about changes, additions and updates to Plesk Obsidian on an iteration to iteration basis.

docs.plesk.com

Argon2 usage in PHP 7.2 and 7.3 no longer causes errors in PHP applications (for example, 503 HTTP errors during attempts to log in to TYPO3 and Nextcloud). (PPP-49780)

 

[Enverex]

We're seeing the exact same behaviour when using Redis with Joomla. The 7.3.19 to 7.3.20 update results in the exact same temporarily unavailable message the others are experiencing. Switching down to 7.1 or disabling Redis negates the error. The Argon fix above hasn't resolved the problem in this case.

 

[bac1x]

Nextcloud 18.0.7.1 works now fine here without erros under fpm-php 7.3.20

 

[maybeageek]

After the plesk update everything is back to normal.