Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Jul 2003 10:16:24 +0100
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        Fredrik =?iso-8859-1?Q?Carl=E9n?= <baterista@arrhythmetic.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: apache doesn't reply on explicit hostname
Message-ID:  <20030708091624.GB3700@happy-idiot-talk.infracaninophile.co.uk>
In-Reply-To: <WorldClient-F200307080935.AA35060488@arrhythmetic.net>
References:  <WorldClient-F200307080935.AA35060488@arrhythmetic.net>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
On Tue, Jul 08, 2003 at 09:35:06AM +0200, Fredrik Carlén wrote:
> Hello! I have apache 2.0 on my  
> "# uname -a 
> FreeBSD al-khwarizmi.intra.arrhythmetic.net 5.0-RELEASE FreeBSD 
> 5.0-RELEASE #0: Thu Jan 16 22:16:53 GMT 2003     
> root@hollin.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC  i386"-system 
> :) 
>  
> Apache replies to http://localhost, but not to 
> http://al-khwarizmi.intra.arrhythmetic.net which is the full name for my 
> system. How come? "ServerName al-khwarizmi.intra.arrhythmetic.net:80" is 
> in my httpd.conf, sure enough. This doesn'nt work, either: 
>  
> "# telnet al-khwarizmi.intra.arrhythmetic.net 80 
> Trying 192.168.0.2... 
> telnet: connect to address 192.168.0.2: Connection refused 
> telnet: Unable to connect to remote host" 
>  
> Why is this? Could anybody help me. You're always very helpful on this 
> list... 

Sounds like apache is not listening on your network interfaces.  By
default, the apache config will have a line:

    Listen 80

which means 'bind to all network interfaces and listen on port 80', so
it should work unless you've modified that part of the httpd.conf
file.  Check to see if apache is listening on the right port by using
netstat.  Run:

    % netstat -na | grep '\.80 '

You should see a line like:

    tcp4       0      0  *.80                  *.*                    LISTEN

If apache is listening on your network interfaces, then check any
firewall rulesets you may have in place.  Chances are you're
inadvertently filtering out the incoming connection.

	Cheers,

	Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQE/CovodtESqEQa7a0RAunmAJ4iuyT4j1orQ2z2m1lpt/ojtRp+RgCfUvD4
6iboisX/8G2liBw2fNnjc+8=
=Huvj
-----END PGP SIGNATURE-----

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030708091624.GB3700>