WP Super Cache generating “access_compat:error” entries in error log

  • hastibe

    (@hastibe)


    3 years, 11 months ago

    Here are a couple examples:

    [access_compat:error] [pid ######:tid ##############] [client ##.###.###.###:#####] AH01797: client denied by server configuration: /home/user/mydomainname.com/wp-content/cache/supercache/www.mydomainname.com/index-https.html, referer: http://www.mydomainname.com/

    [access_compat:error] [pid ######:tid ##############] [client ##.###.###.###:####] AH01797: client denied by server configuration: /home/user/mydomainname.com/wp-content/cache/supercache/www.mydomainname.com/index-https.html

    I am seeing probably 100+ entries similar to these ones in my site’s error.log every day. I don’t know enough to understand what is going on here, so I reached out to my host, and they said to reach out to WP Super Cache support about them, as they always involve WP Super Cache’s /cache/supercache/ directory.

    Any insight that could be shared about these errors, why they are happening, and what can / should be done about them would be much appreciated!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Donncha O Caoimh (a11n)

    (@donncha)

    3 years, 10 months ago

    Sorry. I have no idea why that’s happening. Other people have access_compat problems with other software on their web servers so it’s not strictly related to wp-super-cache. It’s some configuration of your site. Sorry I can’t help much there.

    Thread Starter hastibe

    (@hastibe)

    3 years, 10 months ago

    Okay, thanks–I’ll circle back to our website host about the site configuration, and -just to clarify- when you say it’s some configuration of my site, you mean my server, right? That it’s some configuration of my server?

    Or, are you saying a website configuration setting (i.e. theme or plugin) could be causing this access_compat:error for WP Super Cache?

    Thread Starter hastibe

    (@hastibe)

    3 years, 10 months ago

    Well, just as an update from my host (DreamHost), they think it is the Mod Rewrite Rules inserted into the .htaccess file when using the “Expert” Cache Delivery Method that is causing the access_compat errors, but aren’t certain. For now, I have gone back to the “Simple” Cache Delivery Method, to see if the errors stop.

    Thread Starter hastibe

    (@hastibe)

    3 years, 10 months ago

    An update on my previous post, switching to the “Simple” Cache Delivery Method has eliminated the 100+ daily access_compat errors in the error.log. So, it seems like there is some incompatibility between DreamHost servers and the plugin’s “Expert” Cache Delivery Method (specifically the Mod Rewrite Rules inserted into the .htaccess file). If there’s any way this could be looked into with DreamHost (or that I could help with that), I would be appreciative.

    Plugin Author Donncha O Caoimh (a11n)

    (@donncha)

    3 years, 10 months ago

    It’s odd that it’s a problem with Dreamhost because I’m sure there must be many websites using this plugin in expert mode.
    If it works in simple mode then I think you should use it. It’s just as fast as expert mode unless your website is really taking a pounding in traffic.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘WP Super Cache generating “access_compat:error” entries in error log’ is closed to new replies.