I just moved from Digital Ocean to AWS. My usual setup procedures for the web server I use for experimentation are not working.

I can reach the site through IPv4 but all domains error out and my SSL certificate doesn't show up when tested on SSL Shopper. DNS appears to be working fine, my firewall is open, SSL certificate installed and NGINX running fine. When all the obvious things are working what do I need to check? Or alternately am I missing something really obvious?

This is my setup.

The IPv4 address brings up the default NGINX welcome screen.

Unfortunately all domains error out,





SSL Labs test

IPs detected correctly on https://www.ssllabs.com/ but in both cases unable to connect to server.

SSL Shopper test

No SSL certificates found on https://www.sslshopper.com/.

In Linux

Both ports open.

firewall-cmd --list-ports

80/tcp 443/tcp

Nginx installed.

Nginx status: Active: active (running) since Fri 2021-03-05 13:48:16 MST; 2h 33min ago

curl localhost:80 returns 301 redirect which is correct.

Lets Encrypt SSL certificate installed.

Expiry Date: 2021-06-03 18:11:03+00:00 (VALID: 89 days)

In AWS console:

VPC > Your VPCs >

DNS hostnames: Enabled

DNS resolution: Enabled

IPv6 pool: Amazon ✓ Associated

EC2 > Instances >

Instance state: Running

Status check: 2/2 checks passed

Public IPv4 address: (example.com)

Elastic IP addresses: (example.com) [Public IP]

EC2 > Security Groups >

Inbound rules


HTTPS TCP 443 ::/0

Route 53 > Hosted zones >


example.com A Simple

example.com AAAA Simple 2001:0db8:85a3:0000:0000:8a2e:0370:7334

www.example.com A Simple

www.example.com AAAA Simple 2001:0db8:85a3:0000:0000:8a2e:0370:7334


This is what my security console looks like. VPC > Security Groups > [my id] enter image description here

  • What exactly do you mean by "error out"? – Tilman Schmidt Mar 6 at 19:20

You need to open port 443 for IPv4 in your AWS security group (and port 80 for IPv6).

  • Hi Mike, in the AWS console when I select HTTP from the dropdown the Port range is greyed out with 80 in the field. It won't let me change it. The same story for https. I'm at EC2 > Security Groups > [my security group ID] – myNewAccount Mar 6 at 0:21
  • I wouldn't expect it to let you change the port number when you select a service by name. What does that have to do with this, though? – Michael Hampton Mar 6 at 0:37
  • @myNewAccount You need to add a new rule to the security group - one for HTTP port 80 and one for HTTPS port 443. – MLu Mar 6 at 1:44
  • @MLu As soon as I select HTTP the Port range goes to 80 and stays greyed out. – myNewAccount Mar 6 at 1:48
  • 1
    You've been commenting on the answer this whole time though... – Michael Hampton Mar 6 at 2:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.