Warning

Port 80 is closed or doesn't answer

The short version

Open port 80 and redirect it to HTTPS, so visitors who type the name still arrive.

What it means

Port 80, the plain HTTP port, is closed or doesn't answer on these addresses. Your site may well work on port 443 over HTTPS, but someone who types your domain into an older browser, a script or a device that starts with plain HTTP gets an error instead of being sent on to the secure address.

Why it matters

Modern browsers try HTTPS first for many sites, but not all of them do, and not for every domain. Plenty of clients still start with plain HTTP: links in old emails and documents, printed addresses typed by hand, monitoring services and certificate authorities checking control of a domain. An open port 80 that redirects to HTTPS costs nothing and catches all of them. The common HTTP challenge that free certificate authorities use also needs port 80.

How to fix it

  1. Allow incoming TCP on port 80 in the server's firewall and in your provider's security group, for IPv4 and IPv6.
  2. Configure the web server to answer on port 80 with a permanent redirect to the HTTPS address. In nginx: a server block with listen 80;, listen [::]:80; and return 301 https://$host$request_uri;.
  3. Keep the redirect simple: send every path to the same path on HTTPS, and serve no content on port 80.
  4. If you use a CDN, switch on its setting that redirects HTTP to HTTPS.

Check it worked

Run the web port check again with the fresh option. Port 80 should be open on every address and show a redirect to an HTTPS address. The redirect checker shows the full chain.