Website subdirectories: httpd.conf or nameserver?

I have a web page up:
http://www.mustangengr.com , that seems to display OK.

Luckily, I have a hub on my DSL, so I've got two computers with different
IPs. I can surf index.html, but when I try to look at
http://www.mustangengr.com/richgrise , from the inside of the LAN it's
OK, but it puts http://10.0.0.1/richgrise in the address window, since
that's eth1 on the server, and, of course, when I try to access it from
the other port on the hub, which is outside, 4.11.176.118 vs. 4.11.176.232 ,
I get the error message:

An error occurred while loading http://www.mustangengr.com/richgrise:

Timeout on server
Connection was to 10.0.0.1 at port 80

So, clearly, I'm not configured right yet.

Now, in the last couple of days I've done a lot of reading about this,
(letting the public see a web site) and seem to remember having skimmed
past something about subdirecories, but was it in reading about DNS, or
was it in reading about Apache? ?:-|

FWIW, Slackware 10.0, Apache
The one thing I hate about these docs is that it's hard to know
exactly where to start looking, like you're standing at the door of
the Library of Congress, but there's no index. Or there's an index,
but you don't know the name of the doc you're supposed to get.

So, anyway, which path of discovery is more likely to yield an
answer sooner?

Thanks,
Rich

On Thu, 23 Dec 2004 18:00:22 +0000, Rich Grise wrote:

> FWIW, Slackware 10.0, Apache [and hit send prematurely]

Apache 1.3,

# rc.firewall Linux Firewall version 2.0rc9 -- 05/02/03
# http://projectfiles.com/firewall/
#
# Copyright (C) 2001-2003 Scott Bartlett <srb@mnsolutions.com>

and the rest essentially right out of the box.

Thanks!
Rich

On Thu, 23 Dec 2004 18:00:22 +0000, Rich Grise wrote:

> I have a web page up:
> http://www.mustangengr.com , that seems to display OK.
>
> Luckily, I have a hub on my DSL, so I've got two computers with different
> IPs. I can surf index.html, but when I try to look at
> http://www.mustangengr.com/richgrise , from the inside of the LAN it's
> OK, but it puts http://10.0.0.1/richgrise in the address window, since
> that's eth1 on the server, and, of course, when I try to access it from
> the other port on the hub, which is outside, 4.11.176.118 vs. 4.11.176.232 ,
> I get the error message:
>
> An error occurred while loading http://www.mustangengr.com/richgrise:
>
> Timeout on server
> Connection was to 10.0.0.1 at port 80
>
> So, clearly, I'm not configured right yet.

And it's a dynamic IP, being served by ns8.zoneedit.com and
ns17.zoneedit.com .

Thanks!
Rich

Rich Grise wrote:
> On Thu, 23 Dec 2004 18:00:22 +0000, Rich Grise wrote:
>
>
>>I have a web page up:
>>http://www.mustangengr.com , that seems to display OK.
>>
>>Luckily, I have a hub on my DSL, so I've got two computers with different
>>IPs. I can surf index.html, but when I try to look at
>>http://www.mustangengr.com/richgrise , from the inside of the LAN it's
>>OK, but it puts http://10.0.0.1/richgrise in the address window, since
>>that's eth1 on the server, and, of course, when I try to access it from
>>the other port on the hub, which is outside, 4.11.176.118 vs. 4.11.176.232 ,
>>I get the error message:
>>
>>An error occurred while loading http://www.mustangengr.com/richgrise:
>>
>>Timeout on server
>>Connection was to 10.0.0.1 at port 80
>>
>>So, clearly, I'm not configured right yet.
>
>
> And it's a dynamic IP, being served by ns8.zoneedit.com and
> ns17.zoneedit.com .
>
> Thanks!
> Rich
>
>
Are you certain that your ISP does *not* block port 80? I know that many
a large ISP does that just to keep possbile traffic "under control".

--

humjohn AT aerosurf DOT net

Hi Rich

In your httpd.conf file what is the ServerName directive set to?

If it's set to 10.0.0.1 then, as far as I know, Apache will use that as the
base for URLs. This works fine on your LAN but is no good from the
"outside" since 10.x.x.x is a private IP range.

You could try changing it to www.mustangengr.com or the public IP address to
see if that does the trick. Adding the port number on the end, eg
www.mustangengr.com:80 helps to tighten things up too from what I remember
reading.

Hope this helps

Tim.


"Rich Grise" <rich@example.net> wrote in message
news:pan.2004.12.23.17.12.50.991069@example.net...
>I have a web page up:
> http://www.mustangengr.com , that seems to display OK.
>
> Luckily, I have a hub on my DSL, so I've got two computers with different
> IPs. I can surf index.html, but when I try to look at
> http://www.mustangengr.com/richgrise , from the inside of the LAN it's
> OK, but it puts http://10.0.0.1/richgrise in the address window, since
> that's eth1 on the server, and, of course, when I try to access it from
> the other port on the hub, which is outside, 4.11.176.118 vs. 4.11.176.232
> ,
> I get the error message:
>
> An error occurred while loading http://www.mustangengr.com/richgrise:
>
> Timeout on server
> Connection was to 10.0.0.1 at port 80
>
> So, clearly, I'm not configured right yet.
>
> Now, in the last couple of days I've done a lot of reading about this,
> (letting the public see a web site) and seem to remember having skimmed
> past something about subdirecories, but was it in reading about DNS, or
> was it in reading about Apache? ?:-|
>
> FWIW, Slackware 10.0, Apache
> The one thing I hate about these docs is that it's hard to know
> exactly where to start looking, like you're standing at the door of
> the Library of Congress, but there's no index. Or there's an index,
> but you don't know the name of the doc you're supposed to get.
>
> So, anyway, which path of discovery is more likely to yield an
> answer sooner?
>
> Thanks,
> Rich
>

