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

Plesk 12, .htaccess/.htpasswd visible in web browser

Peter_Smith

New Pleskian
Hello,

Runing Plesk 12 on CentOS Apache/2.2.15. I'm able to view .htaccess and .htpasswd files on my sites in my browser. I've tried adding this to the .htaccess

<Files .htpasswd>
Order allow,deny
Deny from all
</Files>

<Files .htaccess>
Order allow,deny
Deny from all
</Files>​

, but it has no effect. I have another rule in the same .htaccess file:

<Files wp-login.php>
AuthUserFile /var/www/vhosts/blahblahblah.com/httpdocs/.htpasswd
AuthName "Private access"
AuthType Basic
require user blah
</Files>​

And this *does* work. So I know that the htaccess is being read.

In most default Apache configs I've seen, access to .htpasswd and .htaccess has been denied by default, and sure enough, when I check /etc/httpd/conf/httpd.conf:

<Files ~ "^\.ht">
Order allow,deny
Deny from all
Satisfy All
</Files>​

Any idea what's going on? As far as I know httpd.conf hasn't been edited manually, and the rest of the httpd config files are all automatically generated by Plesk.
 
Back
Top