Hetzner SSL Certificate Not Working: Fix It Step by Step

Hetzner SSL Certificate Not Working: Fix It Step by Step

The fastest way to fix this is to decide which of two problems you have. Either the certificate was never issued, or it was issued but your server is not serving it. The first case is almost always a domain validation problem. The second case is a hostname, binding, or chain problem. They look identical in a browser, but the fixes are completely different, so make this call first.

A useful clue on Hetzner managed hosting: if you open https:// on your domain and only the konsoleH login page appears, the SSL account for that domain has not been installed at all. That is an installation problem, not a serving problem.

Identify Your Hetzner Setup First

The fix depends on where the certificate lives, so check this before changing anything.

Where your site runs Where certificates are managed Renewal
Managed hosting (Web Hosting, Managed Server) SSL Manager in konsoleH Basic and Let's Encrypt renew automatically; Business is manual
Cloud servers using Hetzner-managed certificates Hetzner Console, under Security then Certificates Hetzner renews managed certificates; uploaded ones are your responsibility
VPS or Cloud server where you installed the certificate yourself Your web server configuration You control renewal

If you are on managed hosting, the SSL Manager in konsoleH is where certificates for the domains in your hosting account are handled, and third-party certificates can be imported there. Note that Hetzner's Basic and Let's Encrypt certificates work only with Hetzner products and cannot be used with other hosting providers.

Issuance Failed: Fixing Certificates in konsoleH

If the certificate was never issued, domain authentication is the usual blocker. Work through these checks in order.

Confirm the Domain and Subdomain Exist

To apply for a free certificate in konsoleH, the domain must be associated with an active hosting account, and any subdomain must already have been created. A missing subdomain entry is a quiet failure: the request goes nowhere useful.

Understand What a Pending Request Means

After the request, konsoleH asks the certification authority to authenticate your domain, and that may take a few minutes. With DNS-based authentication, konsoleH creates a DNS record in the zone and the authority may need several hours to verify it. Do not request again during that window; verify the record instead.

Handle Manual Authentication Carefully

Sometimes konsoleH cannot authenticate the domain automatically. When that happens, the SSL Manager shows authentication tokens, and you verify the domain either with a file or with a DNS record.

For the file method, the file must contain exactly the content shown in the SSL Manager, with extra characters such as spaces and line breaks removed. The URL must also return that content directly, without a redirect. A stray newline or an enforced redirect is enough to fail validation.

Check Which Nameservers Your Domain Uses

TXT records you create in konsoleH's DNS management section only work for authentication if your domain actually uses konsoleH's nameservers. If your DNS is hosted elsewhere, create the TXT records at that other provider instead. This is one of the most common reasons a correctly entered record never gets seen.

Read the Result, Then Act

konsoleH will not install the SSL account until authentication is complete, and a successfully installed SSL account shows a green checkmark in the SSL Manager. If authentication is still pending after 24 hours, recheck the file or DNS record and then submit a support request.

If you requested the certificate directly through the domain's SSL account, konsoleH installs it automatically once issued, so no separate installation step should be needed. If you used a different route, the certificate may exist without being installed, which brings you back to the konsoleH login page symptom.

Issuance Failed for Hetzner-Managed Cloud Certificates

For certificates managed by Hetzner in the Cloud Console, the validation path is different. These certificates can only be created with a Hetzner DNS zone, either by using Hetzner DNS directly or by delegating the ACME challenge to Hetzner DNS from an external DNS setup.

Confirm that DNS actually answers for the domain. Hetzner DNS uses the nameservers hydrogen.ns.hetzner.com, oxygen.ns.hetzner.com and helium.ns.hetzner.de, and DNS must respond correctly for a certificate to be created.

Once you fix the underlying error, you do not need to start over. Use the options dropdown in the Hetzner Console to retry issuing the certificate. Retrying is appropriate after a real fix, such as correcting a DNS zone, not as a repeated workaround.

Certificate Exists but the Browser Still Warns

If the certificate was issued and installed but browsers still refuse the connection, the problem is in what is being served. Check these in order.

Verify the Hostname Resolves Correctly

