Website Unavailable
-
WordPress.com website goes down continually. Been advised to have IP addresses whitelisted as host may be blocking access.
Thanks
David
-
Error reports from CDNProxy service as follows;
04/01 11:31:01 connect() failed (110: Connection timed out) while connecting to upstream dcwhyte.com GET / HTTP/1.1
04/01 11:29:31 connect() failed (110: Connection timed out) while connecting to upstream dcwhyte.com GET / HTTP/1.1
04/01 11:21:32 connect() failed (110: Connection timed out) while connecting to upstream dcwhyte.com GET /2012/09/28/global-warning-2/global-growth-2/ HTTP/1.1
04/01 11:06:07 connect() failed (110: Connection timed out) while connecting to upstream dcwhyte.com GET /2012/09/17/get-rid-of-jargon-once-and-for-all/?replytocom=12 HTTP/1.1
04/01 11:05:04 connect() failed (110: Connection timed out) while connecting to upstream dcwhyte.com GET /2012/09/17/get-rid-of-jargon-once-and-for-all/?replytocom=12 HTTP/1.11. 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:
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.
Here is a list of our IPs:
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
IPv6
2400:cb00::/32
2606:4700::/32
2803:f800::/32
2405:b500::/32
2405:8100::/32Can anyone help?
Daviv
-
Hi there – we are unable to support using CloudFlare for your WordPress.com site for several reasons:
1. Their method of pointing your domain to your WordPress.com site requires using an IP address or specific server, which we don’t support. Your site does not have a static IP address or specific server. Instead, requests to load your site are shifted between several IP addresses and servers in order to balance the demand on servers. This means that specifying an IP address or server won’t work.
2. The features of their cloud-based infrastructure simply duplicate the infrastructure already being provided to you by WordPress.com, such as:
– CDN’s (Content Delivery Networks) that deliver your site content from – he location closest to your visitor
– Caching/optimizing files for faster loading times
– Security measures protecting your site from denial of service attacks and other forms of hacking/malware
– Site stats, including search engine terms and incoming link referrers, that are easier to read than Google AnalyticsYou can direct your domain back to your WordPress.com blog by changing your name servers to:
NS1.WORDPRESS.COM
NS2.WORDPRESS.COM
NS3.WORDPRESS.COMIf your domain is registered with us, you can change your name servers following this guide: http://en.support.wordpress.com/domains/change-name-servers/
If there are other features you were interested in using via CloudFlare, besides the ones listed above, can you let me know more about what you’re trying to do? I’ll be happy to help you learn more about the equivalent feature on WordPress.com.
-
Thanks Kathryn. I eventually worked out that the name servers needed to be WordPress.com – thanks for the explanation re Cloudflare. Next time, I’ll go on the forum before considering any so-called enhancements!
Much appreciatedDavid
-
-
Hi Kathryn,
I cancelled the Cloudflare account – seems to me WordPress.com does everything anyway – no need to duplicate functions – received this response. Re the “Domains that are no longer using CloudFlare nameservers will be automatically deactivated after a period of inactivity.” statement won’t affect my website, right?
Message begins –
Dear CloudFlare user,CloudFlare noticed that you are no longer pointing to the CloudFlare service. This change means that your website is no longer receiving the benefits of CloudFlare’s caching and security features, so please change the name servers back if you would still like to have CloudFlare protect and speed up your website.
IMPORTANT NOTE: Domains that are no longer using CloudFlare nameservers will be automatically deactivated after a period of inactivity. CloudFlare settings and DNS records will be preserved and your domain can be reactivated at any time.
If you believe that this email was sent in error, or if you have additional questions, please contact us at: http://support.cloudflare.com/
If an issue with the CloudFlare service caused issues for your site that caused you to change name servers, please review our troubleshooting tips to resolve common problems here: http://blog.cloudflare.com/cloudflare-tips-troubleshooting-common-proble
If you still intend to keep using CloudFlare, then you need to change your name servers to the following:
DNS1: DAN.NS.CLOUDFLARE.COM
DNS2: ELLE.NS.CLOUDFLARE.COMTo do so, you can log in to your registrar or visit your CloudFlare account here: https://www.cloudflare.com/my-websites.html.
Your name servers now point to the following:
DNS1: NS2.WORDPRESS.COM
DNS2: NS3.WORDPRESS.COM
DNS3: NS1.WORDPRESS.COM
DNS4: [not set]
DNS5: [not set]If you have any questions, contact us at: http://www.cloudflare.com/contact.html
Message ends.Appreciate your thoughts.
David
-
Hi there, did you register your domain through CloudFlare? If so, and if CloudFlare won’t allow you to keep the name servers pointed anywhere other than CloudFlare, then you’ll want to transfer your domain to another registrar to ensure the mapping to your WordPress.com site keeps working.
-
Hi Kathy,
No – the domain is registered with Go Daddy via Google. I suspect Cloudflare is suggesting that if I no longer use them, the domain will be ‘deactivated’, i.e. no longer able to acccess their services. Website is working perfectly now. I also followed through with Google Webmaster tools “Fetch as Google” and retrieved the URL 3 times, and I haven’t received any “googlebot can’t access your site” messages since 26th March. So I think it’s ok now.
Thanks again for you support and input.
David -
- The topic ‘Website Unavailable’ is closed to new replies.
WordPress.com Forums 