Web Server on MBL - With .htaccess

Legacy Products My Book Live
1

Following posts here and elsewhere, I easily set-up a Web Server on my My Book Live.

Since I only want to allow access to it to remote family members, I need to password protect it using Apache .htaccess.

However, for the life of me, I can’t make it work.  I’ve search the web, and found various options, but wind up with the same result.  It works fine without configuring apache for htaccess.

When I try enabling it, I get a browser message “The server encountered an internal error or misconfiguration and was unable to complete your request.”. 

When I check the Apache site 's log , I get:

    [Tue Jun 30 21:47:50 2015] [crit] [client x.x.x.x] configuration error:  couldn’t check user.  No user file?: /

The Apache2.conf has the following at the end if it:

  <Directory “/shares/Public/WWW/page”>
    Options Indexes Includes FollowSymLinks MultiViews
    AllowOverride AuthConfig
    Order allow,deny
    Allow from all
    AuthType Basic
    AuthName “PasswordRequired”
    AuthUserFile /home/secure/lpasswds
    Require valid-user  
 

I have tried modifying the apache2/sites-available, or using a .htaccess file instead.  The results are always the same.

I have been assuming that the issue is that apache can’t access the htpasswd-created passwd-file.  I then changed the file security, and then tried moving the password-file to different folders, including the web page folder.

Even if I deliberately change the lpasswds filename to something else, causing a deliberate error, the message is still the same.  So it’s either something else, or it’s a pretty general message.

After any Apache configuration change, I’ve executed a:

    /etc/init.d/apache2 reload

Has anyone successfully used Apache .htaccess to password protect a MBL served website?  Any idea what I may be doing wrong?

Thanks for any suggestions you can offer.

2

Install FeaturesPackManager, as it has an https webserver called AccessBook.   Then you can look around in it’s code to reverse engineer what you are looking for.

3

Thanks for the suggestion, Wdlive76.

Actually, I already tried that.  I specifically looked at the “private web server” part, hoping that would do the trick.  However, they utilized a certificate, not .htaccess.  And the “public web server” version had no security at all.

I briefly looked at the AccessBook part, which is a file-server, as I understand it, and so would use different security features, wouldn’t it?

4

accessbook is https webaccess running on apache.  Can create as many users as required with unique pwrds and unique access to different parts of the directories as required.

5

Ok.  Thanks again!

I’ll give it a shot on the weekend.