Skip to main content

.htaccess AuthType not working, keeps prompting for password

Comments

7 comments

  • Moses Moore
    Something I didn't try was to use the cPanel interface itself to password-protect the directory. ...:2083/cpsess0000000000/frontend/x3/htaccess/dohtaccess.html?dir=%2fhome%2f Turned on the checkbox. Created a new user with a password that has more than five bytes. Here's the resulting .htaccess file: AuthType Basic AuthName "argle:bargle" AuthUserFile "/home/moses/.htpasswds/public_html/box/passwd" require valid-user ... and I'm still getting re-prompted for the password over and over again. So now I've done it the "right" way, using cPanel's own interface, and it still isn't working. This is infuriating.
    0
  • cPanelMichael
    Hello :) Do you notice any error messages in /usr/local/apache/logs/error_log when this happens? Thank you.
    0
  • Moses Moore
    Hello :) Do you notice any error messages in /usr/local/apache/logs/error_log when this happens? Thank you.

    Sorry, when I said "there is no message in the error.log file" I mean to say "there is no message in the error_log file." I did not mean to mislead you.
    0
  • cPanelMichael
    Could you confirm you reviewed /usr/local/apache/logs/error_log and not the "error_log" file in the account's public_html directory? Thank you.
    0
  • Moses Moore
    Could you confirm you reviewed /usr/local/apache/logs/error_log and not the "error_log" file in the account's public_html directory? Thank you.

    # tail /usr/local/apache/logs/error_log [Wed Sep 09 16:41:39 2015] [error] [client 198.100.144.83] File does not exist: /usr/local/apache/htdocs/robots.txt [Wed Sep 09 17:04:15 2015] [notice] Graceful restart requested, doing restart Is this what you are thinking of? This is what I meant.
    0
  • cPanelMichael
    Feel free to 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.
    0
  • cPanelMichael
    To update, this issue was resolved after the user determined Squid was intercepting traffic on eth0 port 80, that would take the 'Authentication:' http header, then pass it to localhost:80. It worked with "https" because Squid was not intercepting port 443. Thank you.
    0

Please sign in to leave a comment.