httpd connection refused message

httpd connection refused message

[Kevin J. Cummings]

Hi folks,
	My ISP renumbered their network Monday morning (at midnight) and my 
cable modem got hung.  I called tech support to get the cable modem to 
unhang, and my network came back with the new address (after I ifup'ed 
again).  My problem is that ever since then, whenever I try and access 
my home WWW page, I get the message:

	The connection was refused when attempting to contact kjchome.homeip.net:81

I am running apache on port 81 because my ISP is blocking port 80 access 
(thank you Code Red!).  This was working for a LONG time previous to 
this incident.

I have NO PROBLEM if I use an internal network name or IP address, but I 
cannot seem to use the eth1 network name or IP address.  I get a 
different error if I try the external address port 80 (which is due to 
the port 80 port blocking, no?)  So, what has changed so that I cannot use:

	httpd://kjchome.homeip.net:81

but access to this URL seems to work just fine for people on the other 
side of my cable modem?????

Have I misconfigured something (to the best of my knowledge, I haven't 
changed my apache configuration).

-- 
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us

Re: httpd connection refused message

[Keith Morse]

On Wed, 2 Oct 2002, Kevin J. Cummings wrote:

> Hi folks,
> 	My ISP renumbered their network Monday morning (at midnight) and my 
> cable modem got hung.  I called tech support to get the cable modem to 
> unhang, and my network came back with the new address (after I ifup'ed 
> again).  My problem is that ever since then, whenever I try and access 
> my home WWW page, I get the message:
> 
> 	The connection was refused when attempting to contact kjchome.homeip.net:81
> 
> I am running apache on port 81 because my ISP is blocking port 80 access 
> (thank you Code Red!).  This was working for a LONG time previous to 
> this incident.
> 
> I have NO PROBLEM if I use an internal network name or IP address, but I 
> cannot seem to use the eth1 network name or IP address.  I get a 
> different error if I try the external address port 80 (which is due to 
> the port 80 port blocking, no?)  So, what has changed so that I cannot use:
> 
> 	httpd://kjchome.homeip.net:81
> 


Some guesses are: 
	
	firewall rules are setup for old ipaddress

	webserver is still configured for old ip address

	tcp_wrappers is still configured for old ip address.  look at 
	/etc/hosts.allow or /etc/xinet.d/*.

Re: httpd connection refused message

[Carl]

>
>Some guesses are: 
>        
>        firewall rules are setup for old ipaddress
>
>        webserver is still configured for old ip address
>
>        tcp_wrappers is still configured for old ip address.  look at 
>        /etc/hosts.allow or /etc/xinet.d/*.

Could also be that you have your own DNS server running which hasn't been updated.

--
Carl

Re: httpd connection refused message

[Kevin J. Cummings]

Thanks to everyone who responded.  I finally today fixed the problem
(but not before my ISP renumbered my network *again*!  Turns out it was
a Mozilla cache problem.  When I cleared out Mozilla's caches,
everything was fine again.   Sigh!   Seems Mozilla somehow remembers the
old IP address of a cached page, even if it may have changed!  (I had a
9 day timeout on my cached pages.)

Kevin J. Cummings wrote:
 > Hi folks,
 >     My ISP renumbered their network Monday morning (at midnight) and my
 > cable modem got hung.  I called tech support to get the cable modem to
 > unhang, and my network came back with the new address (after I ifup'ed
 > again).  My problem is that ever since then, whenever I try and access
 > my home WWW page, I get the message:
 >
 >     The connection was refused when attempting to contact
 > kjchome.homeip.net:81
 >
 > I am running apache on port 81 because my ISP is blocking port 80 access
 > (thank you Code Red!).  This was working for a LONG time previous to
 > this incident.
 >
 > I have NO PROBLEM if I use an internal network name or IP address, but I
 > cannot seem to use the eth1 network name or IP address.  I get a
 > different error if I try the external address port 80 (which is due to
 > the port 80 port blocking, no?)  So, what has changed so that I 
cannot use:
 >
 >     httpd://kjchome.homeip.net:81
 >
 > but access to this URL seems to work just fine for people on the other
 > side of my cable modem?????
 >
 > Have I misconfigured something (to the best of my knowledge, I haven't
 > changed my apache configuration).
 >

-- 
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us