Connect Hetzner

Connect your Hetzner account to InfraNest to manage your cloud servers, DNS zones and SSL certificates in one place, without switching tools.

Overview

• Once connected, your Hetzner servers, DNS zones and certificates appear automatically in InfraNest.
• You can power servers on/off, reboot or rebuild them, manage firewalls, volumes, private networks and load balancers, and edit DNS records — all from InfraNest.
• This is for anyone running servers or domains on Hetzner who wants to manage them alongside the rest of their infrastructure.

Before you start

You'll need a Hetzner API token with Read & Write access. See Create a Hetzner API token for the steps.

NoteThe same token covers both your Hetzner cloud resources and your Hetzner DNS zones.

Connect Hetzner

1. Go to Integrations and open Hetzner.
2. Give the connection an Account label so you can recognise it later. This is optional.
3. Choose which features to use it for: Cloud, DNS and Certificates.
4. Paste your API token.
5. Leave Email me when this integration has problems ticked if you'd like a heads-up by email if something goes wrong.
6. Select Connect.

InfraNest checks the token and starts bringing in your servers and zones straight away.

What you get once it's connected

• Cloud servers — see and manage your servers: power on/off, reboot, rebuild, snapshots and backups, firewalls, volumes, private networks and load balancers.
• DNS — view and edit your DNS zones and records, and create or delete zones.
• SSL certificates — your Hetzner certificates appear in your certificate list.

Good to know

• Hetzner doesn't sell domains, so there's no domain-registration feature here.
• You can connect more than one Hetzner project — just add another connection.

Troubleshooting

• "Authentication failed" — the token may be wrong or removed. Generate a new Read & Write token in the Hetzner Cloud Console and reconnect.
• Nothing appears after connecting — make sure the token has Read & Write access (read-only can't manage resources), then run the sync again from the Hetzner page under Integrations.
• A one-off error in the activity log — a single failed call now and then is usually the provider having a bad moment, not a problem with your token. InfraNest checks before it acts on one: if the same token still works, nothing is switched off and nothing is emailed. You only hear from us once a problem repeats.
• "Server graphs" shows as paused — this means Hetzner refused the CPU and bandwidth figures twice in a row. Hetzner tokens have only two settings, Read and Read & Write, and both can read graphs — so there is no extra permission to switch on. Check the token still exists in the Hetzner Cloud Console, or paste in a new one, then select Re-enable on the Hetzner page under Integrations.