Solved

APACHE - PASSWORD/VIRTUAL HOST PRBLM ---)

Posted on 2000-02-24
8
229 Views
Last Modified: 2013-11-15
I am currently running APACHE as a web server and have configured .htaccess security files and the have worked propperly, that is they ask for a password when you come to a restricted area of the webpage. BUT ever since I have installed ANY virtual hosts it has not worked AT ALL ANYWHERE although the virtual host does. PLEASE SOMEONE HELP ME... thanks in advanced...
0
Comment
Question by:TENSOR
  • 5
  • 3
8 Comments
 
LVL 40

Expert Comment

by:jlevie
ID: 2556602
Do you mean that all user authentication stopped working, real and virtual instances? Or do you mean that the virtual hosts aren't honoring .htaccess files in their respective htdocs directories? Being able to see one of your virtual host config sections would help a lot in our being able to solve this problem.
0
 

Author Comment

by:TENSOR
ID: 2556696
############## THIS SECTION WAS ADDED BY SENTHIL - ###########
NameVirtualHost 63.194.81.67
<VirtualHost 63.194.81.67>
ServerName www.v-solve.com
DocumentRoot /somewhere/abc/html/
AccessFileName .htaccess
</VirtualHost>
########## LELANDSD.COM - SENTHIL #############################
<VirtualHost 63.194.81.67>
ServerAdmin fatalerror404@hotmail.com
ServerName www.lelandsd.com
DocumentRoot /somewhere/else/lelandsd/
AccessFileName .htaccess
</VirtualHost>
<VirtualHost 63.194.81.67>
ServerAdmin fatalerror404@hotmail.com
ServerName lelandsd.com
DocumentRoot /somewhere/else/lelandsd/
AccessFileName .htaccess
</VirtualHost>
################################################
0
 

Author Comment

by:TENSOR
ID: 2556698
Edited text of question.
0
 
LVL 40

Expert Comment

by:jlevie
ID: 2557334
First, you don't need to the "AccessFile" directive in each virtual host section. It's sufficient to declare it once in the global section. Typically one wants to have at the global level a piece like:

AccessFileName .htaccess
<Files ~ "^\.ht">
    Order allow,deny
    Deny from all
</Files>

Which defines the htaccess file name and prevents those files from being seen if the document directory is browseable.

The reason that your virtual hosts aren't requiring user authentication is that you've not told Apache to do so. Each directory to be protected must allow user authentication to be set up with an "AllowOverride Authconfig" directive. Also, there's a couple of other directives one should typically apply to a directory (especially a document root). So one of you virtual hosts should look like:

<VirtualHost 63.194.81.67>
ServerName www.v-solve.com
DocumentRoot /somewhere/abc/html/
<Directory />
    Options Indexes FollowSymLinks
    AllowOverride AuthConfig
    Order allow,deny
    Allow from all
</Directory>
</VirtualHost>
0
Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

 

Author Comment

by:TENSOR
ID: 2560161
Please post your awnsers as comments as the future, If they work I will acept it as an awnser...
0
 

Author Comment

by:TENSOR
ID: 2560185
I meant to accept that...please write it again and I will accept...
0
 
LVL 40

Accepted Solution

by:
jlevie earned 100 total points
ID: 2560295
First, you don't need to the "AccessFile" directive in each virtual host section. It's sufficient to declare it once in the global section. Typically one wants to have at the global level a piece like:

AccessFileName .htaccess
<Files ~ "^\.ht">
   Order allow,deny
   Deny from all
</Files>

Which defines the htaccess file name and prevents those files from being seen if the document directory is browseable.

The reason that your virtual hosts aren't requiring user authentication is that you've not told Apache to do so. Each directory to be protected must allow user authentication to be set up with an "AllowOverride Authconfig" directive. Also, there's a couple of other directives one should typically apply to a directory (especially a document root). So one of you virtual hosts should look like:

<VirtualHost 63.194.81.67>
  ServerName www.v-solve.com
  DocumentRoot /somewhere/abc/html/
    <Directory />
      Options Indexes FollowSymLinks
      AllowOverride AuthConfig
      Order allow,deny
      Allow from all
  </Directory>
</VirtualHost>
0
 

Author Comment

by:TENSOR
ID: 2560401
thanks!
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Problem We are doing a daily copy of data in file system in Linux manually and I want to automate the same . We need many features in this automation:    1. We want to be able to exit in case of errors    2. We want the copy to happen via …
Note: for this to work properly you need to use a Cross-Over network cable. 1. Connect both servers S1 and S2 on the second network slots respectively. Note that you can use the 1st slots but usually these would be occupied by the Service Provide…
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now