2010
04.29

Just finished fixing two more sites that were giving 500 errors because of chmodded folders set to 777. I checked out one site at random and found an older install of wordpress running. As I’ve stated in the past you have to keep your installs up to date. Not doing so leaves the server open to potential exploits which in turn can cause the server to be compromised. That is why I offer to upgrade your wordpress installs whenever a new version comes out (minus 3.0 for now). All you have to do is submit a Support Ticket, send me an email or instant message on msn.
As you also know I made this mandatory and your given 48 hours to fix the problem (or have me fix it) before the account is suspended. To see the specific post I’m talking about click here.

2010
04.15

After the recent attacks one measure I’ve been meaning to activate is suPHP. Last week I activated it, and found one site that is a big forum to not work at all. So I turned it off. Last night I activated it again and fixed said forum.

In total I’ve fixed three accounts at this moment, the latest being another forum.

If any of your accounts have problems before contacting me make sure your files are not chmodded to 777 or 666. suPHP doesn’t like this instead leave them as 755 or 644.
If at this point your site still doesn’t work send in a support request and I’ll get it fixed asap.

2010
04.08

Update #2 April 9 @ 1:06pm It looks like the attacks have stopped, everything is working fine.

As you may have noticed throughout the past week the vps has experienced massive http floods. Preventative measures have been put in place. These measures are being updated frequently as the attacks persist.

Right now if one ip has 50 or more connections it is banned for thirty minutes. In most cases I have permanently banned them. As with everything there can be false positives. So if you can’t connect to your website please fill out the Support Form and your ip address will be unbanned..

I will post more updates as they come..

UPDATE #1 @ 9:56pm The server was rebooted as the new changes that were implemented today don’t seem to be doing anything.
The server techs don’t know if this is a software or hardware issue. The data centre is going to run tests and we should have a definitive answer soon.