From owner-freebsd-isp@FreeBSD.ORG Sat Jul 12 07:49:30 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3181837B401 for ; Sat, 12 Jul 2003 07:49:30 -0700 (PDT) Received: from blacklamb.mykitchentable.net (65-37-71-4.bras01.elk.ca.frontiernet.net [65.37.71.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3909543FD7 for ; Sat, 12 Jul 2003 07:49:29 -0700 (PDT) (envelope-from drew@mykitchentable.net) Received: from tagalong (unknown [192.168.1.28]) by blacklamb.mykitchentable.net (Postfix) with SMTP id 6C4683BF594; Sat, 12 Jul 2003 07:48:56 -0700 (PDT) Message-ID: <006301c34884$cbd1e7c0$1c01a8c0@lc.ca.gov> From: "Drew Tomlinson" To: "Scot W. Hetzel" References: <20030709180108.3B56B3BF415@blacklamb.mykitchentable.net><200307111728.40455.olivas@digiflux.org> <00aa01c347c4$59b19c00$6e2a6ba5@lc.ca.gov> <01f001c3480f$fe94a690$13fd2fd8@Admin02> Date: Sat, 12 Jul 2003 07:48:56 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: FreeBSD ISP Subject: Re: mod_frontpage & UID/GID Settings - SOLVED X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2003 14:49:30 -0000 ----- Original Message ----- From: "Scot W. Hetzel" To: "Drew Tomlinson" Cc: "FreeBSD ISP" Sent: Friday, July 11, 2003 5:53 PM > From: "Drew Tomlinson" > > Thanks for your reply. Since it was a new install, I removed the ports > > and then installed the apache13-fp port. This time I tried it right > > "out of the box" and was able to use the FP client to access my root > > web. Then I added a few name-based virtual webs to httpd.conf, > > restarted apache, and then installed the extensions on them using the > > fp_install.sh script and that work as well. What I found interesting is > > that after that, any attempts to access the root web were directed to > > the virtual web listed first in httpd.conf. This is probably by design > > but I could find it in the apache docs. Anyway, I created another > > virtual web to point to my root web and listed it first. Now things are > > working as I expect. > > > No it's not by design. You should have been able to access the root web > with your web browser. The problem is that somehow the FrontPage client > access the wrong web. I had placed the following into the httpd.conf file: > > # This Virtual Host makes it so FrontPage will display pages from the > # root web. When multiple Listen directives are specified, Frontpage > # will try to access the pages from the wrong virutal host. This fixes it. > # > #NOTE: This Virtual Host Entry must be kept as the last _default_ > # virtual host entry. > # > # ServerAdmin webmaster@@@HOSTNAME@@ > # ServerName @@HOSTNAME@@ > # > > You would need to uncomment this entry before adding additional Virtual > Webs. Yes, I have that but I didn't understand exactly what it did. Thank you. I have uncommented the lines and made sure they appear after the "_default_:10865" entry for the admin pages. Everything is working great! > > However I can't access the admin pages installed on port 10865. I can > > access them from the FP client on port 80 in the root web > > (/usr/local/www/data) but not from > > /usr/local/frontpage/version5.0/admin-exe. I can also access them from > > the FP client for all of the virtual webs. Have you had any success > > with the port 10865 admin pages? I wonder what I'm missing, if > > anything? > > > Was the problem with verifying usernames/passwords? Try adding: Yes. > AllowOverride AuthConfig Limit Indexes Options > > to the VirtualHost settings for the FP admin pages. This solves it!!! Thank you again and thanks for the port. Drew