i haven’t changed anything with the control panel but now i am getting errors saying the site can not be reached when trying to access the contral panel. The web server is still running as sites are still loading but it get refused to connect when trying to access the I.P. and or control panel.
How to i regain access?
In addition to this i had an email last night saying that the hestia update had failed
Error: hestia update failed
Error: hestia-nginx update failed
Error: hestia-php update failed
systemctl status hestia
● hestia.service - LSB: starts the hestia control panel
Loaded: loaded (/etc/init.d/hestia; generated)
Active: failed (Result: exit-code) since Thu 2025-02-20 02:40:36 UTC; 6h ago
Docs: man:systemd-sysv-generator(8)
Process: 931529 ExecStart=/etc/init.d/hestia start (code=exited, status=1/FAILURE)
Feb 20 02:40:32 domainnameretracted.com systemd[1]: Starting LSB: starts the hestia control panel…
Feb 20 02:40:36 domainnameretracted.com hestia[931529]: * Starting hestia-nginx hestia-nginx
Feb 20 02:40:36 domainnameretracted.com hestia[931641]: nginx: [emerg] getpwnam(“hestiaweb”) failed in /usr/local/hestia/nginx/conf/nginx.conf:2
Feb 20 02:40:36 domainnameretracted.com systemd[1]: hestia.service: Control process exited, code=exited, status=1/FAILURE
Feb 20 02:40:36 domainnameretracted.com systemd[1]: hestia.service: Failed with result ‘exit-code’.
Feb 20 02:40:36 domainnameretracted.com systemd[1]: Failed to start LSB: starts the hestia control panel.
apt remove hestia-nginx hestia-php
apt install hestia --reinstall
apt install hestia-nginx hestia-php
Is this safe to run on a live server? There are sites hosted on it?
Yes sites hosted on the server are not affected
I ran those commads on the second command i got
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
hestia : Depends: bubblewrap but it is not installable
E: Unable to correct problems, you have held broken packages.
The running the third command gave me the same output as above
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following package was automatically installed and is no longer required:
libpmem1
Use ‘apt autoremove’ to remove it.
The following NEW packages will be installed:
hestia-nginx hestia-php
0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded.
Need to get 0 B/66.6 MB of archives.
After this operation, 0 B of additional disk space will be used.
Selecting previously unselected package hestia-nginx.
(Reading database … 102654 files and directories currently installed.)
Preparing to unpack …/hestia-nginx_1.27.3_amd64.deb …
Unpacking hestia-nginx (1.27.3) …
Selecting previously unselected package hestia-php.
Preparing to unpack …/hestia-php_8.3.16_amd64.deb …
Unpacking hestia-php (8.3.16) …
Setting up hestia-php (8.3.16) …
dpkg: error processing package hestia-php (–configure):
installed hestia-php package post-installation script subprocess returned error exit status 5
Setting up hestia-nginx (1.27.3) …
Job for hestia.service failed because the control process exited with error code.
See “systemctl status hestia.service” and “journalctl -xe” for details.
invoke-rc.d: initscript hestia, action “start” failed.
● hestia.service - LSB: starts the hestia control panel
Loaded: loaded (/etc/init.d/hestia; generated)
Active: failed (Result: exit-code) since Thu 2025-02-20 09:50:51 UTC; 27ms ago
Docs: man:systemd-sysv-generator(8)
Process: 993912 ExecStart=/etc/init.d/hestia start (code=exited, status=1/FAILURE)
Feb 20 09:50:46 domainnameretracted.com systemd[1]: Starting LSB: starts the hestia control panel…
Feb 20 09:50:46 domainnameretracted.comhestia[993912]: * Starting hestia-nginx hestia-nginx
Feb 20 09:50:51 domainnameretracted.com hestia[993919]: nginx: [emerg] getpwnam(“hestiaweb”) failed in /usr/local/hestia/nginx/conf/nginx.conf:2
Feb 20 09:50:51 domainnameretracted.com systemd[1]: hestia.service: Control process exited, code=exited, status=1/FAILURE
Feb 20 09:50:51 domainnameretracted.com systemd[1]: hestia.service: Failed with result ‘exit-code’.
Feb 20 09:50:51 domainnameretracted.com systemd[1]: Failed to start LSB: starts the hestia control panel.
/var/lib/dpkg/info/hestia-nginx.postinst: line 15: syshealth_adapt_hestia_nginx_listen_ports: command not found
dpkg: error processing package hestia-nginx (–configure):
installed hestia-nginx package post-installation script subprocess returned error exit status 127
Processing triggers for systemd (245.4-4ubuntu3.23) …
Errors were encountered while processing:
hestia-php
hestia-nginx
E: Sub-process /usr/bin/dpkg returned an error code (1)
apt update
apt install bubblewrap
This seems to get an error too -
Package bubblewrap 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 ‘bubblewrap’ has no installation candidate
What OS are you using?
Linux Ubuntu 18.04 currently
Actually apologies it’s Ubuntu 20.04.6 LTS
We have never released 1.9 for 18.04 it is EOL for almost 2 years…
So why it is requiring the new hestia web user…
https://launchpad.net/ubuntu/+source/bubblewrap
Is still supported…
Yeah sorry the hosting company says one thing on their internal pages and the server actually reports something else when i login to the server it says
Ubuntu 20.04.6 LTS
20.04 should be fine.
Why is it not downloading the package then …
Before doing the bubblewrap command the previous command had this at the end
W: GPG error: Index of /packages/mainline/ubuntu/ focal InRelease: The following signatures were invalid: EXPKEYSIG ABF5BD827BD9BF62 nginx signing key [email protected]
E: The repository ‘Index of /packages/mainline/ubuntu/ focal InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
curl -s https://nginx.org/keys/nginx_signing.key | sudo gpg --dearmor > /usr/share/keyrings/nginx-keyring.gpg
then run apt update again
Similar but slightly different after running apt update i get this error now
E: Failed to fetch https://uyuni.cwcs.co.uk:443/rhn/manager/download/r1soft-ubuntu-2004-amd64/Packages 403 403 [IP: 46.17.89.52 443]
E: Failed to fetch https://uyuni.cwcs.co.uk:443/rhn/manager/download/zabbix50-ubuntu-2004-amd64/Packages 403 403 [IP: 46.17.89.52 443]
E: Failed to fetch https://uyuni.cwcs.co.uk:443/rhn/manager/download/ubuntu-2004-amd64-main-uyuni/Packages 403 403 [IP: 46.17.89.52 443]
E: Failed to fetch https://uyuni.cwcs.co.uk:443/rhn/manager/download/ubuntu-20.04-pool-amd64-uyuni/Packages 403 403 [IP: 46.17.89.52 443]
E: Failed to fetch https://uyuni.cwcs.co.uk:443/rhn/manager/download/ubuntu-2004-amd64-uyuni-client/Packages 403 403 [IP: 46.17.89.52 443]
E: Failed to fetch https://uyuni.cwcs.co.uk:443/rhn/manager/download/ubuntu-2004-amd64-universe-uyuni/Packages 403 403 [IP: 46.17.89.52 443]
E: Failed to fetch https://uyuni.cwcs.co.uk:443/rhn/manager/download/ubuntu-2004-amd64-main-updates-uyuni/Packages 403 403 [IP: 46.17.89.52 443]
E: Failed to fetch https://uyuni.cwcs.co.uk:443/rhn/manager/download/ubuntu-2004-amd64-main-security-uyuni/Packages 403 403 [IP: 46.17.89.52 443]
E: Failed to fetch https://uyuni.cwcs.co.uk:443/rhn/manager/download/ubuntu-2004-amd64-universe-updates-uyuni/Packages 403 403 [IP: 46.17.89.52 443]
E: Failed to fetch https://uyuni.cwcs.co.uk:443/rhn/manager/download/ubuntu-2004-amd64-universe-security-uyuni/Packages 403 403 [IP: 46.17.89.52 443]
E: Failed to fetch https://uyuni.cwcs.co.uk:443/rhn/manager/download/ubuntu-2004-amd64-universe-backports-uyuni/Packages 403 403 [IP: 46.17.89.52 443]
E: Some index files failed to download. They have been ignored, or old ones used instead.
The bubblewrap install still gets the same error