HETZNER + HestiaCP Version 1.5.8

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.

We start here: Getting Started — Hestia Control Panel documentation

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.

  1. 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…

  2. 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…

3 Likes

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

1 Like

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.

3 Likes

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. :slight_smile:
Best advice is still to call Hetzner supprot. They have likely screwed up something with their install images.

All those keys are hosted ubuntu key server. Probally you still have issues reaching them…

I can confirm that

gpg --no-default-keyring --keyring /usr/share/keyrings/hestia-keyring.gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys A189E93654F0B0E5
gpg: keybox ‘/usr/share/keyrings/hestia-keyring.gpg’ created
gpg: keyserver receive failed: Connection timed out

T.

I just tried everything from one of my servers on Hetzner. Everything works fine, so it’s not a global problem.

Exactly… and then, after more than 20 installations, you’re left wondering why it doesn’t work with a hoster :slight_smile:

I’m off work for today. Set the default image to 20.04. Let’s see if that works better.

T

@eris and neven

I found the problem.
There is a rule in the Hetzner firewall template “Webserver”:

“Name: tcp established, ports: 32768-65535 protocol: tcp, flags: ack, action: accept”.

If you take them into your own rule set, the installation will work. Whereby it is then the first servers that need this rule.

Why Hetzner goes his own way will remain a mystery.

T

Sounds like you used/enabled the hetzner firewall and forgot to add the outgoing tcp connections, you’ll find more about it in their docs: https://docs.hetzner.com/robot/dedicated-server/firewall/

But indeed, not a hestia issue at all :slight_smile:.

@Raphael

This is an incoming rule. Outgoing are not set at the time.

You’re right then, in the end it’s not a Hestia problem :wink:

T.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.