Directory protection not working

N1ghteyes

Active Member
Mar 3, 2014
33
2
8
Reading, UK
cPanel Access Level
Root Administrator
Twitter
As per thread title, In Cpanel 54.01, when trying to protect a directory through the directory privacy option with the Paper Lantern theme, the request isn't completed fully.

After a few mins of working through this I discovered the following:-
- The passwd file is created correctly, in the correct location
- It is given the correct permissions
- The htaccess file is not correctly updated with the required Auth rules
- Manually editing the htaccess file is possible, though hardly ideal for less technical users.

I couldn't get this to work with any set of permissions settings on the .htaccess file.
 

N1ghteyes

Active Member
Mar 3, 2014
33
2
8
Reading, UK
cPanel Access Level
Root Administrator
Twitter
to manually fix, add the following to your .htaccess (replacing where appropriate):

AuthType Basic
AuthName "<YourUsername>"
AuthUserFile "/home/<Account>/.htpasswds/public_html/<foldername>/passwd"
require valid-user
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,201
363
Hello :)

I'm unable to reproduce this issue in cPanel version 54.0.7. It's scheduled for publication to the "Current" build tier later today. Could you verify if the issue persists after updating to this version?

Thank you.
 

N1ghteyes

Active Member
Mar 3, 2014
33
2
8
Reading, UK
cPanel Access Level
Root Administrator
Twitter
Hi Michael,

No luck I'm afraid. Upgraded to 54.0.7 and the issue persists. Tested on both the X3 and paper lantern themes, and on a couple of different accounts.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,201
363
Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome.

Thank you.
 

N1ghteyes

Active Member
Mar 3, 2014
33
2
8
Reading, UK
cPanel Access Level
Root Administrator
Twitter
I'm getting:
The provided IP (5.133.180.184) and support access id do not match.

When using the support ID located on WHM, for the hostname I'm using....