Jerome

this really doesn’t tell me where to look to fix the problem… both CDN boxes are empty.

I’ve turned off BPS, and restored root .htaccess with wordpress default .htaccess, resubmitted my permalink structure just to be on the safe side, and boom, no more errors.

I’ve done a bit more digging, and I noticed that one of these such errors involved a referrer of yahoo image search. The user searched for an image, clicked one of mine, then proceeded to come to my site, where I was presented with a 403/500 page. (was a 403 error, and at the bottom it said “additionally, server encountered an error 500).

I’d post my error log for this specific example here, but due to the nature of content, I will have to go create a yahoo image search of something more acceptable and force this error to occur from my actions on yahoo. I’ll do this tomorrow.

So, I went to my security logs to notice that this plugin seems to have successfully blocked a direct hack attempt on my website:

>>>>>>>>>>> 403 GET or Other Request Error Logged - June 25, 2013 - 10:30 pm <<<<<<<<<<<
REMOTE_ADDR: 187.156.31.48
Host Name: dsl-187-156-31-48-dyn.prod-infinitum.com.mx
SERVER_PROTOCOL: HTTP/1.1
HTTP_CLIENT_IP:
HTTP_FORWARDED:
HTTP_X_FORWARDED_FOR:
HTTP_X_CLUSTER_CLIENT_IP:
REQUEST_METHOD: GET
HTTP_REFERER:
REQUEST_URI:  deleted
QUERY_STRING:
HTTP_USER_AGENT: MSIE9

I have root, ssh, whatever I need. back on topic, though, the code I posted above is the closest thing to what you showed me as your example.

This is slightly off-topic, but I’m finding it VERY frustrating that after almost every BPS upgrade, it decides to lock everyone out and send them to error page 403.

# Each directory to which Apache has access, can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# permissions.
#
<Directory />
   Options All -Indexes
   AllowOverride All
</Directory>

I have error logging for my server set to an ftp-accessible location already, thats how I found the errors.

I’ve figured out which of the 3 httpd.conf files are read upon boot, so I will head into it and make a couple edits, and see what I can do. I’m not exactly sure what’s triggering the errors though, so not sure I can replicate it.

I’m currently talking to my host about the fact that I have 3 different httpd.conf files on my server, and I am trying to figure out if they’re all read on boot or if just one is, and which one etc etc. So I’m right here with you, if you have any more suggestions please just reply here, I’ve email-subscribed to this thread.

I’m another one of the people suffering from this issue, and between the 2 servers I am running BPS on, only one of them actually has this condition.

So, I am going to compare php.ini and other files to see what the differences are, and report back.

Has anyone been able to obtain php error logs regarding this issue? I cannot, as for some reason the errors arent firing into my logs. I’m still trying to get that to happen.

EDIT: haha cybermike your post only showed up after I submitted mine. Was this the only error you have? It may very well be what the dev needs to fix this bug asap ??

Well, I eliminated the problem on one of my domains, (thank you SO much for the fix). I’ve got another domain that I need to fix this bug for, but other than that, I’d love to see an actual release fix from the developer so I am not bothered to do this on every site I run FWP on (which is dozens, mind you). I always use custom prefixes on db tables to enhance security, and this is the first time that’s shot me in my foot.

Testing this now, as I’ve cleared 100MB of error logs from this joke in the past few days.

Any fix coming from the developer on this one??

I’ve loaded 190MB files into Filebase before without an issue, both with the uploader and sideloader. Only recommendation I have for the Error -600 is to open .htaccess and put the following line in there, which will allow for a 200M max upload size:

php_value upload_max_filesize 200M

I personally believe that this is simply an “unsecure permissions” issue… take a minute to check your databases for rogue admin accounts… some may be named adminz, adminx, adminy, etc… if you are the only user or admin on your site, then you should have only one user row in your database.

Next, check your theme permissions. Upgrade your timthumb.php installations, and lastly, search all of your template files for any malicious code that may start with base64_decode, str_rot13(sp?), etc, as those may be your offenders. These injected codes are actually decoding a string that is POSTed to the infected page, which is in essence sending out all of the spam emails.

Please add custom mime types to the options menu… maybe right under the blacklist section. Thanks!

Following this topic as I need answers regarding the solution to this problem. The only plugin we use is Feedwordpress… do you use it too?

The blogs that are being affected are using the latest WordPress version.