• 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.

Apache Access control policy

kadoudal

Regular Pleskian
I created vhost with access control on a directory, but it seems that no control at all are performed.... (existing users and passwords in the AuthUserFile....) when reaching the URL http://www.mydomain.net/mysuburi

here is my /var/www/vhosts/mydomain.net/conf/vhost.conf

<Directory /var/rails/mydomain/dev/mysuburi/current/public >
AuthType Basic
AuthName "mydomainRepository"
AuthUserFile /etc/apache2/dav_mydomain.passwd
Require valid-user
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order deny,allow
Deny from all
Allow from all
</Directory>

which is strange, is that this AuthUserFile is used also to control the access to a subdomain (svn) and this time the control is performed when reaching the url "http://svn.mydomain.net/myproject"

/var/www/vhosts/mydomain.net/subdomains/svn/conf/vhost.conf

<Location /myproject >
DAV svn
SVNPath /var/svn/opticoaching/myproject
AuthzSVNAccessFile /etc/apache2/opticoaching_svn_access.rules
Require valid-user
AuthType Basic
AuthName "mydomainRepository"
AuthUserFile /etc/apache2/dav_mydomain.passwd
<LimitExcept GET PROPFIND OPTIONS REPORT>
Require valid-user
</LimitExcept>
</Location>

Am I missing anything important ? (I guess so, but what ? and where ?)

thanks for your help
 
Hi,

Make sure that /etc/apache2/dav_mydomain.passwd is readable to user/group httpd is running under (usually it is apache/apache).

Also try running
/usr/local/psa/admin/bin/websrvmng -v -a

to rebuild apache configs. Perhaps /var/www/vhosts/mydomain.net/conf/vhost.conf was simply not included - it should be included after websrvmng execution

If it does not help then try checking apache error log when accessing domain page:
/var/www/vhosts/mydomain.net/statisits/logs/error_log

Maybe this will give more clues.
 
Back
Top