Rich Grise wrote:
> I have a web page up:
> http://www.mustangengr.com , that seems to display OK.
>
> Luckily, I have a hub on my DSL, so I've got two computers with different
> IPs. I can surf index.html, but when I try to look at
> http://www.mustangengr.com/richgrise , from the inside of the LAN it's
> OK, but it puts http://10.0.0.1/richgrise in the address window, since
> that's eth1 on the server, and, of course, when I try to access it from
> the other port on the hub, which is outside, 4.11.176.118 vs. 4.11.176.232 ,
> I get the error message:
>

I can see the page from external.
On my apache web server (www.rollingviolation.com) the listen line is:
Listen x.x.x.x:80
where x.x.x.x is the internal address (not the 24.x.x.x it resolves to.)

from the inside, I can't connect to www.rollingviolation.com - I use
"webbox" (the hostname) to connect. I believe it's because the fqdns
name resolves to the 24.x.x.x address and my Linksys refuses to pass
packets that way. (internal destined for external which is actually the
external IP of the linksys mapped back to a NATted port on the inside.)

If you design your site with relative links <a href="/">home</a> instead
of <a href="http://mustangengr.com/">home</a> it'll work no matter
where/what you call it.

But, I think you fixed it... I can see the page from here. :)

Ray

Rich Grise wrote:
> I have a web page up:
> http://www.mustangengr.com , that seems to display OK.
>
> Luckily, I have a hub on my DSL, so I've got two computers with different
> IPs. I can surf index.html, but when I try to look at
> http://www.mustangengr.com/richgrise , from the inside of the LAN it's
> OK, but it puts http://10.0.0.1/richgrise in the address window, since
> that's eth1 on the server, and, of course, when I try to access it from
> the other port on the hub, which is outside, 4.11.176.118 vs. 4.11.176.232 ,
> I get the error message:
>
> An error occurred while loading http://www.mustangengr.com/richgrise:
>
> Timeout on server
> Connection was to 10.0.0.1 at port 80
>

Check the page. Your index page works and your 404 error page works,
but I get the same error.

Ray

On Thu, 23 Dec 2004 19:10:26 +0000, Tim G wrote:

> Hi Rich
>
> In your httpd.conf file what is the ServerName directive set to?

It's www.mustangengr.com, now. ;-)

I just started down httpd.conf, and when I got to "This has to be a
[FQDN]...", I remembered that that's the part I always skipped over
before because I didn't have a FQDN.

Works now! :-D :-D :-D :-D :-D :-D !!!!

http://www.mustangengr.com/richgrise

Thanks!
Rich

On Thu, 23 Dec 2004 10:39:45 -0800, HJohnson wrote:

> Rich Grise wrote:
[couldn't get to subdirs at the time of writing OP]

> Are you certain that your ISP does *not* block port 80? I know that many
> a large ISP does that just to keep possbile traffic "under control".

Yeah, I got port 80 open day before yesterday, thanks to Antoine EMERIT's
assistance. :-)

And since my OP, I got to ServerName in httpd.conf. :-)

Thanks!
Rich

http://www.mustangengr.com this works fine... you are in California.

http://www.mustangengr.com/richgrise this does too from the outside.. saw
the picture etc.

Your sample address had a colon on the end which should not be there after
/richgrise

Check the gateway setting on the netcard. I assume you are using a NAT
router for the 10 subnet, so the gateway is the nat router IP, and not the
public ip.

"Rich Grise" <rich@example.net> wrote in message
news:pan.2004.12.23.17.12.50.991069@example.net...
> I have a web page up:
> http://www.mustangengr.com , that seems to display OK.
>
> Luckily, I have a hub on my DSL, so I've got two computers with different
> IPs. I can surf index.html, but when I try to look at
> http://www.mustangengr.com/richgrise , from the inside of the LAN it's
> OK, but it puts http://10.0.0.1/richgrise in the address window, since
> that's eth1 on the server, and, of course, when I try to access it from
> the other port on the hub, which is outside, 4.11.176.118 vs. 4.11.176.232
,
> I get the error message:
>
> An error occurred while loading http://www.mustangengr.com/richgrise:
>
> Timeout on server
> Connection was to 10.0.0.1 at port 80
>
> So, clearly, I'm not configured right yet.
>
> Now, in the last couple of days I've done a lot of reading about this,
> (letting the public see a web site) and seem to remember having skimmed
> past something about subdirecories, but was it in reading about DNS, or
> was it in reading about Apache? ?:-|
>
> FWIW, Slackware 10.0, Apache
> The one thing I hate about these docs is that it's hard to know
> exactly where to start looking, like you're standing at the door of
> the Library of Congress, but there's no index. Or there's an index,
> but you don't know the name of the doc you're supposed to get.
>
> So, anyway, which path of discovery is more likely to yield an
> answer sooner?
>
> Thanks,
> Rich
>