# Latest update requires cache purge in CloudFlare
**URL:** https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166
**Category:** Self-hosting
**Created:** [Octobre 31, 2017, 8:05 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166 "2017-10-31T20:05:05Z")
**Posts on this page:** 20
**Page:** 2
### Author:  [@Pad\_Pors](https://meta.discourse.org/u/Pad_Pors)
#### Post date: [Octobre 31, 2017, 8:49 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/21 "2017-10-31T20:49:48Z")
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?
---
### Author:  [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [Octobre 31, 2017, 8:51 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/22 "2017-10-31T20:51:30Z")
@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?
---
### Author:  [@Brock\_Busby](https://meta.discourse.org/u/Brock_Busby)
#### Post date: [Octobre 31, 2017, 8:52 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/23 "2017-10-31T20:52:36Z")
> [@Pad\_Pors](#):
>
> but after a while we get “insecure connection problem”. and I can’t confirm it!
>
> Your connection is not secure
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.
---
### Author:  [@dax](https://meta.discourse.org/u/dax)
#### Post date: [Octobre 31, 2017, 8:54 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/24 "2017-10-31T20:54:48Z")
> [@Pad\_Pors](#):
>
> I could see our css has come back to normal for some seconds after DNS has changed to grey.
I can confirm that for you
The browser page says that the certificate expired on May 22, 2017 now…
---
### Author:  [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)
#### Post date: [Octobre 31, 2017, 8:55 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/25 "2017-10-31T20:55:07Z")
I CAN CONFIRM THAT IT’S AN ISSUE WITH CLOUDFLARE
I accessed through IP and it’s perfectly working
* * *
Trying to clear all cache…
---
### Author:  [@Pad\_Pors](https://meta.discourse.org/u/Pad_Pors)
#### Post date: [Octobre 31, 2017, 8:57 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/26 "2017-10-31T20:57:44Z")
I’m little bit confused. more than my knowledge! but I guess I should follow this thread:
> [@Allow SSL / HTTPS for your Discourse Docker setup](https://meta.discourse.org/t/allowing-ssl-https-for-your-discourse-docker-setup/13847):
>
> 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](https://meta.discourse.org/t/142537?silent=true) defaults – a container configuration file at/var/discourse/containers/app.yml and Discourse docker is installed at: /var/discourse Buy a SS…
am I right?
* * *
p.s.: thanks @jomaxro for your experimenting spirit! 🙂 I was just reading meta to find out some clue before your experiments!
---
### Author:  [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)
#### Post date: [Octobre 31, 2017, 9:01 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/27 "2017-10-31T21:01:03Z")
**Enabling Development Mode in Cloudflare is a temp fix for this issue**
I’m testing other stuff to check if it’s permanent
---
### Author:  [@Brock\_Busby](https://meta.discourse.org/u/Brock_Busby)
#### Post date: [Octobre 31, 2017, 9:01 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/28 "2017-10-31T21:01:45Z")
> [@barreeeiroo](#):
>
> I CAN CONFIRM THAT IT’S AN ISSUE WITH CLOUDFLARE
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.
---
### Author:  [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)
#### Post date: [Octobre 31, 2017, 9:04 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/29 "2017-10-31T21:04:33Z")
Probably in that update some CSS stuff changed (I’m not sure) and it’s wrongly cached and/or processed by Cloudflare
---
### Author:  [@Brock\_Busby](https://meta.discourse.org/u/Brock_Busby)
#### Post date: [Octobre 31, 2017, 9:06 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/30 "2017-10-31T21:06:51Z")
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.
---
### Author:  [@Pad\_Pors](https://meta.discourse.org/u/Pad_Pors)
#### Post date: [Octobre 31, 2017, 9:09 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/31 "2017-10-31T21:09:50Z")
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.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [Octobre 31, 2017, 9:26 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/32 "2017-10-31T21:26:11Z")
@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.
---
### Author:  [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)
#### Post date: [Octobre 31, 2017, 9:30 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/33 "2017-10-31T21:30:09Z")
**PERMANTENT FIX:**
1. Login to Cloudflare
2. Go to Speed Section of your domain
3. Uncheck _CSS_
4. Go to Caching Section
5. Click the Arrow next to _Purge Individual Files_ and hit _Purge Everything_, and then _Confirm_
6. Wait a few seconds and check if your site loads properly
* * *
And it’s fixed 😊
---
### Author:  [@Brock\_Busby](https://meta.discourse.org/u/Brock_Busby)
#### Post date: [Octobre 31, 2017, 9:49 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/34 "2017-10-31T21:49:51Z")
Thanks for this temp solution
> [@barreeeiroo](#):
>
> Uncheck JS, CSS and HTML (yes, the three checkboxes and make sure they have been disabled refreshing the page)
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.
> [@barreeeiroo](#):
>
> Click the Arrow next to Purge Individual Files and hit Purge Everything, and then Confirm
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.
- [http://yourdiscoursedomain/](http://yourdiscoursedomain/)\*
- [https://yourdiscoursedomain/](https://yourdiscoursedomain/)\* (if using SSL)
---
### Author:  [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)
#### Post date: [Octobre 31, 2017, 9:51 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/35 "2017-10-31T21:51:03Z")
> [@Brock\_Busby](#):
>
> 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 **1** file…_, so I prefered to Purge Everything, as maybe it doesn’t support wildcards 😅
---
### Author:  [@RyanK](https://meta.discourse.org/u/RyanK)
#### Post date: [Octobre 31, 2017, 9:51 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/36 "2017-10-31T21:51:56Z")
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 🙂
---
### Author:  [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)
#### Post date: [Octobre 31, 2017, 9:52 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/37 "2017-10-31T21:52:27Z")
> [@jomaxro](#):
>
> No issues on my sandbox: [https://test.jomaxro.win/](https://test.jomaxro.win/)
Mmm, is the Flags tab working? On mine not 😕
But maybe it’s an issue with a plugin, just to discard a general bug
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [Octobre 31, 2017, 9:53 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/38 "2017-10-31T21:53:02Z")
Thanks heaps Ryan, Hope you enjoy your retreat, we do have a workaround so its not mega super extra urgent.
---
### Author:  [@Brock\_Busby](https://meta.discourse.org/u/Brock_Busby)
#### Post date: [Octobre 31, 2017, 9:53 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/39 "2017-10-31T21:53:11Z")
> [@barreeeiroo](#):
>
> 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/](https://discussions.ftw.in/)\*” will purge our entire Discourse domain but not our origin.
---
### Author:  [@RyanK](https://meta.discourse.org/u/RyanK)
#### Post date: [Octobre 31, 2017, 9:53 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/40 "2017-10-31T21:53:50Z")
It’s not officially starting for a couple days, but most of the global team is either already in SF or en route
[Page précédente](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166.md?page=1)
[Page suivante](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166.md?page=3)