I could see our css has come back to normal for some seconds after DNS has changed to grey.
but after a while we get “insecure connection problem”. and I can’t confirm it!
Your connection is not secure
do you know how to remove the insecure connection problem?
@Pad_Pors looks like your Let’s Encrypt SSL cert expired in May. Were you using a CloudFlare certificate, that now isn’t being used as traffic isn’t going through CloudFlare?
Going “grey” means you do not use any Cloudflare features. Thus, you were likely using the default SSL setting in Cloudflare or have a SSL page rule set, and when you turn off Cloudflare, then SSL isn’t being applied.
I can confirm that for you
The browser page says that the certificate expired on May 22, 2017 now…
I CAN CONFIRM THAT IT’S AN ISSUE WITH CLOUDFLARE
I accessed through IP and it’s perfectly working
Trying to clear all cache…
I’m little bit confused. more than my knowledge! but I guess I should follow this thread:
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 SSL Certificate
Go to namecheap or some other SSL cert provider and purchase a SSL cert for your domain. Follow all the step documented by them to generate private key and CSR and finally get your cert. I used the apache defau…
am I right?
@jomaxro for your experimenting spirit! I was just reading meta to find out some clue before your experiments!
Enabling Development Mode in Cloudflare is a temp fix for this issue
I’m testing other stuff to check if it’s permanent
I’m not sure Cloudflare is the issue here. As I’ve mentioned, we hadn’t done any changes to our code or to Cloudflare, and when beta14 hit, then we have the issue.
Probably in that update some CSS stuff changed (I’m not sure) and it’s wrongly cached and/or processed by Cloudflare
We use Cloudflare as a reverse proxy because we get DDoS attcked quite often. We cannot live with Cloudflare in dev mode as that exposes our IP address.
you’re right. but now even if there is a bug in the latest update, it can be reproduced. and the bug can be solved.
@RyanK is there any way you can help escalating this for us? Lots of Discourse sites can no longer use CloudFlare due to Rocket Loader breaking us.
Thanks for this temp solution
In our testing, you only need to uncheck CSS.
Keep in mind this sets it so your entire domain isn’t auto minimizing CSS. You may want to create a page rule for your Discourse subdomain and add the rule “Disable Performance”. Keep in mind this turns off all auto-minify, Rocket Loader, etc ONLY for your Discourse subdomain.
I strongly recommend you check “Purge Individual Files” and then type in your Discourse domain with trailing “/*” (slash star). This way you are only clearing all cache on your Discourse instance and not your entire origin domain.
I’ve tried also that, but then Cloudflare said:
Purging , so I prefered to Purge Everything, as maybe it doesn’t support wildcards 1 file…
Absolutely. Let me see if I can get some eyes on this. We are actually having our company retreat this week so I think everyone is in the pacific timezone
Mmm, is the Flags tab working? On mine not
But maybe it’s an issue with a plugin, just to discard a general bug
Thanks heaps Ryan, Hope you enjoy your retreat, we do have a workaround so its not mega super extra urgent.
I’ve tried also that, but then Cloudflare said: Purging 1 file…, so I prefered to Purge Everything, as maybe it doesn’t support wildcards
My solution worked for me. For example, “
https://discussions.ftw.in/*” will purge our entire Discourse domain but not our origin.
It’s not officially starting for a couple days, but most of the global team is either already in SF or en route