Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Jun 2005 01:52:15 +0000
From:      Chuck Robey <chuckr@chuckr.org>
To:        Sarath ER <sarath@linuxtechs.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Still trying to get my site up!
Message-ID:  <42BF5BCF.5060203@chuckr.org>
In-Reply-To: <42BF48EC.3050509@linuxtechs.net>
References:  <Pine.WNT.4.63.0506261904510.728@Treneq> <42BF48EC.3050509@linuxtechs.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Sarath ER wrote:

> Gerard Seibert wrote:
>
>> Thanks to several individuals, I have almost gotten my Apache2 server
>> working. Almost, but not quite.
>>
>> My ISP blocks port 80; therefore I am using a redirect from
>> DynDNS.org to redirect to an alias using port 9545.
>>
>> The 'beerstud.us' redirects to 'www2.beerstud.us:9545'
>>
>>> From my FreeBSD box, if I type: lynx http://beerstud.us, I see the 
>>
>>
>> following message: Using http://www2.beerstud.us:9545/. The
>> connection is made and the index.htm file is displayed.
>>
>> However, I am unable to reach this site from any other computer.
>> Eventually, the request will time out and I receive an error message
>> telling me that the site is not available.
>>
>> I am not sure what I am doing wrong at this point. I have posted the
>> following files if anyone feels ambitious enough to look them over
>> for me.
>
Sarath, I will see if I can rephrase some of this, and at least help
*MY* understanding.  If your ISP is blocking port 80, then the fix
absolutely must fall into one of two categories: either you can find out
how your ISP is blocking it, and do a workaround of that, or you must
have someone else perform a service for you, having the required URL
changed to be the correct base port (not 80, and I would myself choose
8080, if your ISP didn't block that also).  Nice thing about that, your
friendly apache-friend isn't going to lose any bigtime bandwidth,
because it's still being served from your machine, your friend is merely
serving to redirect the port, not actually
serve it.

Now, I will make the assumption here that the above paragraph is mostly
right.  You could use ethereal very simply to check and make sure of
it.  One screwup would be to have the redirect be close, but not
actually what it should be, and it's really, really easy to read and
check this.  I'd bet it as either a very likely thing to be, OR while
you do it, you are pretty likely to spot the real problem.  Go give it a
try.  Ethereal is such a great tool that you can't really lose here,
learning how to use it, you're looking at a win-win situation.

>>
>> httpd.conf     =    http://www.seibercom.us/FreeBSD/httpd.conf
>>
>> hosts        =    http://www.seibercom.us/FreeBSD/hosts
>>
>> This is the output from ifconfig -a
>> net-card.txt    =    http://www.seibercom.us/FreeBSD/net-card.txt
>>
>> resolv.conf    =    http://www.seibercom.us/FreeBSD/resolv.conf
>>
>> The 'hosts' file has a pretty good description of my network in it. I
>> double checked my router, and I believe it is configured correctly to
>> pass port 9545 through.
>>
> Hi,
>
> Just checked www2.beerstud.us:9545, the connection fails.. Are you sure
> that you have enabled port forwarding in the router?
>
> - Sarath
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe@freebsd.org"





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