[SOLVED] Certificate installed but not "read"

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: cte.com.br

I ran this command:Instalattion according to Let’s Encrypt Apache + Ubuntu 18.04 steps.

It produced this output:Congratulations! Cert installed.

My web server is (include version): Amazon (AWS EC2)

The operating system my web server runs on is (include version): Ubuntu 18.04

My hosting provider, if applicable, is: AWS

I can login to a root shell on my machine (yes or no, or I don’t know): yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 0.31.0

2

Hi @maicon.passos

you have created three identical certificates

Issuer not before not after Domain names LE-Duplicate next LE
Let's Encrypt Authority X3 2019-09-26 2019-12-25 cte.com.br - 1 entries duplicate nr. 3
Let's Encrypt Authority X3 2019-09-26 2019-12-25 cte.com.br - 1 entries duplicate nr. 2
Let's Encrypt Authority X3 2019-09-26 2019-12-25 cte.com.br - 1 entries duplicate nr. 1

but it's impossible to see if you use one of these. Because there is a timeout checking https.

http works. Is there a firewall or a wrong configured router?

ec2-18-229-152-3.sa-east-1.compute.amazonaws.com

is your hostname, there is a firewall you have to open.

3

Hello! And thanks for the super fast reply.

You can guide me a way to check what is blocking https to work? As described we are using a AWS EC2 instance, is there a default configuration to make this work?

Thanks!

4

Hello! Problem solved! I just added port 443 on Instance Security Group, thanks for your help!

5

Yep, happy to read you have found the solution. I don't use AWS, but there are other users with the same problem. And it's required to allow port 443 to see, if it has worked.

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.