# 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:** [May 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:** 16

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [May 24, 2017, 2:22am UTC](https://meta.discourse.org/t/my-site-is-down-with-a-weird-ssl-notification/63246/16 "2017-05-24T02:22:12Z")

</div>

> [@Falco](#):
>
> it can take literally hours to propagate and update caches.

The TTL used by CloudFlare is only 300 seconds.

HSTS specifically takes longer because the browser has retained the instruction. For example on Chrome you can visit chrome://net-internals/#hsts and remove a domain, which will immediately bypass the old HSTS instruction.

> [@Yassine\_Yousfi](#):
>
> My domain name is: [stopbyte.com](http://stopbyte.com)

Are you referring to the default shared SSL that CloudFlare implements? If not what’s the source?

In your app.yml did you enable support for Let’s Encrypt by uncommenting the entries for web.template.ssl and web.letsencrypt.ssl.template? They’re all you need for HTTPS at the server end. Once they’re working you can safely enable strict HTTPS at CloudFlare.

---

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