Upgrade from 1.2.x to 1.4.2 - Error on some customer pages (503)

    Hello,


    finally we updated our imscp from the 1.2.x branch to 1.4.2 and everything worked well as far as i can say. Services are running and ssl for panel, services and pages, too.
    But we have an 503 error on all customer pages, but not at one customer page. On one page everything works as expected and all other pages are failing with 503 service unavailable.


    It seems that the fcgi process is searching for the php5-fpm process but after update its the php5.6-fpm process.

    Code
    1. [Mon Apr 10 20:00:28.158315 2017] [proxy:error] [pid 12055:tid 124158032029440] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/run/php5-fpm-forum.domain.tld.sock (*) failed
    2. [Mon Apr 10 20:00:28.158353 2017] [proxy_fcgi:error] [pid 12055:tid 124158032029440] [client 37.24.253.20:50886] AH01079: failed to make connection to backend: httpd-UDS, referer: https://forum.domain.tld/


    This is the error, which is in each log file from the failing customer pages. So how can we fix this problem? Don't know how and we already tried to reconfigure imscp or restart the processes.


    Hope anyone could give a short help to fix this issue. :)

    Reporting rules - Reminder


    If you cannot figure out alone, give us access to your server.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support

    Sorry for not posting the missing information.


    Distro: Debian Jessie 8.3
    I-MSCP Version: old -> 1.2.x branch | after update -> 1.4.2
    Server Implementation: PHP-FPM
    PHP Version: PHP 5.6


    Error log from one customer page:

    Code
    1. [Mon Apr 10 19:21:13.487158 2017] [proxy:error] [pid 26738:tid 115895847712512] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/run/php5-fpm-cyrex.org.sock (*) failed
    2. [Mon Apr 10 19:21:13.487199 2017] [proxy_fcgi:error] [pid 26738:tid 115895847712512] [client 84.132.70.28:56858] AH01079: failed to make connection to backend: httpd-UDS, referer: https://www.facebook.com/
    3. [Mon Apr 10 19:21:13.579538 2017] [proxy:error] [pid 26739:tid 115895875680000] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/run/php5-fpm-cyrex.org.sock (*) failed
    4. [Mon Apr 10 19:21:13.579553 2017] [proxy_fcgi:error] [pid 26739:tid 115895875680000] [client 84.132.70.28:56859] AH01079: failed to make connection to backend: httpd-UDS, referer: https://cyrex.org/Serverarbeiten
    5. [Mon Apr 10 19:53:11.627136 2017] [proxy:error] [pid 12055:tid 124157925066496] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/run/php5-fpm-cyrex.org.sock (*) failed
    6. [Mon Apr 10 19:53:11.627162 2017] [proxy_fcgi:error] [pid 12055:tid 124157925066496] [client 37.24.253.20:50478] AH01079: failed to make connection to backend: httpd-UDS
    7. [Mon Apr 10 19:53:11.668736 2017] [proxy:error] [pid 12055:tid 124157952243456] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/run/php5-fpm-cyrex.org.sock (*) failed
    8. [Mon Apr 10 19:53:11.668752 2017] [proxy_fcgi:error] [pid 12055:tid 124157952243456] [client 37.24.253.20:50479] AH01079: failed to make connection to backend: httpd-UDS
    9. [Mon Apr 10 19:53:19.375188 2017] [proxy:error] [pid 12054:tid 124157845284608] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/run/php/php5.6-fpm-cyrex.org.sock (*) failed
    10. [Mon Apr 10 19:53:19.375216 2017] [proxy_fcgi:error] [pid 12054:tid 124157845284608] [client 37.24.253.20:50525] AH01079: failed to make connection to backend: httpd-UDS


    I will send you the login details for our server via conversation, so you could watch into this issue.


    Thanks very much.

    @freedom


    The problem is due to the fact that you use certbot (distribution package) manually. You have generated many SSL vhosts that are not managed by i-MSCP and therefore, PHP socket paths were not updated during upgrade.


    I've removed all LE SSL vhosts and I've re-run the i-MSCP installer. You need now instruct Certbot to regenerate all SSL vhosts. However, bear in mind that those vhosts are not managed by i-MSCP and therefore, they won't be updated by i-MSCP. This is also valable for the PhpSwitcher plugin. If you change the PHP version for one of your site, the LE ssl vhost will not be updated, leading to unexpected socket path.


    If you want a proper management of your Let's Encrypt SSL vhosts, best is to use our LetsEncrypt plugin.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support

    @Nuxwin


    Thanks for resolving the problem. Would the Letsencrypt Plugin for i-MSCP solve the problem forever or would this create the same errors?
    If this will work with the plugin, i will talk with some of our teammembers so we can buy and implement the plugin.


    Until now we used certbot manually and renew the certs from there.


    Thanks for your help! :)

    @freedom


    Our Let's Encrypt plugin hooks into i-MSCP core and that is a big difference. In your case, the ssl vhosts are static because these are no known by i-MSCP while in the case of our plugin, they are dynamic and are updated when needed. You wouldn't have such problem with our plugin.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support
    Quote from freedom

    As already written in the pm, we will come back to you soon and buy the plugin. Thanks for your help.

    You're welcome ;)


    Thread closed.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support