apache errors after upgrade to wordpress 4.0

  • Resolved ropezg

    (@ropezg)


    10 years, 6 months ago

    Hello,

    I’ve been using BulletProof security for a year and I like how it works, it’s a great plugin!
    Today I upgraded my site to wordpress 4.0 and soon after I noticed a lot of the same errors appearing in the apache error_log (never had these errors before):

    (9)Bad file descriptor: /home/ropezg/public_html/wp-content/cache/page_enhanced/www.mysite.com/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable, referer: https://www.google.co.uk/

    These errors only started to appear today and my impression is that they’re connected to the upgrade (I didn’t do any other changes on the site).
    First realized that something is wrong when I started receiving resource down notifications from HostTracker Notifier. Asked my hosting support what’s happening and they found those errors in the log file.

    After I turned off the Booleproof mode (turned on Default mode) these errors have stopped.

    As I would like to continue using this great plugin, could you please give me any tips on how to get rid of the above mentioned errors?

    Thanks a lot!

    ps. I did google for a solution before posting this, but didn’t find anything helpful

    https://www.ads-software.com/plugins/bulletproof-security/

Viewing 6 replies - 16 through 21 (of 21 total)
  • Plugin Author AITpro

    (@aitpro)

    “…the last resort is to dissect the BPS htaccess code line by line in search for the unwanted redirect”

    I don’t believe that is necessary because there is not any other BPS htaccess code that would cause in infinite redirect loop. The error message is accurate and means literally – some code that has the capability to do redirects is looping back on itself or a redirect rule that was created is redirecting back on itself. So only .htaccess code such as: ErrorDocument, Redirect, RedirectMatch do redirects. What is a litte tricky is RewriteRule. It can “almost” be considered a redirect, but it is technically not a redirect >>> BUT using the R flag in a RewriteRule will cause/create a redirect.
    https://httpd.apache.org/docs/current/mod/mod_rewrite.html#rewriterule
    https://httpd.apache.org/docs/2.2/rewrite/flags.html#flag_r

    Thread Starter ropezg

    (@ropezg)

    I see…well the only other line that includes Redirect or RedirectMatch is:
    RedirectMatch 403 \.(htaccess|htpasswd|errordocs|logs)$

    so I could comment out that one?

    Plugin Author AITpro

    (@aitpro)

    I forgot about that rule so yep comment it out. I added some more info above because you can use a RewriteRule directive to create a redirect using the R flag. ??

    Thread Starter ropezg

    (@ropezg)

    hi
    Just a quick update:
    I commented the RedirectMatch 403 line
    and Turned Off mod security

    unfortunately, it didn’t help.
    I get 30-50 those error messages daily.

    will update if I find something else

    cheers!

    Plugin Author AITpro

    (@aitpro)

    …and Turned Off mod security. unfortunately, it didn’t help. I get 30-50 those error messages daily.

    If you are still seeing the same mod_security errors then mod_security was not actually turned off. You should check with your host at this point. It is probably some funky/whacky mod_security SecRule or SecFilter or some combination of W3TC, cloudFlare, BPS and mod_security that is causing the problem. your host can do this check/test.: “LogLevel debug to get a backtrace”.

    Thread Starter ropezg

    (@ropezg)

    ok, will continue investigating this with them
    thanks!

Viewing 6 replies - 16 through 21 (of 21 total)
  • The topic ‘apache errors after upgrade to wordpress 4.0’ is closed to new replies.