• 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 Changed behavior regarding password protected directories.

webmasterfreya

New Pleskian
Server operating system version
Debian 10
Plesk version and microupdate number
18.0.59 update 2
Something (major) has changed regarding password protected directories.
I got a complaint from a user that she could not login anymore today on a certain subdirectory, but last week she could.

After an extensive search it turns out that one can now only logon at subdirectory level (eg /domain.com/maintenance/subsystem) when one has the same authorization (user/password) on the parent directory (/domain.com/maintenance).

I tested the logins for other users and the same problem occured. Only after granting rights at the parent directory the users can login.

Will be a lot of work to adjust to this changed behavior.

Questions:
So what has changed and why has it changed?
Could this have something to do with the thread "Resolved Protected directory not working for php files" ?
Can you recreate this problem?
 
I am not sure whether this should not be expected behavior. Normally, password protection works for the directory it was set for and subdirectories. I would not want to file this as a product issue unless it is analyzed on the affected system and confirmed by product management that it is not intended to be like this. Could you please open a support ticket and give support SSH access so that they can check it on the machine and also research internally whether this is an intended behavior?
 
I am not sure whether this should not be expected behavior. Normally, password protection works for the directory it was set for and subdirectories. I would not want to file this as a product issue unless it is analyzed on the affected system and confirmed by product management that it is not intended to be like this. Could you please open a support ticket and give support SSH access so that they can check it on the machine and also research internally whether this is an intended behavior?
Yes you are right. Normally or usually passwords protection works correctly.
 
Peter,

Thanks for your prompt reply. I do remember that in the (far) past it worked like it is working now.
Conclusion: it did not work like this in the last year or so (before 18.0.59) .
I've been busy adjusting to the current situation and this ticket can be closed as far as i'm concerned.
 
Back
Top