# Installed certificate, but https site not working

**URL:** <https://community.letsencrypt.org/t/installed-certificate-but-https-site-not-working/169361>\
**Category:** Help\
**Created:** [January 9, 2022, 10:36pm UTC](https://community.letsencrypt.org/t/installed-certificate-but-https-site-not-working/169361 "2022-01-09T22:36:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![shahravi](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/shahravi/32/57309_2.png) [@shahravi](https://community.letsencrypt.org/u/shahravi)\
**Post date:** [January 9, 2022, 10:36pm UTC](https://community.letsencrypt.org/t/installed-certificate-but-https-site-not-working/169361/1 "2022-01-09T22:36:35Z")

</div>

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. [crt.sh | example.com](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: [www.childrenscodingclub.com](http://www.childrenscodingclub.com)

I ran this command:sudo certbot --nginx

It produced this output:  
Requesting a certificate for [childrenscodingclub.com](http://childrenscodingclub.com) and [www.childrenscodingclub.com](http://www.childrenscodingclub.com)

Successfully received certificate.  
Certificate is saved at: /etc/letsencrypt/live/childrenscodingclub.com/fullchain.pem  
Key is saved at: /etc/letsencrypt/live/childrenscodingclub.com/privkey.pem  
This certificate expires on 2022-04-09.  
These files will be updated when the certificate renews.  
Certbot has set up a scheduled task to automatically renew this certificate in the background.

Deploying certificate  
Successfully deployed certificate for [childrenscodingclub.com](http://childrenscodingclub.com) to /etc/nginx/sites-enabled/childrenscodingclub.com  
Successfully deployed certificate for [www.childrenscodingclub.com](http://www.childrenscodingclub.com) to /etc/nginx/sites-enabled/childrenscodingclub.com  
Congratulations! You have successfully enabled HTTPS on [https://childrenscodingclub.com](https://childrenscodingclub.com) and [https://www.childrenscodingclub.com](https://www.childrenscodingclub.com)

My web server is (include version): nginx version: nginx/1.18.0 (Ubuntu)

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

My hosting provider, if applicable, is: AWS EC2 instance

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, using ssh

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

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [January 9, 2022, 10:43pm UTC](https://community.letsencrypt.org/t/installed-certificate-but-https-site-not-working/169361/2 "2022-01-09T22:43:13Z")

</div>

> [@shahravi](#):
>
> AWS EC2 instance

All looks good. Check your AWS Security Group to ensure you allow traffic for port 443

---

<div class="post-metadata">

**Author:** ![shahravi](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/shahravi/32/57309_2.png) [@shahravi](https://community.letsencrypt.org/u/shahravi)\
**Post date:** [January 9, 2022, 10:55pm UTC](https://community.letsencrypt.org/t/installed-certificate-but-https-site-not-working/169361/3 "2022-01-09T22:55:54Z")

</div>

Thanks! This solved it, and I can see the site at [https://childrenscodingclub.com](https://childrenscodingclub.com)

Newbie to implementing https, so looks like I now have to change requests going from my Angular application to https, and unsure yet if [socket.io](http://socket.io) requests served through my node server will continue to work or not. Will do some research and make headway.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [February 8, 2022, 10:56pm UTC](https://community.letsencrypt.org/t/installed-certificate-but-https-site-not-working/169361/4 "2022-02-08T22:56:01Z")

</div>

Closed on February 8, 2022, 10:56pm UTC

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