• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Password Protected Directory not working

chubba

New Pleskian
Hi All,

Just upgraded to Obsidian and password protection on directories seems to be failing. Here's an example of the plesk-stat folder:
1585055406105.png

If I hit the page on the site /plesk-stat I get an nginx 404. It looks like the htpasswd stuff is all correct in the confs and the password files are there but the page won't load. Remove the folder protection and the page loads. Any idea why the password request isn't being passed over to Apache correctly by nginx?

Just tested on another site on the server and it's working fine, just appears to be an issue with this one domain...
 
I had following error with password protection:
I added password protection in Plesk but the folder didn't get protected. After analysing Plesk logfiles, Plesk didn't regenerate the Apache/Nginx configuration files of the Domain.
To force Plesk to do so, I entered in the configuration of Apache/Nginx under the Domain Panel, introduced a " " in the file and saved it.
This has forced Plesk to update the configuration files but NOT to restart Apache/Nginx!!!! Only after manually restarting Apache (thru Plesk Management Button) the password protected folder was finally protected!
 
Back
Top