My website has been running for a long time now, and suddenly today, after checking the traffic analytics noticed that it’s been down for the whole day. tried getting into the website and I get this error: "Your connection is not private Attackers might be trying to steal your information from mydomain.com (for example, passwords, messages, or credit cards). NET::ERR_CERT_COMMON_NAME_INVALID" [imagem] I rebuilt the website, but nothing :frowning: and checked CloudFlare it seems fine. Contacted Godaddy there was no issue from their side at all. I’m confused now any ideas?

[imagem] 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. [imagem] Yassine_Yousfi: My domain name is: 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.

Your site is presenting the wrong certificate, and has HSTS enabled. With the information available, there’s not a lot more detail we can give.

[imagem] mpalmer: HSTS I didn’t enable it! [imagem] and more awkwardly, I didn’t touch any coding or server at all it just went down on its own!!! :o

HSTS can be enabled by the origin server, it doesn’t have to be enabled by Cloudflare. If you ticked “force https” in your Discourse site’s settings, then that’ll do it. If your site is being proxied by Cloudflare, then it’s a problem at their end, and not something wrong with Discourse. Otherwise, check the certificate you’ve configured Discourse to use, and ensure that it matches the name you’re using to access the site.

[imagem] mpalmer: If you ticked “force https” in your Discourse site’s settings Yep, I’ve done that on discourse side loooong ago, and it’s been fine since then. there is no way to contact cloudflare :frowning: so is there a way I can “untick” the force https box from server side (as i can’t access my admin panel now). that way at least won’t be harmed that much :slight_smile: thanks

Well, what you changed recently? On Cloudflare DNS settings, is the cloud orange or gray? Try making it gray.

Changed absolutely nothing! :flushed: the cloud is orange, just changed it but nothing changed :o

When you change it from orange to gray, it changes the DNS entries, and it can take literally hours to propagate and update caches. After you are sure the change is live, a rebuild should trigger a new cert (I’m assuming you are using our Let’s Encrypt setup).

I followed these instructions from sam. [imagem] Allow SSL / HTTPS for your Discourse Docker setup Self-Hosting This guide is likely out of date as there are now very few reasons not to use the built-in Let’s Encrypt certificate that Just Works. See also: 2023-04-10 @pfaffman says: This is left here mostly for historical purposes. So you’d like to enable SSL for your Docker-based Discourse setup? Let’s do it! This guide assumes you used all the standard install defaults – a container configuration file at/var/discourse/containers/app.yml and Discourse docker is installed at: /var/discourse Buy a SS… Yep, will be waiting.

So you bought a certificate? Maybe it expired? Did you check that?

Nop, I used free shared one :slight_smile: I don’t buy certificates :sunglasses:

My site is down with a weird SSL notification

Suporte ao Produto Instalação

Yassine_Yousfi (sin) Maio 24, 2017, 1:11am 9

I followed these instructions from sam.

Yep, will be waiting.

Tópico		Respostas	Visualizações
Force Discourse to use SSL/HTTPS through CloudFlare Sysadmins how-to , cloudflare	7	7121	21 de Julho de 2017
Let’s Encrypt problem after upgrading to 1.9.0.beta3 Bug	13	1852	14 de Julho de 2017
Site Down. Please Help! Product Support	5	726	3 de Maio de 2019
Why is the Apple Touch Icon loaded via HTTP instead of HTTPS? Product Support	28	5225	19 de Dezembro de 2018
Discourse CDN with an invalid SSL cert? Product Support cdn , hosted-support	2	152	30 de Março de 2026

My site is down with a weird SSL notification

Tópicos relacionados