Confirm that the exact hostname in the address bar resolves to the IP address of the server holding the certificate. A domain pointing at an old server, a parking page, or a different host will serve a different certificate entirely, or none.

Confirm the Certificate Covers That Exact Name

A certificate must cover your domain name, either directly or through a wildcard certificate, for the site to be served securely over HTTPS. The details matter:

  • A Business certificate covers specific names such as example.com and www.example.com, and a multi-name certificate is called a SAN certificate.
  • A wildcard certificate covers all subdomains directly under a domain, such as *.example.com.

So if your certificate lists example.com but visitors reach www.example.com, the connection fails unless www is also covered. A wildcard for *.example.com does not cover example.com itself, and it does not cover deeper names like shop.eu.example.com.

Check Server-Side Binding and the Chain

On a VPS or Cloud server where you installed the certificate, three things must line up.

  1. The web server block or virtual host for the exact hostname must reference the certificate.
  2. The private key must match that certificate. A mismatched key pair produces a handshake failure or a warning, even though the files load without error.
  3. The full chain must be installed. When adding a server certificate with intermediate certificates in the Hetzner Console, the primary certificate and the intermediate certificates are combined into a single PEM sequence and pasted into the form. A missing intermediate breaks validation on some clients while working fine in others, which makes it easy to miss.

After any change, reload the web server rather than assuming the new configuration is live.

Rule Out Mixed Content and Stale Caches

If the padlock appears but the browser still flags the page as not fully secure, the likely cause is insecure resources loaded over plain HTTP. Check the browser console for blocked or warned requests and update those URLs to HTTPS.

Also rule out caching before you change anything else. A CDN or a browser holding an old certificate, an old redirect, or an old page can make a fixed site look broken. Test in a private window and, where relevant, purge the CDN cache.

A Special Kubernetes Case: Domain Changes and Old Certificates

If you run a Hetzner load balancer through the Hetzner Cloud Controller Manager, a domain change can leave the previous certificate attached. With HCCM v1.36.0, changing the managed certificate domains annotation on a load balancer Service does not necessarily replace the certificate already attached, so the old one can remain in place.

This is a name collision, which is not the same as a certificate request that cannot complete domain validation. A fresh unique name will not repair missing DNS authority, so confirm which of the two problems you actually have before editing anything.

Renewal and Expiry Checks

An expired certificate produces the same browser warning as a misconfiguration, so check the expiry date early.

Basic and Let's Encrypt certificates renew automatically as long as the hosting account remains active. Business certificates do not; they must be renewed or reissued manually in the SSL Manager, and the web server uses a reissued certificate only after it is activated. Certificates you uploaded yourself to the Hetzner Console also need your own monitoring and renewal.

When to Contact Hetzner Support

Hetzner does not offer phone support for setting up, requesting, or troubleshooting SSL certificates, and help comes only through an authorized support request in konsoleH. Open that request under Management → Support Request, select the affected hosting account, and choose the topic SSL. Menu labels can shift over time, so look for the equivalent path if the wording differs slightly.

Include enough detail that support does not have to ask: the exact hostname, whether you use www, non-www or both, where DNS is hosted, which nameservers are authoritative, the certificate type, the current status shown in the SSL Manager or Console, and any error text. If authentication is still pending after 24 hours, recheck the file or DNS record before submitting the request.

Quick Symptom-to-Fix Summary

  • Only the konsoleH login page appears over HTTPS: the SSL account is not installed. Request or install it through the domain's SSL account.
  • Request stuck in authentication: recheck the file content, redirects, and whether your DNS uses konsoleH's nameservers.
  • Cloud managed certificate failed: confirm a Hetzner DNS zone answers correctly, fix the error, then retry from the options dropdown.
  • Issued but browser still warns: verify the hostname resolves to the right server and that the certificate covers the exact name in use.
  • Self-managed server: check the virtual host binding, the key pairing, and that the full chain is installed.
  • Padlock present but page flagged: look for mixed content and clear caches before touching the certificate.
  • Expired: confirm whether renewal is automatic or manual for your certificate type.

Working in this order stops you from reissuing certificates that were never the problem, and gets the right detail into a support request when you need one.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top