[Error 503 only for Froxlor after changing to php7/fpm]

Still, in the 35_froxlor* VHost files for the customer sites the path is the same (replacing froxlor.panel-* by the customer) and there it works?

[Error 503 only for Froxlor after changing to php7/fpm]

But this file is created by froxlor, so somewhere this path has to come from?

And what exactly do you refer to by "your side"? Apache config? FPM config? Froxlor config?

[Error 503 only for Froxlor after changing to php7/fpm]

Vhost for port 80:

https://pastebin.com/wwxH5efn

Vhost for port 443:

https://pastebin.com/TnXSRbbQ

Just noticed that there is still some php5-fpm stuff remaining...?

[Error 503 only for Froxlor after changing to php7/fpm]

Hello there.

After updating to PHP 7.1 with FPM my customer sites work perfectly, however I cannot access the Froxlor backend (as well as phpmyadmin) anymore, I get an error 503. Froxlor is supposed to also run with FPM.

I am running on Debian8, Apache 2.4, PHP 7.1, PHP 7.1-FPM

The apache error log reads:

[Tue Jun 06 21:56:28.394119 2017] [proxy:error] [pid 6572] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/php/php7.1-fpm.sock (*) failed
[Tue Jun 06 21:56:28.394177 2017] [proxy_fcgi:error] [pid 6572] [client x.x.x.x:35356] AH01079: failed to make connection to backend: httpd-UDS

php7.1-fpm status seems ok, and the logfile is empty besides from restarts.

Could it be related to the fact that the customer sites all run with ssl, the froxlor and phpmyadmin not yet?

Where else can I look? Some help would be appreciated

Best, Michael