Fail

Port 443 doesn't answer

The short version

Check the firewall in front of these addresses and allow port 443.

What it means

We tried to connect to port 443 on these addresses and got no answer at all within three seconds: no refusal and no connection. That usually means a firewall drops the packets silently, or the address isn't routed to a working server any more.

Why it matters

A silent drop is the slowest way to fail. A visitor's browser waits for the connection to time out before it gives up or tries another address, so the page hangs for many seconds. If all your addresses are affected, your site is down for everyone using HTTPS, which today is nearly everyone.

How to fix it

  1. Check the firewall on the server itself (for example ufw, firewalld or nftables) and allow incoming TCP on port 443, for IPv4 and IPv6 separately.
  2. Check your provider's firewall or security group in front of the server. Cloud providers block every port by default until you add a rule.
  3. If the address has moved to another server, update or remove the A or AAAA record that still points at it.
  4. If you use a CDN or proxy, check that the address in DNS is the provider's and not your origin server's, which may only accept connections from the provider.

Check it worked

Run the web port check again with the fresh option. Each address should show port 443 as open. If it still doesn't answer, check that the server is running and reachable from outside your network.