Hello, I just updated my server from ubuntu 20.04 to 22.04 and all my websites are running normally but I can’t access the hestiacp admin panel (Internal Server Error)
Here’s the log via /var/log/hestia/nginx-error.log
2022/08/08 15:49:30 [error] 4171217#0: *39877 FastCGI sent in stderr: "PHP message: PHP Warning: Undefined array key "look" in /usr/local/hestia/web/templates/pages/list_backup.html on line 97" while reading upstream, client: 100.98.55.95, server: _, request: "GET /list/backup/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/hestia-php.sock:", host: "ruka.moe.team:6969", referrer: "https://ruka.moe.team:6969/list/user/"
2022/08/09 02:45:45 [crit] 740#0: *1 connect() to unix:/var/run/hestia-php.sock failed (2: No such file or directory) while connecting to upstream, client: 66.96.230.119, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/hestia-php.sock:", host: "ruka.moe.team:6969"
The SMTP function has also become error so that I can’t receive and send emails
Hard to give advice without being able to get inside the machine and poke around. As general advice, have you rebooted since the upgrade? A reboot sometimes clears up mysterious errors like these.
Second thought, I think on upgrading from 20.x to 22.x you might have got a later version of exim which needs a different config file. You can see the different versions here
“apt policy exim4” will tell you what you have installed
I have no experience with this kind of thing as this is the first time I’ve had an error like this so if you have a workaround for this I would really appreciate it
Here’s the output after run “apt policy exim4” command
OK, well you’ve definitely got the later version of exim, which needs the later config. And I see from the Hestia Install file, that the only difference between the two installs is the single config file.
if [ "$exim" = 'yes' ]; then
echo "[ * ] Configuring Exim mail server..."
gpasswd -a Debian-exim mail > /dev/null 2>&1
if [ "$release" = "22.04" ]; then
# Jammyy uses Exim 4.95 instead but config works with Exim4.94
cp -f $HESTIA_INSTALL_DIR/exim/exim4.conf.4.94.template /etc/exim4/exim4.conf.template
else
cp -f $HESTIA_INSTALL_DIR/exim/exim4.conf.template /etc/exim4/
fi
So I’d suggest taking a backup of your existing exim config file and replacing it with the new version. Are you comfortable doing that yourself?
I’m not saying this will definitely fix the problem, but it seems like something that needs to be done anyway.
I’d do something like this, but don’t just copy what I’m suggesting here, without understanding it.
cd /etc/exim4/
cp exim4.conf.template exim4.conf.backup220809
cp /usr/local/hestia/install/deb/exim/exim4.conf.4.94.template ./exim4.conf.template
systemctl restart exim4
systemctl status exim4
when you upgrade your os, you also need to adjust the apt config files to your new os codename in /etc/apt/apt.d/. Do this, then apt update && apt --reinstall hestia-php and it should work.
The output after run apt --reinstall hestia-php command :
root@ruka:/etc/apt/apt.conf.d# apt-get --reinstall install hestia-php
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
golang-1.18-go golang-1.18-src golang-1.19-doc golang-doc python3-libxml2
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 2 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for hestia-php:amd64