# Https redirects but shows 'This site can’t be reached'

**URL:** <https://community.letsencrypt.org/t/https-redirects-but-shows-this-site-can-t-be-reached/142787>\
**Category:** Help\
**Created:** [January 15, 2021, 7:11am UTC](https://community.letsencrypt.org/t/https-redirects-but-shows-this-site-can-t-be-reached/142787 "2021-01-15T07:11:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pa1rjp](https://avatars.discourse-cdn.com/v4/letter/p/85f322/32.png) [@pa1rjp](https://community.letsencrypt.org/u/pa1rjp)\
**Post date:** [January 15, 2021, 7:11am UTC](https://community.letsencrypt.org/t/https-redirects-but-shows-this-site-can-t-be-reached/142787/1 "2021-01-15T07:11:06Z")

</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. [https://crt.sh/?q=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:  
[http://dofriendly.com/](http://dofriendly.com/)

I ran this command:  
sudo certbot --nginx

It produced this output:  
ubuntu@ip-172-31-24-214:~$ sudo certbot --nginx  
Saving debug log to /var/log/letsencrypt/letsencrypt.log  
Plugins selected: Authenticator nginx, Installer nginx

Which names would you like to activate HTTPS for?

* * *

1: [dofriendly.com](http://dofriendly.com)  
2: [www.dofriendly.com](http://www.dofriendly.com)

* * *

Select the appropriate numbers separated by commas and/or spaces, or leave input  
blank to select all options shown (Enter 'c' to cancel): 1,2  
Cert not yet due for renewal

You have an existing certificate that has exactly the same domains or certificate name you requested and isn't close to expiry.  
(ref: /etc/letsencrypt/renewal/dofriendly.com.conf)

What would you like to do?

* * *

1: Attempt to reinstall this existing certificate  
2: Renew & replace the cert (limit ~5 per 7 days)

* * *

Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1  
Keeping the existing certificate  
Deploying Certificate to VirtualHost /etc/nginx/sites-enabled/dofriendly  
Deploying Certificate to VirtualHost /etc/nginx/sites-enabled/dofriendly

Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.

* * *

1: No redirect - Make no further changes to the webserver configuration.  
2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for  
new sites, or if you're confident your site works on HTTPS. You can undo this  
change by editing your web server's configuration.

* * *

Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2  
Redirecting all traffic on port 80 to ssl in /etc/nginx/sites-enabled/dofriendly  
Redirecting all traffic on port 80 to ssl in /etc/nginx/sites-enabled/dofriendly

* * *

Congratulations! You have successfully enabled [https://dofriendly.com](https://dofriendly.com) and  
[https://www.dofriendly.com](https://www.dofriendly.com)

You should test your configuration at:

> **[SSL Server Test: dofriendly.com (Powered by Qualys SSL Labs)](https://www.ssllabs.com/ssltest/analyze.html?d=dofriendly.com)**

  

> **[SSL Server Test: www.dofriendly.com (Powered by Qualys SSL Labs)](https://www.ssllabs.com/ssltest/analyze.html?d=www.dofriendly.com)**

* * *

IMPORTANT NOTES:

- Congratulations! Your certificate and chain have been saved at:  
/etc/letsencrypt/live/dofriendly.com/fullchain.pem  
Your key file has been saved at:  
/etc/letsencrypt/live/dofriendly.com/privkey.pem  
Your cert will expire on 2021-04-15. To obtain a new or tweaked  
version of this certificate in the future, simply run certbot again  
with the "certonly" option. To non-interactively renew _all_ of  
your certificates, run "certbot renew"

- If you like Certbot, please consider supporting our work by:

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

The operating system my web server runs on is (include version):  
Distributor ID: Ubuntu  
Description: Ubuntu 18.04.4 LTS  
Release: 18.04  
Codename: bionic

My hosting provider, if applicable, is:

> **[Make Your Own Way | GoDaddy IN](https://in.godaddy.com/)**
>
> All the help and tools you need to grow online: Websites, Domains, Digital and Social Marketing - plus GoDaddy Guides with you every step of the way

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

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [January 15, 2021, 8:00am UTC](https://community.letsencrypt.org/t/https-redirects-but-shows-this-site-can-t-be-reached/142787/2 "2021-01-15T08:00:57Z")

</div>

Welcome to the Let's Encrypt Community 🙂

Well... your port 443 (HTTPS) is closed, so redirecting from port 80 (HTTP) to port 443 (HTTPS) will result in no one being able to receive a useful response from your webserver.

Thank you, by the way, for choosing to reinstall your existing certificate rather than acquiring a duplicate certificate. It shows your wisdom in recognizing the existence of an _installation_ problem rather than an _acquisition_ problem.

---

<div class="post-metadata">

**Author:** ![pa1rjp](https://avatars.discourse-cdn.com/v4/letter/p/85f322/32.png) [@pa1rjp](https://community.letsencrypt.org/u/pa1rjp)\
**Post date:** [January 15, 2021, 9:00am UTC](https://community.letsencrypt.org/t/https-redirects-but-shows-this-site-can-t-be-reached/142787/3 "2021-01-15T09:00:57Z")

</div>

That was so dumb of me 😅, thank you so much 🙂

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [January 15, 2021, 1:17pm UTC](https://community.letsencrypt.org/t/https-redirects-but-shows-this-site-can-t-be-reached/142787/4 "2021-01-15T13:17:16Z")

</div>

It happens. I've done worse. 🙂

---

<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 14, 2021, 1:17pm UTC](https://community.letsencrypt.org/t/https-redirects-but-shows-this-site-can-t-be-reached/142787/5 "2021-02-14T13:17:17Z")

</div>

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