• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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