Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Security

HTTPS not working: test DNS, TLS and web-server layers

Published August 2026 · 8 min read

HTTPS depends on several layers succeeding in order. A valid certificate cannot help when DNS points to the wrong IP, and an open port cannot help when the server presents a certificate for another hostname.

Start with DNS

Resolve the hostname and confirm it points to the intended public endpoint. Check both A and AAAA records; a broken IPv6 path can affect clients even when IPv4 works.

Verify TCP reachability on port 443

Check provider and host firewalls, reverse-proxy listening sockets, and network routes. A connection timeout or refusal occurs before certificate validation.

Inspect the TLS handshake and certificate

Confirm hostname coverage, validity, trust chain, and the certificate being served by the public virtual host. If a CDN or proxy terminates TLS, inspect that edge as well as the origin when relevant.

Then troubleshoot the HTTP application response

Once TLS succeeds, HTTP 404, 500, 502, redirect loops, or application errors are separate problems. Do not keep replacing certificates after the secure connection is already established.

Next step

If HTTPS is not working, confirm DNS reaches the right server, port 443 is reachable, the TLS handshake succeeds, the certificate matches, and the web server has the correct virtual host.

Read website troubleshooting guides

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

cPanel error logs: where to look when a site breaks

cPanel exposes recent website errors, while server and application logs may contain deeper detail. Learn which log to check for PHP, Apache, cPanel, mail, and system failures.

Read the guide

Database connection failed: how to check the whole path

A database connection failure can involve DNS, host, port, firewall, service state, TLS, credentials, privileges, connection limits, or application configuration.

Read the guide

More troubleshooting guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move