My website is offline or unavailable?

If CloudFlare can not connect to your server, a "Website Currently
Unavailable, no cached version" message will appear. This error
message occurs in two circumstances:
1.Your server or hosting provider is having issues
2.Your server or hosting provider is nothaving issues, but either your
hosting provider or server is limiting or blocking connections from
CloudFlare IPs
Tips to diagnose if your origin server isoffline
When you see the "Website Currently Unavailable" message, the first
step is to check to see if your origin server is having issues. To do
so, there are two tests that you can run.
Test 1)Try accessing the following subdomain for your website (i.e
yourdomain.com):
direct.yourdomain.com
If you can't get to the site going direct,then the issue is likely
with your serveror hosting provider. In this case, contact your
hosting provider to find out why your origin server is offline.
Note: CloudFlare adds the 'direct' subdomain when you sign up for the
service. It bypasses CloudFlare's network. Some users choose to edit
the name of the subdomain, so if you've changed the name, then you
should replace 'direct' with the revisedsubdomain name.
Test 2)Run the following curl command in Terminal or Putty:
curl -v -H 'Host: yourdomain.com' server IP address
So, as an example:
curl -v -H 'Host: yourdomain.com' 111.111.111.11
Tip: You can get your server IP address from your CloudFlare DNS
Settings page for the domain.
If the curl returns an error message like "can't connect to host" or
"500 internal server error", then the issue iswith your server or
hosting provider. Please contact your hosting provider for assistance.
If the curl returns HTML in the response, then the issue is that your
server or hosting provider has rules in place limiting connections
from CloudFlare IPs.
Proceed to the next section for Troubleshooting Help.
Tips to ensure CloudFlare's IPs are accepted by your server
If your server origin is online, then:
1.Make sure that you're not blocking CloudFlare IPs in .htaccess,
iptables , or your firewall.
2.Make sure your hosting provider isn'trate limiting or blocking IP
requests from the CloudFlare IPs and ask themto whitelist the IP
addresses below:
IPv4
204.93.240.0/24
204.93.177.0/24
199.27.128.0/21
173.245.48.0/20
103.21.244.0/22
103.22.200.0/22
103.31.4.0/22
141.101.64.0/18
108.162.192.0/18
190.93.240.0/20
188.114.96.0/20
197.234.240.0/22
198.41.128.0/17
162.158.0.0/15
IPv6
2400:cb00::/32
2606:4700::/32
2803:f800::/32
2405:b500::/32
2405:8100::/32
3) Make sure that you're operating off of the most recent versions of
Bad Behavior or mod_security. You want to ensure that mod_security's
core rules aren't blocking CloudFlare requests.
4) If you are running custom Apache modules, such asmod_antiloris and
mod_reqtimeout,disable and unload the modules. These modules will
block any time an IP connects more than 22 times. Since all
connections are now coming from a CloudFlare IP, you will definitely
hit the limit causing the error page. As soon as you unload the
module, the issue will disappear.