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 
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 .
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 
T.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.