• 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 protection of / doesn't work since 18.0.59 when there is php

Linulex

Silver Pleskian
Server operating system version
Almalinux 8.9
Plesk version and microupdate number
Version 18.0.59
Using the built-in password-protected directories feature in Plesk

When an index.php exists the password protection of "/" gives errors 403.

when only index.html only exists, it works fine.

when password protection existed before the upgrade it kept working.

Did not test with other .php files

regards
Jan
 
I see it is the same problem as in


and it already has a bug number ID PPPM-14334

is there a place where i can follow the bug id's? This is a severe bug for us because websites that are still in development always get password protected.

regards
Jan
 
Is there any timeline for the fix or a workaround? We have more then 20 customers where PHP broke, all protected with Plesk's Protected directory.
 
There is no ETA, but the issue is definitely being worked on and it has a high priority. By experience from the past, such things are normally handled within days and published in a hotfix or the nearest minor update.
 
Workaround for us was just to disable the feature in Plesk and manually creating .htpasswd with entry in the .htaccess. Works without any issue for us.
 
Back
Top