From owner-freebsd-isp@FreeBSD.ORG Fri Jul 11 17:53:25 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 44CD937B401 for ; Fri, 11 Jul 2003 17:53:25 -0700 (PDT) Received: from mail.westbend.net (ns1.westbend.net [216.47.253.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DF2643FBD for ; Fri, 11 Jul 2003 17:53:24 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from Admin02 (admin02.westbend.net [216.47.253.19]) by mail.westbend.net (8.12.9/8.12.9) with SMTP id h6C0rNHZ020118; Fri, 11 Jul 2003 19:53:23 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <01f001c3480f$fe94a690$13fd2fd8@Admin02> From: "Scot W. Hetzel" To: "Drew Tomlinson" References: <20030709180108.3B56B3BF415@blacklamb.mykitchentable.net><200307111728.40455.olivas@digiflux.org> <00aa01c347c4$59b19c00$6e2a6ba5@lc.ca.gov> Date: Fri, 11 Jul 2003 19:53:22 -0500 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 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) cc: FreeBSD ISP Subject: Re: mod_frontpage & UID/GID Settings 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 00:53:25 -0000 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. > 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: AllowOverride AuthConfig Limit Indexes Options to the VirtualHost settings for the FP admin pages. Scot