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
Running on Hetzner?
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.
What it is
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.
The honest version
No technology is all upside. This is where Hetzner earns its place and where it tends to cause trouble.
Sound familiar?
The Hetzner problems that bring people to us, and what you have once each one is fixed.
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
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
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
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
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
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
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
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
Pick up the phone for one dark server, or hand us the whole estate.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
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.
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.
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.
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.
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.
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
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: