• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Plesk 12.5.4 Centos7 http auth log spam

exospec

New Pleskian
Hi,

I have a strange issue on this new set up, I expect it is something simple, hopefully someone can help.

I have 'secured' httpdocs of a vhost with an htaccess file using something like this:

####
AuthUserFile /var/www/vhosts/exampledomain.com/.htpasswd
AuthGroupFile /dev/null
AuthName Authentication
AuthType Basic

require user exampleuser
####

This correctly prompts a user to enter username and password when first landing on exampledomain.com

It works correctly and the user is able to navigate the site as expected. However.. in the error_log, for every resource the user accesses, there are lots and lots of lines like:

[Wed Oct 12 13:54:58.690690 2016] [authz_user:error] [pid 19224:tid 140260008752896] [client xxx.xxx.xxx.xxx:38644] AH01663: access to xxxxxxxxxx failed, reason: user 'exampleuser' does not meet 'require'ments for user to be allowed access, referer: xxxxxx

I can't understand why I am getting these messages?

Thanks!
 
Could you please clarify, why you do not use default Plesk feature for Password Protected Directories for this purpose?
 
Thanks Igor,

When I use the Password Protected Directories feature, it does not apply the protection recursively. For example I have added protection to httpdocs, but it is not behaving recursively. It only pops up for authentication if I go directly to: domain.com/httpdocs

Any ideas? Thanks
 
Back
Top