Unable to change backend template on freshly installed Hestia 1.4.2

Hello guys,
i’m here looking for help. My needs it’s to use the PHP 5.6 for hosting some old php websites.

My host it’s a vps with Debian 10.9 and HestiaCP v1.4.2 (fresh installed).

Actually i’m facing 2 different errors:

  1. Trying to load a info.php file in folder, lands to an error:
    [Mon Jun 14 17:36:42.426293 2021] [proxy:error] [pid 5807:tid 139781410141952] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/php/php7.4-fpm-cms.xxxxx.top.sock (*) failed
    [Mon Jun 14 17:36:42.426336 2021] [proxy_fcgi:error] [pid 5807:tid 139781410141952] [client] AH01079: failed to make connection to backend: httpd-UDS

Anyway, php7.4 fpm seems installed correctly and working:

php7.4-fpm.service - The PHP 7.4 FastCGI Process Manager
   Loaded: loaded (/lib/systemd/system/php7.4-fpm.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2021-06-14 11:31:39 CEST; 6h ago
     Docs: man:php-fpm7.4(8)
  Process: 3377 ExecReload=/bin/kill -USR2 $MAINPID (code=exited, status=0/SUCCESS)
 Main PID: 29624 (php-fpm7.4)
   Status: "Processes active: 0, idle: 0, Requests: 5, slow: 0, Traffic: 0req/sec"
    Tasks: 1 (limit: 1167)
   Memory: 29.1M
   CGroup: /system.slice/php7.4-fpm.service
           └─29624 php-fpm: master process (/etc/php/7.4/fpm/php-fpm.conf)
  1. I’m creating a new host and then trying to change the backend template, from the “default” to the “PHP-5_6”.
    What happens it’s that once saved, it seems everything ok, but the backend in the UI remains as “default” value.

When trying to change it manually with the command:

v-change-web-domain-backend-tpl USER DOMAIN TEMPLATE [RESTART]

The result it’s:

/usr/local/hestia/bin/v-change-web-domain-backend-tpl: line 96: shell_list: command not found

do you have any advice on what to check?

Thank you very much!

What is the name of the user? domain.com

Hello Eris, Thank you for your reply.

You’ve right, the username it’s the same as the domain name. So it’s the same bug that you’ve mentioned.

I’ll try to dig into it!

Best way is to change the username to something else then domain.com removal the . should be fine.


Should be enough

Thank you very much, i’ll try asap and i will let you know!

Thank Again eris