concrete5.org website hosting issue?

Permalink
Is Concrete5.org still having web hosting issues?

It is becoming a common occurrence that the Concrete5 website goes temporarily offline. I have noticed other people mentioning it in the forum over the past few months. Are other people also still experiencing this?

The offline message mentions CloudFlare I think.

Hopefully this problem can get sorted out once and for all.

Regards
Luke

studio108
 
Mainio replied on at Permalink Reply
Mainio
Yeah, it's been a recurring problem for a "while" now:
https://www.concrete5.org/community/forums/chat/concrete5.org-under-...

Still seeing it occasionally but not nearly as often as it occurred during December and January. And the breaks are shorter as well now.
CMSDeveloper replied on at Permalink Reply 1 Attachment
CMSDeveloper
Yeh! Cloudflare sucks. It's just a dumb proxy with some port filtering.
Just blocked all cloudflare ip addresses in my hosting firewall services!

Deny from 199.27.128.0/21
Deny from 173.245.48.0/20
Deny from 103.21.244.0/22
Deny from 103.22.200.0/22
Deny from 103.31.4.0/22
Deny from 141.101.64.0/18
Deny from 108.162.192.0/18
Deny from 190.93.240.0/20
Deny from 188.114.96.0/20
Deny from 197.234.240.0/22
Deny from 198.41.128.0/17
Deny from 162.158.0.0/15
Deny from 104.16.0.0/12

This to prevent my clients to use cloudflare services.
Just a security issue, has to do with "The Patriot Act" and NSA for EU users.

Whois:
Registry Registrant ID:
Registrant Name: CloudFlare, Inc.
Registrant Organization: CloudFlare, Inc.
Registrant Street: 665 Third Street
Registrant City: San Francisco
Registrant State/Province: CA
Registrant Postal Code: 94107
Registrant Country: US
Registrant Phone: +1.6503198930
studio108 replied on at Permalink Reply 1 Attachment
studio108
The concrete5 web hosting issue continues! (see attached screen grab)

At about 10.15am GMT the Concrete5 site was down again. This then has a knock on effect when trying to working on a clients website. When logging into the clients site I have to wait until the CMS realises that it cannot check for updates due to the fact the main C5 server is down.

Surely this problem should be sorted out by now!