No access to HestiaCP backend

All HestiaCP are working fine (ssh, web, dns, mail…) but I can’t access to backend from https://host.domain.tld:8083/login/.

I don’t updated to Hestia v1.2.0, so it must be v1.1.2 (I don’t know where to watch it using SSH) running on Debian 9.

I tested “v-restart-web-backend”, “v-restart-web” and “v-restart-system” and none of them solved it.

What could be happening? Which log can I look at to find out?

Please check /var/log/hestia/nginx-error.log

I think it is a issue in the configuration of Nginx

Thank you for your answer. This is the message error that keeps recurring:

2020/07/09 23:23:25 [crit] 1108#0: *21 connect() to unix:/var/run/hestia-php.sock failed (2: No such file or directory) while connecting to upstream, client: "MyClientIP", server: _, request: "GET /login/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/hestia-php.sock:", host: "host.domain.tld:8083"

There is something wrong with you “hestia” php.

Please run:

systemctl status hestia

And check what the error is

You may also try to run

systemctl restart hestia

Maybe it gives some error messages

systemctl status hestia
● hestia.service - LSB: starts the hestia control panel
   Loaded: loaded (/etc/init.d/hestia; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2020-07-09 18:40:40 CEST; 4h 52min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1066 ExecStart=/etc/init.d/hestia start (code=exited, status=127)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/hestia.service
           ├─1104 nginx: master process /usr/local/hestia/nginx/sbin/hestia-nginx
           └─1108 nginx: worker process

Jul 09 18:40:40 systemd[1]: Starting LSB: starts the hestia control panel...
Jul 09 18:40:40 hestia[1066]: Starting hestia-nginx: hestia-nginx.
Jul 09 18:40:40 hestia[1066]: Starting hestia-php: hestia-php/usr/local/hestia/php/sbin/hestia-php: error while loading shared libraries: libzip
Jul 09 18:40:40 systemd[1]: hestia.service: Control process exited, code=exited status=127
Jul 09 18:40:40 systemd[1]: Failed to start LSB: starts the hestia control panel.
Jul 09 18:40:40 systemd[1]: hestia.service: Unit entered failed state.
Jul 09 18:40:40 systemd[1]: hestia.service: Failed with result 'exit-code'.

apt-get install libzip4

If doesn’t exist try libzip5

:slight_smile:

Jul 09 23:35:02 my.host.com hestia[18814]: Starting hestia-php: hestia-php/usr/local/hestia/php/sbin/hestia-php: error while loading shared libraries: libzi

2 Likes

Solved!!!

apt-get install libzip4 && systemctl restart hestia

Why didn’t that package exist?

Thank you very much!

For me it was fixed with
apt-get install libzip5 && systemctl restart hestia

i have the same error, but non of above worked for me

~ # apt-get install libzip5 && systemctl restart hestia
Reading package lists… Done
Building dependency tree
Reading state information… Done
Package libzip5 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package ‘libzip5’ has no installation candidate

~ # apt-get install libzip4 && systemctl restart hestia
Reading package lists… Done
Building dependency tree
Reading state information… Done
libzip4 is already the newest version (1.5.1-4+0~20190318173200.9+buster~1.gbp333132).
libzip4 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

debian 10

systemctl status hestia
● hestia.service - LSB: starts the hestia control panel
Loaded: loaded (/etc/init.d/hestia; generated)
Active: active (running) since Sun 2020-07-19 21:14:57 BST; 4min 45s ago
Docs: man:systemd-sysv-generator(8)
Process: 5769 ExecStart=/etc/init.d/hestia start (code=exited, status=0/SUCCESS)
Tasks: 3 (limit: 4915)
Memory: 11.9M
CGroup: /system.slice/hestia.service
├─5775 nginx: master process /usr/local/hestia/nginx/sbin/hestia-nginx
├─5776 nginx: worker process
└─5778 php-fpm: master process (/usr/local/hestia/php/etc/php-fpm.conf)

Jul 19 21:15:14 server.lislehost.com sudo[6118]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 19 21:15:14 server.lislehost.com sudo[6118]: pam_unix(sudo:session): session closed for user root
Jul 19 21:15:14 server.lislehost.com sudo[6124]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 19 21:15:14 server.lislehost.com sudo[6124]: pam_unix(sudo:session): session closed for user root
Jul 19 21:15:16 server.lislehost.com sudo[6146]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 19 21:15:16 server.lislehost.com sudo[6146]: pam_unix(sudo:session): session closed for user root
Jul 19 21:15:16 server.lislehost.com sudo[6149]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 19 21:15:16 server.lislehost.com sudo[6149]: pam_unix(sudo:session): session closed for user root
Jul 19 21:15:16 server.lislehost.com sudo[6155]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 19 21:15:16 server.lislehost.com sudo[6155]: pam_unix(sudo:session): session closed for user root

libzip4 solved my problem, not libzip5. Have you tried to install it? But your hestia service don’t has the error:

error while loading shared libraries: libzip

Depending on OS lib zip 4 or 5 is required and would solve the is.

With out the correct information we can’t help… But everything seems to be working fine

i see this in

[> Sun Jul 19 21:30:08.419111 2020] [ssl:warn] [pid 1631] AH01909: 176.9.39.57:443:0 server certificate does NOT include an ID which matches the server name

[Sun Jul 19 21:30:08.423635 2020] [mpm_prefork:notice] [pid 1631] AH00163: Apache/2.4.43 (Debian) mod_fcgid/2.3.9 mpm-itk/2.4.7-04 OpenSSL/1.1.1g configured – resuming normal operations

[Sun Jul 19 21:30:08.423651 2020] [core:notice] [pid 1631] AH00094: Command line: ‘/usr/sbin/apache2’

i have done

v-add-letsencrypt-host

It is complaining that mpm_prefork causing the issue. This issue is not related to “Hestia Nginx” package or Control panel it self. Requesting an SSL certificate for the control pannel wil not resolve the issue…

you probably locked yourself out with the CSF experiments then… from the status you posted above, your hestia is up and running.

1 Like

i have disabled csf and still the same, if was csf i would not be able to access server at all, but i can view sites running on server it and ssh to iti get internal error 500 when trying to view hestacp.

As any changes errors in php will result in an error 500. I suggest reinstalling Hestia package first via

apt update && apt install --reinstall hestia

Or check in /etc/hestia/nginx-error.log for any errors

2 Likes

shows no errors

will try reinstall

reinstall worked, not sure the issue was though!

Then there was most likely a issue with a php error. Not sure why…