• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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