# My site is down with a weird SSL notification

**URL:** <https://meta.discourse.org/t/my-site-is-down-with-a-weird-ssl-notification/63246>\
**Category:** Self-hosting\
**Created:** [Maio 24, 2017, 12:14am UTC](https://meta.discourse.org/t/my-site-is-down-with-a-weird-ssl-notification/63246 "2017-05-24T00:14:05Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [Maio 24, 2017, 1:29am UTC](https://meta.discourse.org/t/my-site-is-down-with-a-weird-ssl-notification/63246/13 "2017-05-24T01:29:10Z")

</div>

If you shared your site name then people could look at your certificate and have more information to help you like whether DNS changes have propagated.

My best guess is that whatever certificate you got is expired. Can you say how or where you got it? The instructions you linked to don’t describe how to get a certificate.

The simplest solution would be to turn off cloudflare and rebuild your site with Let’s Encrypt.

You can turn off force\_https like this:

```bash
cd /var/discourse
./launcher enter app
rails c
SiteSetting.force_https=false
exit
exit

```

But most browsers (like yours) will remember that the site is supposed to be https and will try very hard not to connect. Or, more elegantly:

> [@mpalmer](#):
>
> but it won’t do any good, as any previous visitor to the site will have remembered that HTTPS is supposed to be enabled, and will fail to connect (as shown in the error you originally pasted).

---

_[View the full topic](https://meta.discourse.org/t/my-site-is-down-with-a-weird-ssl-notification/63246)._