PDA

View Full Version : Site problems?



pepperpot
07-20-2012, 02:49 PM
When I use the "new post" or "what's new" tabs I get an error message. Anyone else?

Jolie Rouge
07-20-2012, 02:58 PM
I get it when I try to "SEARCH" or use the "new posts" feature .... :(

pepperpot
07-20-2012, 03:07 PM
Website currently unavailable
The website you are trying to access is currently unavailable. Please try again at a later time.
If you are the site owner, here is a help resource to help resolve the issue.

That's what I get.

This is from the "help resource"....

CloudFlare
Home
Features
Help
Sign up
Login
HelpWikiHelp centerKnowledge baseWikiVideosSystem statusDownloads
CloudFlare Wiki
Search help:
Type what you're looking for. We will try to find it for you!
I keep seeing My Site is Offline
Page
Discussion
View source
History

If CloudFlare can not connect to your server, a "Website Currently Unavailable" message will appear. This error message occurs in two circumstances:

Your server or hosting provider is having issues
Your server or hosting provider is not having issues, but either your hosting provider or server is limiting or blocking connections from CloudFlare IPs
Tips to diagnose if your origin server is offline

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 server or 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 revised subdomain 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.

If the curl returns an error message like "can't connect to host" or "500 internal server error", then the issue is with 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't rate limiting or blocking IP requests from the CloudFlare IPs and ask them to whitelist the IP addresses below:

204.93.240.0/24 (204.93.240.0 - 204.93.240.255)
204.93.177.0/24 (204.93.177.0 - 204.93.177.255)
199.27.128.0/21 (199.27.128.0 - 199.27.135.255)
173.245.48.0/20 (173.245.48.0 - 173.245.63.255)
103.22.200.0/22 (103.22.200.0 - 103.22.203.255)
141.101.64.0/18 (141.101.64.0 - 141.101.127.255)
108.162.192.0/18 (108.162.192.0 - 108.162.255.255)
190.93.240.0/20 (190.93.240.0-190.93.255.255)
2400:CB00:/32 (2400:CB00:0000:0000 - 2400:CB00:FFFF:FFFF)
2606:4700:/32 (2606:4700:0000:0000 - 2606::4700:FFFF:FFFF)
2803:f800:/32 (2803:f800:0:0:0:0:0:0 - 2803:f800:FFFF:FFFF)
3) Make sure that you're operating off of the most recent versions of Bad Behavior or mod_security. mod_security's core rules aren't blocking CloudFlare requests.

Jolie Rouge
07-20-2012, 03:14 PM
A "bug" in the system after yesterday's maintaince...

pepperpot
07-21-2012, 07:50 AM
Is anyone working on this? :shrug:

BeanieLuvR
07-22-2012, 02:21 PM
I hope someone fixes it soon. I can't use search to look for RTV shows. :( I get an error message.

pepperpot
07-24-2012, 02:47 PM
:elefant: Yay, we're fixed! :)

Jolie Rouge
07-24-2012, 02:52 PM
:elefant: Yay, we're fixed! :)

:clapping :clapping :clapping

BeanieLuvR
07-24-2012, 03:40 PM
WooHoo! Great news! :D Thanks to whoever fixed it. :)

DAVESBABYDOLL
07-25-2012, 12:10 PM
Thank Brandon :)