Does anyone have step-by-step instructions for Hetzner?
Today’s attempts with Debian 10 and Ubuntu 18.04.6 fail miserably and here in the forum one jumps from one thread to the next.
1.) Adjust DNS
2.) use https://gabizz.github.io/hestiacp-scriptline-generator
3.) read this Установка панели управления Hestia на Ubuntu 20.04 LTS — BlogMailns
It is frustrating. It does not work.
Best regards
Tom
I never had an issue with Hestia on Hetzner virtual machines. (Or any other for that matter.)
Create the VM, Pick a name for it, create A record in DNS, wait for it to propagate, and then follow HestiaCP install instructions from official doc.
Provide more information. Is there any particular error you are facing?
N.
Hello neven.
I don’t have virtual machines.
Either dependencies are missing. Then the keyring will not be accepted. Problems that are already mentioned here in the forum. The matching threads are blocked because the topic was partly 1 year ago, but is still relevant.
The “administrative instructions” state that it is currently being revised. The script that has worked in many other installations no longer works, even though it is the same system version.
At the end of the day you just want to get done 
You have a dedicated server? Collocation?
If it’s just a hosting acount, forget it. You can not install Hestia on a simple hosting accont. Don’t even try. 
Yes, a dedicated server and it’s not the first installation of Hestia. Only the first at Hetzner.
I think you should just prime your server with clean Linux install. (for example Ubuntu 20.04 LTS)
Hestia installs it’s dependencies, so there should be no problems.
We might be able to help you with your current server, but we need more info. Where it fails, what errors you are getting etc.
Hello neven,
these are basically fresh installs.
I just re-initialized the system in Robot. As soon as I have the first error messages, I can post them.
We test multiple times again Hetzner. Have installed Ubuntu 20.04 in the past multiple times with out issues on a dedicated server. We save a log in /root/hst_xxx/ folder with login information…
Hello eris,
I’ve read enough that it works for you.
It doesn’t work for me today.
I just download the script, install the keyring and run the installation script as specified in the link above.
So I have to ask you what you guys do differently?
T.
Hello nine,
I’ve been beyond the instructions for years. It is known and familiar to me. So far, this has always worked excellently. I don’t even use the instructions anymore.
T.
This should work fine it will make sure all the things are set up.
Provide us with more Infomation. I am not able to start a server +30 euro / month for a short period of time and invest time for testing it in this special use case…
Debug info what doesn’t work and so on. If I call my car mechanic and ask why my car is broken they will also ask what is wrong. Same here… Unless you want to pay me 100 euro/hr I am able to help without providing the information…
The first mistake at Hetzner is the package sources, although one can assume that everything is OK with a fresh installation. is.
Step 1: sudo apt update && apt upgrade -y
W: Failed to fetch http://en.archive.ubuntu.com/ubuntu/dists/bionic/InRelease Could not connect to en.archive.ubuntu.com:80 (141.30.62.24), connection timed out Could not connect to de.archive.ubuntu.com:80 (141.30.62.25), connection timed out Could not connect to en.archive.ubuntu.com:80 (141.30.62.22), connection timed out Could not connect to de.archive.ubuntu. com:80 (141.30.62.23), connection timed out Could not connect to en.archive.ubuntu.com:80 (141.30.62.26), connection timed out
W: Failed to fetch http://en.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Unable to connect to de.archive.ubuntu.com:http:
W: Failed to fetch http://en.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease Unable to connect to en.archive.ubuntu.com:http:
W: Some index files failed to download. They have been ignored, or old ones used instead.
So in the next step we adjust DNS and source.list
T
This is not an issue with Hestia but with the image from Hetzner in this situation ask support from Hetzner… And not us…
Maybe your resolve.conf is wrong and doesn’t work propperly. If you have modified it change it back to default
eris,
the resolve.conf is untouched.
There is a thread about this in the forum:
Try it with out any changes to the DNS. A default server should always be able to download via apt
Your problem is on a network level.
Try pinging 141.30.62.24. If it works, change nameservers in resolve.conf to 1.1.1.1 and 1.0.0.1 and try again. Else, contact Hetzner support.
My experience with Hetzner is excellent. I havent had a second downtime in 3 years, and 0 problems.
I first adjusted the source.list.
Instead of the standard sources from Hetzner, I now use those from 1&1. So far no problems. Also “sudo apt update && and apt upgrade ran without problems.”
Happy too soon:
Updating currently installed packages, please wait… W: GPG error: Index of /ondrej/apache2/ubuntu bionic InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 4F4EA0AAE5267A6C
E: The repository ‘Index of /ondrej/apache2/ubuntu bionic InRelease’ is not signed.
W: GPG error: https://apt.hestiacp.com bionic InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A189E93654F0B0E5
E: The repository ‘https://apt.hestiacp.com bionic InRelease’ is not signed.
W: GPG error: Index of /ondrej/php/ubuntu bionic InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 4F4EA0AAE5267A6C
E: The repository ‘Index of /ondrej/php/ubuntu bionic InRelease’ is not signed.
The installer is now downloading and installing all required packages.
NOTE: This process may take 10 to 15 minutes to complete, please wait… /
Error: apt-get install failed
T .
There was a thread from eris about this
rm /usr/share/keyrings/hestia-keyring.gpg
mkdir /root/.gnupg/
gpg --no-default-keyring --keyring /usr/share/keyrings/hestia-keyring.gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys A189E93654F0B0E5
Well, you need to install keys for the sources. But this kind of support is beyond Hestia, and you might need to pay for help.
Best advice is still to call Hetzner supprot. They have likely screwed up something with their install images.