I can see the phpinfo itself. What items in phpinfo should I be suspicious of?
just thought of something. Have you disabled 7.2 and enable 7.3?
a2dismod php7.2
a2enmod php7.3
as far as phpinfo, it’s more of what’s not showing up. If it’s not listed on the table, that probably means the file you have is not compatible
I’m 7.3 only.
I am on Nextcloud 18.0.6.
With PHP 7.3.20, php-fpm segfaults when accessing Nextcloud.
I’ve switched to PHP 7.4.8, Nextcloud works ok.
Switching back to PHP 7.3.20, php-fpm segfaults again.
This is on Debian 9.
I also switched to PHP 7.4.8 and I got NC to work. Is this issue specific to PHP7.3.20?
General.
Is Nextcloud in PHP 7.4 working stably anymore?
Should I take this opportunity to switch to a PHP 7.4 environment?
I’ve been using 7.4 with no issue.
Seem like 7.3 is NOT compatible with nextcloud.
1 Like
PHP 7.3 is working like a charm with Nextcloud. In most cases users are forgetting to install all required or removing all legacy components or are not configuring their PHP environment in the right way.
1 Like
Hello,
You have a problem with php-fpm (FastCGI Process Manager). Users of Apache doesnt need this. All command lines with a2dismod or apache module are useless.
When you updated php, did you say “yes” when the updater offered to keep the configuration files of the developer ?
First, check that php7.3-fpm is running : systemctl status php7.3-fpm
Same problem here. Nextcloud with php 7.3.20 fpm broken.
It worked before flawlessly with php 7.3.19.
I upgraded from latest nc 18 to latest nc 19, still broken.
Welcome page works, login not possible.
“Nice” error message:
“proxy_fcgi:error *** Connection reset by peer: *** AH01075: Error dispatching request to :”
(after the last “:” there is just nothing.)
I’m loving it!
I’m having the same issue. Upgraded to php 7.3.20 yesterday. Now I can’t login to Nextcloud or use the dav-API. Same issue with 7.2.32. Nextcloud was working perfectly with 7.3.19.
This is the error message in the logs.
[Wed Jul 15 11:08:50.433405 2020] [proxy_fcgi:error] [pid 26086:tid 140618688878336] [client 77.22.176.119:52511] AH01067: Failed to read FastCGI header
[Wed Jul 15 11:08:50.433486 2020] [proxy_fcgi:error] [pid 26086:tid 140618688878336] (104)Connection reset by peer: [client 77.22.176.119:52511] AH01075: Error dispatching request to :If you’re in a hurry to solve the problem, you’ll have to switch to PHP 7.4.
I made a hasty switch to PHP 7.4, but I still don’t understand the downside.
For various reasons, I cannot go to php 7.4 easily on that server.
I also do not understand the problem. All other Webapplications work fine on that server, with the very same php configurations. Just nextcloud does not work with latest 7.2.X and 7.3.X (I tested both now).
I’m still running Nextcloud 17. According to the system requirements 7.4 is not supported.
@khujo i suggest a solution for your special usecase: upgrade to v18 via console should work on php 7.3, i did myself an upgrade from 18 to 19 “manually” (I stopped using webupdater in general, as it works not that often without flaws).
Then you could switch to php 7.4 maybe, if your server supports that.
I’ll try that. Thank you!
Anyone up with a solution already for nextcloud with php 7.3.20?
I havent had the exact problem. However when I first upgraded to PHP7.4 I had some issues that caused segfaults in php-fpm. It seems that some apps/extensions are a bit buggy and need to be disabled (occ app:disable). For me I’ve had issues with radio, maps, bookmarks and other apps using guzzlehttp library.
1 Like
the problem does not occur because of the PHP version, but only on some servers. e.g. for me with plesk-php-7.2 and 7.3.
Solution: manually install your own PHP (also possible in Plesk) and everything works.
I have this very same problem.
Today the 18.0.7 nextcloud update came out. I installed, and I could log in again. For about 5 minutes, then it went back to “Service unavailable”
@Gjimi How do I install my own PHP in plesk? Any help appreciated!
@maybeageek
Please open an own thread with all details. I think your problem differs from the problem in this thread.