Monastery Performance Tweaks

[ivor]

Yeah, there was only one for you Darlica, and Lindorm.  I don't think they stick in the logs for long....

[Aggie]

Lindorm would have a wide array of IP addresses I suppose as he travels in work and have computer access in several different locations all over Sweden...

Applies to me as well.  Except the Sweden part.

[ivor]

Shouldn't matter at all unless a machine on your network is a bot and you share IP Addresses...

[Sibling Zono (anon1mat0)]

A Swedish bot? 

[ivor]

People with glass fembots in their interwebs shouldn't cast pointers to void? 

[Griffin NoName]

I try to avoid voiding !

[Sibling DavidH]

Bart has asked me to tell everyone that he's having trouble logging on.  I am also having some trouble: the first log-on after a long absence - say, overnight - takes at least a minute and often longer.  Subsequent log-ons are quicker.
I've told Bart this and he'll have another go later.

[Swatopluk]

Same here. Refreshing also takes far longer than it should.

[Aggie]

Yes, it's been slow lately.  Seems worse in the evening (North America), but it might just be my home computer.

[Griffin NoName]

Yes, me too. It takes ages to throw up the index page. It's very frustrating. Is it the Cloud thing? Do we really need it?

Also, when I log off, it goes to page not found every time.

[ivor]

Ugh...  Everybody send me broken laptops so  I can get my business rolling and get back to civilization and put the server back up...

[Opsa]

Good idea! Send your broken laptops to MB so he can sell me one cheap! 

The internet has seemed quite slow this week, here, no matter what site I'm on. But it ebbs and flows.

[ivor]

There's no telling...  I could take CloudFlare off and it might be slower.

I guess I should expand on that statement about sending me broken laptops.  If you see one broken and it's cheap or free.  Buy it and send it to me.  Ship it cheap as possible.  UPS Ground or whatever.  Keep track of what you spend and I'll owe ya or send you one that works at some point.  If it's a good one I'll give you a cut.  If they're not so good but still usable I'll fix it and send it to whoever needs one on a priority needs basis to be worked out amongst yourselves. 

If I can just break momentum I'll be set and then we can get the monastery off DreamHost.

[ivor]

Apparently it is a Dreamhost or MB issue.  Anybody care to take a look at any of this stuff?  I'm swamped right now and some of these may be easy.

// To make sure it gets to the right person, please reply above this line
==================================================

Hi Darren,

Thank you for the email.

What's happening specifically? Given that we're not having any systems
issues right now, I'm wondering if your hosting provider is doing some rate
limiting? The error message being returned indicates that your hosting
provider is having issues (some tips below).

Also: I took a look at your DNS settings & you had things like mysql and
mail covered. I've changed these to gray clouds because you could have
performance issues with those enabled (more info here:
http://www.cloudflare.com/wiki/What_subdomains_are_appropriate_for_orange_/_gray_clouds%3F
)


1) You have blocked one of CloudFlare's IP addresses on your server or you
have a .htaccess rule in place that limit connections from some IPs.
CloudFlare acts as a proxy, so it is important not to block requests from
its IP addresses. If you have blocked any of the following IP addresses, you
should remove them from the list or whitelist them. CloudFlare's IP range
includes:

Ports used by CloudFlare: 80 and 443 (for SSL).

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)

If you're not running any blocking software on your own server, then the
most likely place the block is happening is with your *hosting provider*.
Ask them to whitelist our IP addresses below when connecting to your
network. You can tell them that you are operating behind a reverse proxy and
the correct visitor IP will be reported by the X-Forwarded-For header, which
they can use for abuse detection.

Ports used by CloudFlare: 80 and 443 (for SSL).

CloudFlare's IP ranges:

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)

By whitelisting the IPs, you'll have fewer issues in the future.

2) You are running some sort of protection software like BadBehavior or
mod_security that are blocking CloudFlare's servers access to your server.
Please make sure you're using an updated version of Bad Behavior and
mod_security.

3) Your backend server is down. In this case, CloudFlare will serve a page
from its cache with an alert at the top telling your visitor they are in
offline browsing mode. However, if CloudFlare does not have a page in its
cache, then your visitor will see this page.

4) Your firewall has rules set in iptables that could be blocking
CloudFlare. Please check your firewall to see if CloudFlare is allowed
access and that CloudFlare IPs aren't blocked.




On Mon, Feb 7, 2011 at 7:07 AM, Darren Dickerson <
tender+d08f60f4ff10a91ed33e3c43a9aa3ead7182cea64@tenderapp.com> wrote:



Support ticket thread: http://support.cloudflare.com/discussions/problems/4265-cffeedback-feedback-darren-dickerson?anon_token=fd795e24f3c74fcce73c5d7747f5fa2452000b66
Reply with #ignore to stop receiving notifications for this discussion.

[ivor]

Okay...  Worked out what it was between DreamHost and CloudFlare.  How's everything been running the past 24 hours or so?  Better?