Running on Hetzner?

Hetzner server locked or Robot order stuck? We unstick it.

Hetzner is cheap and fast when it works, and unusually quiet when it does not. Most of the tickets we take on involve a server that stopped responding to pings, a fresh account flagged for identity verification, or a Cloud image build that silently fails cloud-init. We get the box back and write down how it is actually configured.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

hetzner-cloud.log

still broken

What it is

Hetzner at a glance

Hetzner is a German hosting company founded in 1997 by Martin Hetzner, best known for cheap dedicated servers out of Falkenstein and Nuremberg, and for Hetzner Cloud, a VM product that competes with DigitalOcean and Linode on price. There is also a second cluster in Helsinki and a newer one in Hillsboro, Oregon.

The product line splits across Hetzner Cloud (API-driven VMs, load balancers, volumes and private networks), Robot (dedicated server rentals, often at well below AWS equivalents), Storage Box (SMB/NFS backup space), and the Server Auction where used machines come up at a discount. There is an official Terraform provider, a Packer plugin, and a decent hcloud CLI, all of which cover the Cloud side.

Type
Cloud VMs, dedicated servers and storage
First released
1997 as a hosting company, 2017 Cloud product
License
Proprietary service, open-source API clients
Maintained by
Hetzner Online GmbH
Typically used for
Budget production hosting, dev and staging clusters, bare-metal workloads, backup targets

The honest version

Hetzner pros and cons

No technology is all upside. This is where Hetzner earns its place and where it tends to cause trouble.

Where Hetzner is strong

  • Price per core and per gigabyte is hard to beatA dedicated AX machine with 64 GB of RAM costs roughly what a mid-size AWS instance does, and the Cloud VMs undercut DigitalOcean and Linode on most sizes.
  • Dedicated hardware is a real option againRobot gives you actual bare metal with EPYC or Ryzen processors, so workloads that suffer on shared hypervisors can go back to running on their own silicon.
  • The Cloud API and Terraform provider are cleanhcloud is small, consistent, and covers almost everything the console does. Teams can describe the whole account in HCL without reverse-engineering anything.
  • Private networks and vSwitch work across productsYou can pin dedicated boxes and Cloud VMs onto the same private subnet, which is useful for keeping a database on bare metal while the web tier scales on Cloud.
  • Snapshots, backups and firewalls come with the CloudCore operational features are included rather than priced per feature, so a small project does not need a bill reconciliation meeting to understand its monthly spend.

Where Hetzner bites

  • Managed services are thin on the groundThere is no managed Postgres, no managed Redis, no S3-compatible object store in the Cloud product itself. You run what you need, or you rent Storage Box and build around its limits.
  • New accounts get verified by a humanSigning up a company for the first time routinely means an ID check, a bank reference, or a short written explanation. Expect a day or two before you can provision anything serious.
  • Outbound SMTP is blocked until you askPort 25 is closed on new accounts to protect reputation, and getting it opened is a support ticket rather than a toggle. Transactional mail breaks if nobody warns the team.
  • Support is written-only and in business hours CETThere is no phone line and no instant chat. Tickets get answered competently but in German working hours, so an outage at midnight Pacific time waits.
  • The Robot panel is older than most of your engineersDedicated servers are managed through a separate, older interface that does not share conventions with Cloud. People come in expecting a single console and find two.
  • North American capacity is one site deepHillsboro helps, but the regions and availability zones you can place things in across the US are still limited next to AWS or Google Cloud. Latency-sensitive customers may need a second provider.

Sound familiar?

Common Hetzner problems we fix

The Hetzner problems that bring people to us, and what you have once each one is fixed.

account under manual verification

Signup is stuck in verification

A company account that cannot provision anything because Hetzner wants a copy of a passport, a business registration document, or a short note about the intended workload.

Account verified, provisioning unlocked

ssh port 22: Connection refused

A production server has gone dark

Ping lost, SSH refused, and no obvious reason on the panel. Usually a kernel panic after an unattended upgrade, a filled disk, or a firewall change that locked the box out of itself.

