Start
/
Fehlerbehebung
/
HTTPS Redirect Troubleshooter

HTTPS Redirect Troubleshooter

Why your redirect works on HTTP but not HTTPS, and how to fix it

You have configured a domain redirect in AutoDNS and it works when you visit http://www.domain.de, but when you try https://www.domain.de your browser shows a security warning or the redirect does not work. This is the most common redirect issue and it is not a bug. This article explains why it happens and how to resolve it.

How AutoDNS Redirects Work

When you set up a redirect in AutoDNS, the system creates a DNS record that points your domain to the InterNetX redirector service. When a visitor requests your domain, the redirector sends an HTTP response telling the browser to go to your target URL.

HTTP redirect: Visitor requests http://domain.de → redirector receives the request → sends a 301/302 redirect to target URL. This works because no SSL certificate is needed for HTTP.
HTTPS redirect: Visitor requests https://domain.de → browser tries to establish an encrypted (TLS/SSL) connection FIRST, before any redirect can happen → the redirector does not have an SSL certificate for your domain → browser shows a security error → redirect never executes.

⚠ Key point: The browser must complete the SSL handshake before it can receive the redirect instruction. Without a valid SSL certificate for your domain on the redirector, the HTTPS connection fails at the TLS layer and the redirect never reaches the browser.

Why HTTPS Fails Without a Certificate

HTTP request flow (works):
Browser → http://domain.de → Redirector → 301 → target URL ✓

HTTPS request flow (fails):
Browser → https://domain.de → TLS handshake → No certificate! → ✗ Connection refused
                                                  ↑
                                     Redirect never reaches the browser.
                                     The failure happens BEFORE the
                                     redirector can respond.

Modern browsers increasingly enforce HTTPS. Many browsers automatically upgrade http:// requests to https://, which means even visitors who type the HTTP version may end up hitting the HTTPS version. This is why a redirect that "used to work" may appear to stop working without any configuration change on your side.

How to Fix It

Option 1: Use a hosting provider with SSL (recommended)

Set up minimal web hosting for the domain (any provider that supports SSL certificates).
Install an SSL certificate for the domain (free via Let's Encrypt, or a commercial certificate via AutoDNS).
Configure the redirect at the hosting level (e.g. via .htaccess, nginx config, or the hosting panel's redirect feature). This handles both HTTP and HTTPS because the hosting server has the certificate.

Option 2: Use Cloudflare or similar CDN with free SSL

Point the domain's nameservers to Cloudflare (free plan available).
Cloudflare provides a free SSL certificate and handles the TLS handshake.
Configure a Page Rule or Redirect Rule in Cloudflare to redirect to the target URL. Both HTTP and HTTPS will work.

Option 3: Keep HTTP-only redirect (limited)

If HTTPS is not required, you can continue using the AutoDNS redirector for HTTP-only redirects. However, be aware that an increasing number of browsers will automatically upgrade to HTTPS, making this option less reliable over time.

Common Error Messages

ERR_SSL_PROTOCOL_ERROR: Browser could not establish an SSL connection. No valid certificate exists for this domain on the redirector. This is the expected error when using HTTPS with the AutoDNS redirector.
ERR_CERT_COMMON_NAME_INVALID: A certificate was presented but it does not match the domain name. The redirector's own certificate does not cover your domain.
ERR_CONNECTION_REFUSED: No server is listening on port 443 (HTTPS) for this domain. The redirector only listens on port 80 (HTTP).
NET::ERR_CERT_AUTHORITY_INVALID: The certificate is not trusted by the browser. Occurs if a self-signed or mismatched certificate is served.
"Your connection is not private": Chrome/Edge warning page shown when HTTPS fails. The user can click "Advanced" to proceed, but most visitors will leave. This is why HTTPS support matters for redirects.

Quick Diagnostic

Does http:// work?: Yes → Your redirect configuration is correct. The issue is HTTPS/SSL only. Follow the fix options above.
Does http:// also fail?: Check: Is the redirect configured in AutoDNS? Are the nameservers pointed to AutoDNS? Has DNS propagated? Use dig domain.de or an online DNS checker to verify.
Did it work before but stopped?: Browser upgrade likely. Modern browsers (Chrome 115+, Firefox, Edge) increasingly auto-upgrade HTTP to HTTPS. Your redirect may still be configured correctly but the browser is now requesting HTTPS first.
HSTS domain?: If the domain previously had HTTPS enabled (e.g. it was hosted with SSL), the browser may have cached an HSTS policy that forces HTTPS. Clear the browser's HSTS cache or wait for the policy to expire.

When to Contact Support

Self-resolvable: HTTPS redirect not working (SSL certificate needed). Browser showing security warning on HTTPS. Redirect works on HTTP but not HTTPS. All covered above.
Contact support: Neither HTTP nor HTTPS redirect works, despite correct configuration. Redirect was working and stopped without any changes on your side (and it's not a browser HTTPS upgrade). Redirect target URL is correct but the browser is redirected to the wrong destination.