From owner-freebsd-questions@FreeBSD.ORG Sat Feb 4 18:21:28 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67BFB16A420 for ; Sat, 4 Feb 2006 18:21:28 +0000 (GMT) (envelope-from robin@reportlab.com) Received: from smtp1.freeserve.com (smtp1.wanadoo.co.uk [193.252.22.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B24943D49 for ; Sat, 4 Feb 2006 18:21:26 +0000 (GMT) (envelope-from robin@reportlab.com) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3008.me.freeserve.com (SMTP Server) with ESMTP id CE1BD1C0008F; Sat, 4 Feb 2006 19:21:25 +0100 (CET) Received: from [81.78.122.102] (modem-2662.hyena.dialup.pol.co.uk [81.78.122.102]) by mwinf3008.me.freeserve.com (SMTP Server) with ESMTP id EAB7F1C00086; Sat, 4 Feb 2006 19:21:24 +0100 (CET) X-ME-UUID: 20060204182124961.EAB7F1C00086@mwinf3008.me.freeserve.com Message-ID: <43E4F0AC.10201@jessikat.fsnet.co.uk> Date: Sat, 04 Feb 2006 18:21:32 +0000 From: Robin Becker User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: je killen References: <43E4AB18.3000900@jessikat.fsnet.co.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Invisible port 80 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Feb 2006 18:21:28 -0000 je killen wrote: > > On Feb 4, 2006, at 5:24 AM, Robin Becker wrote: > >> I am in the process of setting up a pair of freebsd 6.0 servers with >> different hosting services. On one of the servers I cannot seem to >> access the apache server which I have started. I can access port 80 on >> the machine itself using the machine IP address, but from my office >> port 80 seems invisible. The other machine works exactly as expected. >> >> Can anyone suggest something simple that may be causing this? So far I >> have only been using ssh to communicate with the machine so perhaps >> have neglected some network setting etc etc. >> -- >> Robin Becker > > If you are using Apache check httpd.conf to make sure it is listening on > port 80 for the server as a whole or > the virtual host you want to connect to. > JK. ...... I just checked and the httpd.conf says it's listening on port 80 in the global section. The ServerName is set as ww.xx.yy.zz:80 and corresponds to the IP address. I see this in the netstat -an output tcp46 0 0 *.80 *.* LISTEN so I assume the machine is listening. -- Robin Becker