Protected Directorie redirects to error 500

Username (e.g. epiz_XXX) or Website URL

epiz_32851721

Error Message

500 Internal Server Error
Something on the website crashed!

Other Information

When I try to use the Protected Directories feature from my account management page, everything goes fine, I create a user and all no errors. Then when I try to access the protected directory through its url, instead of asking for the user and password it throws 500 Internal Server Error. Before protecting the directory, all was working fine, html page, and php form handler.

What could it be?

1 Like

Hi and welcome to the forum

Something in the .htaccess file itself
probably some code that is not valid

Can you give us the content of the .htaccess file that is in that particular folder that is protected?

  1. open (EDIT) .htaccess file with file manager (monstaFTP)
  2. copy-paste content here

Or leave everything and wait for the admin who will investigate the problem
because it is in his interest to correct it if there is a bug.

4 Likes

Ok than, here is the .htaccess content.

# BEGIN InfinityFree Directory Protection
# DO NOT EDIT - YOUR CHANGES WILL BE OVERWRITTEN
AuthType Basic
AuthName "Login Required"
AuthUserFile "/home/vol11_4/epizy.com/epiz_32851721htdocs/restricted_page/.htpasswd"
Require valid-user
# END InfinityFree Directory Protection

Something seems to be off, because somethimes it asks for the user and password but after it insert it, redirects to infinity free’s 500 error page.

Thanks for the answer by now.

1 Like

@viniSouza let’s put a slash here /

image




copy-paste this code (overwrite the existing one !)
and press save (in file manager)

# BEGIN InfinityFree Directory Protection
# DO NOT EDIT - YOUR CHANGES WILL BE OVERWRITTEN
AuthType Basic
AuthName "Login Required"
AuthUserFile "/home/vol11_4/epizy.com/epiz_32851721/htdocs/restricted_page/.htpasswd"
Require valid-user
# END InfinityFree Directory Protection

And let me know if you still have the E-500

6 Likes

It’s working now, thanks a lot.

But still, it was not my code, it was straight from the management page feature. So some one probably need to take a look on that. Thanks again, best regards!

4 Likes

Thanks for the feedback :slight_smile:
We will certainly investigate the cause.

5 Likes

I investigated it. This was indeed a bug in our generated code. A fix is being prepared right now though and should be life in less than an hour.

7 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.