Jump to content
Froxlor Forum

lanbo

Members
  • Posts

    27
  • Joined

  • Last visited

Posts posted by lanbo

  1. @headtrick, @Keon, did you solve it?

    I'm stuck at the exactly same step after upgrading php version while I was on php-fpm.

    /run/php/php7.2-fpm.sock is not found.

    But this is not the file that should be used anyway I guess...

    This is my froxlor config file:

    # 10_froxlor_ipandport_xxx.xxx.xxx.xxx.80.conf
    # Created 29.09.2018 11:22
    # Do NOT manually edit this file, all changes will be deleted after the next domain change at the panel.
    
    <VirtualHost xxx.xxx.xxx.xxx:80>
    DocumentRoot "/var/www/html/"
     ServerName xxxx.xxxx.com
      <FilesMatch \.()$>
      SetHandler proxy:unix:/var/lib/apache2/fastcgi/1-froxlor.panel-xxx.xxx.com-php-fpm.socket|fcgi://localhost
      </FilesMatch>
    </VirtualHost>

    It's strange why this other file is not being created and therefore not being picked up.

    This are the logs with LogLevel debug:

    [Sat Sep 29 11:50:23.986229 2018] [proxy:debug] [pid 27113:tid 140463228737280] proxy_util.c(2252): [client xxx.xxx.189.83:53264] AH02545: fcgi: has determined UDS as /run/php/php7.2-fpm.sock

    So I guess is something related to proxy_fcgi. I'm stuck...

    I made some progress:

      <FilesMatch \.()$>
      SetHandler proxy:unix:/var/lib/apache2/fastcgi/1-froxlor.panel-xxx.xxxxxx.com-php-fpm.socket|fcgi://localhost
      </FilesMatch>

    should be:

    <FilesMatch \.php$>...</FilesMatch>

    Strange. Why is it not correctly generated?

    However, even if I try to fix it manually, then apache still fails because the socket file has not been generated anyway:

    [Sat Sep 29 12:06:06.752157 2018] [proxy:error] [pid 28900:tid 140013299574528] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/lib/apache2/fastcgi/1-froxlor.panel-xxx.xxxxx.com-php-fpm.socket (*) failed
    [Sat Sep 29 12:06:06.752228 2018] [proxy_fcgi:error] [pid 28900:tid 140013299574528] [client 95.120.189.83:54668] AH01079: failed to make connection to backend: httpd-UDS

    What did you end up doing guys?

    Thanks

  2. @headtrick, @Keon, did you solve it?

    I'm stuck at the exactly same step after upgrading php version while I was on php-fpm.

     

    /run/php/php7.2-fpm.sock is not found.

    But this is not the file that should be used anyway I guess...

    This is my froxlor config file:

    # 10_froxlor_ipandport_xxx.xxx.xxx.xxx.80.conf
    # Created 29.09.2018 11:22
    # Do NOT manually edit this file, all changes will be deleted after the next domain change at the panel.
    
    <VirtualHost xxx.xxx.xxx.xxx:80>
    DocumentRoot "/var/www/html/"
     ServerName xxxx.xxxx.com
      <FilesMatch \.()$>
      SetHandler proxy:unix:/var/lib/apache2/fastcgi/1-froxlor.panel-xxx.xxx.com-php-fpm.socket|fcgi://localhost
      </FilesMatch>
    </VirtualHost>

    It's strange why this other file is not being created and therefore not being picked up.

    This are the logs with LogLevel debug:

    [Sat Sep 29 11:50:23.986229 2018] [proxy:debug] [pid 27113:tid 140463228737280] proxy_util.c(2252): [client xxx.xxx.189.83:53264] AH02545: fcgi: has determined UDS as /run/php/php7.2-fpm.sock

    Si I guess is something related to proxy_fcgi. I'm stuck...

     

    I made some progress:

      <FilesMatch \.()$>
      SetHandler proxy:unix:/var/lib/apache2/fastcgi/1-froxlor.panel-xxx.xxxxxx.com-php-fpm.socket|fcgi://localhost
      </FilesMatch>

    should be:

    <FilesMatch \.php$>...</FilesMatch>

    Strange. Why is it not correctly generated?

    Then apache al least tries to pick the correct one (even if it fails):

     

    [Sat Sep 29 12:06:06.752157 2018] [proxy:error] [pid 28900:tid 140013299574528] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/lib/apache2/fastcgi/1-froxlor.panel-xxx.xxxxx.com-php-fpm.socket (*) failed
    [Sat Sep 29 12:06:06.752228 2018] [proxy_fcgi:error] [pid 28900:tid 140013299574528] [client 95.120.189.83:54668] AH01079: failed to make connection to backend: httpd-UDS

     

    What did you end up doing guys?

    Thanks

×
×
  • Create New...