Server reachable, cause documented

cloud-init: failed stage init-local

Cloud images will not build

A user-data script that works locally but breaks on Hetzner because of a YAML quote, a package that is not in the default repo, or a cloud-init module that silently skips.

Images building cleanly every time

outbound SMTP port 25 blocked

Transactional mail never leaves the server

An app that worked in staging fails in production because Hetzner leaves port 25 closed on fresh accounts, and nobody filed the ticket to open it or moved to a relay.

Mail delivery route sorted

Robot: server not reachable

A dedicated server has locked up

A kernel oops, a RAID controller giving out, or a power incident. Rescue system boot is possible but needs the right account access and a plan for the data on the disks.

Hardware investigated and recovered

snapshot: size exceeds limit

Snapshots and backups have run out of room

A project that outgrew the default snapshot slots, or a Storage Box that filled quietly because retention was never set. Older snapshots overwrite before anyone notices.

Backup rotation on a plan

no runbook, no owner

We inherited a Hetzner estate from a former developer

Panels under a personal email, an SSH key nobody still has, and a VPN between Cloud and Robot that is only documented on a laptop that was returned.

Account recovered, keys rotated

hcloud_server: unexpected status

Terraform runs hit transient states

An apply that errors because the hcloud provider sees initializing or migrating when it expects running, usually during a resize or an image change under load.

Terraform runs clean, retries safe

What we do

Hetzner help, from rescue to steady state

Pick up the phone for one dark server, or hand us the whole estate.

Rescue
A dead Cloud VM or a locked Robot box. We reach it through the rescue system, recover the data, and bring the service back up before writing the incident up.
Build-out
A new Hetzner project designed from scratch with Terraform, private networks, backups and firewall rules so you are not clicking around a panel at 2am.
Migrations
Moving workloads onto Hetzner from AWS, GCP or a dying colo, and moving them back off when the economics change. We plan DNS cutovers rather than hope for them.
Dedicated plus Cloud hybrid
Databases on Robot hardware wired into Cloud VMs through vSwitch, so you keep the price of bare metal without losing elastic web tiers.
Account recovery
Taking over Hetzner accounts stuck under a former contractor, rotating keys, moving billing, and auditing what is actually running.
Managed Tech
Patching, backup verification, snapshot rotation, cost reviews, and someone to page when a Falkenstein rack has a quiet night.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Hetzner alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Hetzner questions

Something else? Call+1 737 727 7327

Is Hetzner reliable enough for production?

For most teams, yes. Falkenstein and Nuremberg have been running for years with decent uptime, and the Cloud control plane is stable. Where it is weaker than AWS or GCP is in the number of regions and the breadth of managed services; if your product needs multi-region failover inside Europe you can do it, across continents you often cannot without a second provider.

Why can I not provision anything on a fresh Hetzner account?

New business accounts are routinely held for identity verification. Hetzner will ask for a company registration document, a passport scan or a short note about what you intend to run. It usually clears in a day or two once the paperwork is in, but trying to launch into production the same afternoon rarely works.

Why is our Hetzner server not sending mail?

Outbound SMTP on port 25 is closed by default on new accounts to protect the shared network reputation. Either file a ticket asking Hetzner to open it after showing them your use case, or send transactional mail through a relay such as Postmark or Mailgun instead of directly from the host.

Can you move us from AWS to Hetzner?

Yes, and the cost delta is often why people ask. The usual path is a Terraform build of the Hetzner side, a database replica streaming across in the background, a switchover window during a quiet traffic period, and the AWS side kept running in standby until the new estate has proved itself for a week or two.

Can you take over a Hetzner account from a previous developer?

Yes. We work with you on the ownership transfer, rotate every SSH key and API token, move billing to your card, and inventory which Robot and Cloud resources exist so none of them stop working silently during the handover.

How much does Hetzner help cost?

The estimate is free. Tell us what is running in Falkenstein, Helsinki or Hillsboro and what has gone wrong, and we send back a price before any changes are made.

Free estimate

Hetzner giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.