Skip to main content

access_compat:error

Comments

7 comments

  • Infopro
    Whats your .htaccess file look like? This isn't a vBulletin issue I don't think, it's an Apache issue with your custom .htaccess if I was to guess.
    0
  • Robert WJ Cull
    My root .htaccess file essentially does not exist anymore and what is there is commented out. I am attaching it anyway. The one from my forums is also attached. After reading you post, I have uncommented 'Options -MultiViews' to see if that has an affect on it. Thanks for looking. Bob
    0
  • cPanelMichael
    Hello :) This is typically noticeable after upgrading to Apache 2.4. Please see the following Apache document: [url=http://httpd.apache.org/docs/2.4/upgrading.html]Upgrading to 2.4 from 2.2 - Apache HTTP Server Version 2.4 Are you using a custom VirtualHost for this domain name? Have you reported the issue to your hosting provider? Thank you.
    0
  • Robert WJ Cull
    I noticed the reports of problems after the upgrade regarding 'allow, deny, require' and wondered if that might be my problem. Yes, I am using a Virtual Host. I have reported the problems and they are constantly working of fixing them (so often that I feel like a nuisance). This one (among others) seems to not get fixed. I never used to have to complain to my support, but I seem to be constantly now:( Between mod security and apache upgrades they keep me having problems. I have suggested they consider moving me to a newer server, but I don't think they gave it any real consideration, I've probably been with them for close to 15 years. It may be time for a move, but when you don't know where to go, that can be scary too. Thanks
    0
  • cPanelMichael
    Feel free to update us with the outcome after your most recent attempt to have them resolve this issue. Thank you.
    0
  • Robert WJ Cull
    I have looked at the IP address' that are associated with the errors and find that most are from China and the ones that are not are also from questionable sources. I am wondering if my host has blocked some IPs and that is causing the error.
    0
  • cPanelMichael
    Assuming you have verified it's not caused by your .htaccess rules, the next place to check is the VirtualHost for the domain name. You can't check that without root access, so you may want to have your provider verify if it's using entries supported with Apache 2.4. Thank you.
    0

Please sign in to leave a comment.