Hestia V1.4.1 Backend Issue on VPS

Ever since Hestia 1.4.1 upgrade, I’ve been having several issues. The website pages are loading successfully. The issue is with the backend!

Now, on my VPS server when I try " sudo apt update" I get the whole list of errors like;.

Err:1 http://mirrors.linode.com/ubuntu focal InRelease Temporary failure resolving ‘mirrors.linode.com
Err:2 https://mirror.mva-n.net/mariadb/repo/10.4/ubuntu focal InRelease Temporary failure resolving ‘mirror.mva-n.net
Err:3 https://apt.hestiacp.com focal InRelease Temporary failure resolving ‘apt.hestiacp.com
Err:4 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease Temporary failure resolving ‘ppa.launchpad.net
Err:5 https://nginx.org/packages/mainline/ubuntu focal InRelease Temporary failure resolving ‘nginx.org
Err:6 http://security.ubuntu.com/ubuntu focal-security InRelease Temporary failure resolving ‘security.ubuntu.com
Err:7 http://mirrors.linode.com/ubuntu focal-updates InRelease Temporary failure resolving ‘mirrors.linode.com
Err:8 http://mirrors.linode.com/ubuntu focal-backports InRelease Temporary failure resolving ‘mirrors.linode.com’ Reading package lists…
Done Building dependency tree Reading state information…
Done 15 packages can be upgraded. Run ‘apt list --upgradable’ to see them.
W: Failed to fetch http://mirrors.linode.com/ubuntu/dists/focal/InRelease Temporary failure resolving ‘mirrors.linode.com
W: Failed to fetch http://mirrors.linode.com/ubuntu/dists/focal-updates/InRelease Temporary failure resolving ‘mirrors.linode.com
W: Failed to fetch http://mirrors.linode.com/ubuntu/dists/focal-backports/InRelease Temporary failure resolving ‘mirrors.linode.com
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease Temporary failure resolving ‘security.ubuntu.com’ W: Failed to fetch https://apt.hestiacp.com/dists/focal/InRelease Temporary failure resolving ‘apt.hestiacp.com
W: Failed to fetch https://mirror.mva-n.net/mariadb/repo/10.4/ubuntu/dists/focal/InRelease Temporary failure resolving ‘mirror.mva-n.net
W: Failed to fetch https://nginx.org/packages/mainline/ubuntu/dists/focal/InRelease Temporary failure resolving ‘nginx.org
W: Failed to fetch http://ppa.launchpad.net/ondrej/php/ubuntu/dists/focal/InRelease Temporary failure resolving ‘ppa.launchpad.net
W: Some index files failed to download. They have been ignored, or old ones used instead.

Question: Do I have to do any Add/Edit/Change on Hestia Cp DNS settings?
DNS and everything used to work well ever since I started with Hestia V1.3.0

My DNS settings a fine on “Namecheap” pointing to “Linode.” And my DNS manager on Linode has never been touched after the first setup over 12 months ago.

Linode support says that the problem points to my server. setup on Hestia CP.

This has happened for first-time , any help and suggestion will be highly appreciated.

There are other issues also after Hestia Cp 1.4.1 update. But I want to start fixing this issue described above.

Again this issue appeared after Hestia 1.4.1 update.

Please help and assist.

Thanks

Try run ping google.com if it will fail

iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
apt update && apt upgrade

It will upgrade to 1.4.2 and fix the issue…

2 Likes

Hey Eris,

Thanks for your reply. I just quickly want to double-check with you to make sure I do the right thing!

#1: I tried ping as follows;

~$ ping google.com
ping: google.com: Temporary failure in name resolution

#2: In Hestia CP Server status for;
iptables showing as “0”. It is not running. Even after Ubuntu 20.04 LTS reboot.

#3: Do I run the command-line exactly as you provided?
What I mean is can I just cut/paste exactly as shown below?

~$ sudo iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
apt update && apt upgrade

Please let me know, and I will wait for your reply before going ahead.

Thanks

Sudo doesn’t work probally if you are logged in as an user you have 2 options:

  1. Login directly as root or use “su” and then provide a password.

Then execute:

iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
apt update && apt upgrade

This issue has been addressed in 1.4.2 and will fix the issue.

1 Like

Thanks, Eris,

Last night, I upgraded Hestia CP to 1.4.2 and it can now connect and update.

There are a couple of things I’ve noticed.

[1]. Under “server” it shows ipTables Service as 0 uptime. Even after Ubuntu 20.04 reboot, it has been that way. Do I need to use any commands?

[2]. With Hestia CP upgrade to 1.4.2, the “Log” has disappeared from “Top Blue Bar.” It used to be there on the left. Is there an issue with it?

[3]. I read that Hestia upgrade to 1.4.2 would fix the File-Manager. After the update, FileManager is still not visible.

Please do advise and assist.

Thank you.

  1. Iptables is not an service and does not return an uptime when we “ask”
  2. Log has been moved to /edit/user and extended to also show the login attempts
  3. Go to settings → Plugins and enable filemanager
1 Like

Thanks, Eris, I’ve learned something new about iPTables from you.

Everything is good now.