can't access apache from the world wide web
JRough
99.XX.XX.31.
Do you have to put the outside IP address in the listen port
directive?
Listen 99.XX.XX.31:80
My server doesnt' have a registered name.
Would I also put that port number in the ServerName directive?
ServerName 99.XX.XX.31:80
I have the ports unblocked on my router with ATT. I cannot access my
server from this number
99.XX.XX.31
What am I missing? Do I have to add passwords. If you can tell me
the document page number I'll read it.
I don't know where to start.
tia,
janis
Kees Nuyt
<jlr...@yahoo.com> wrote:
>I cannot access my apache web server with my outside IP address.
>99.XX.XX.31.
>Do you have to put the outside IP address in the listen port
>directive?
>Listen 99.XX.XX.31:80
This should be enough, it will listen on any IP address:
Listen 80
>My server doesnt' have a registered name.
>Would I also put that port number in the ServerName directive?
>ServerName 99.XX.XX.31:80
>
>I have the ports unblocked on my router with ATT.
Did you forward port 80 to the server's LAN address in the router
(NAT/PAT) ?
>I cannot access my server from this number
>99.XX.XX.31
>What am I missing? Do I have to add passwords. If you can tell me
>the document page number I'll read it.
>I don't know where to start.
Some routers don't know how to loopback NAT.
Set up your browser to use an external proxy (outside your LAN)
and try again. Using an external proxy forces the request to come
"from outside".
>tia,
>janis
--
) Kees
(
c[_] If voting could change the system, it would be illegal.
-- [#537]
JRough
On Oct 16, 3:27 pm, Kees Nuyt <k.n...@nospam.demon.nl> wrote:
> On Fri, 16 Oct 2009 12:10:48 -0700 (PDT), JRough
>
> >I cannot access my apache web server with my outside IP address.
> >99.XX.XX.31.
> >Do you have to put the outside IP address in the listen port
> >directive?
> >Listen 99.XX.XX.31:80
>
> This should be enough, it will listen on any IP address:
>
> Listen 80
>
> >My server doesnt' have a registered name.
> >Would I also put that port number in the ServerName directive?
> >ServerName 99.XX.XX.31:80
>
> >I have the ports unblocked on my router with ATT.
>
> Did you forward port 80 to the server's LAN address in the router
> (NAT/PAT) ?
ending range, which would be begin:80 end:80
and it lets me map it to somewhere on my local computer so I mapped it
to 80 on my local computer. Where else would I map it to?
> >I cannot access my server from this number
> >99.XX.XX.31
> >What am I missing? Do I have to add passwords. If you can tell me
> >the document page number I'll read it.
> >I don't know where to start.
>
> Some routers don't know how to loopback NAT.
> Set up your browser to use an external proxy (outside your LAN)
> and try again. Using an external proxy forces the request to come
> "from outside".
You may be on to something, I saw something about NAT in the error log
or I may be imagining it.
Do I set my browser to my external IP address or any IP address
outside 198.192.1.40. What do you mean
set it to something outside my LAN.
I
> >tia,
> >janis
>
> --
> ) Kees
> (
> c[_] If voting could change the system, it would be illegal.
> -- [#537]
e
JRough
>
> >I cannot access my apache web server with my outside IP address.
> >99.XX.XX.31.
> >Do you have to put the outside IP address in the listen port
> >directive?
> >Listen 99.XX.XX.31:80
>
> This should be enough, it will listen on any IP address:
>
> Listen 80
>
> >My server doesnt' have a registered name.
> >Would I also put that port number in the ServerName directive?
> >ServerName 99.XX.XX.31:80
>
> >I have the ports unblocked on my router with ATT.
>
> Did you forward port 80 to the server's LAN address in the router
> (NAT/PAT) ?
What does this mean, please explain, I don't think my router has a NAT/
PAT in the router.
I only have the option of forwarding it to a port on my local sever.
Should I forward it to port 80?
JRough
>
I'm lost on the proxy setting too. In Mozilla I have the option
manual proxy configuration. I set that to my outside IP address at
port 80. Is that right?
You said something outside my LAN. That is outside my LAN I think.
What else is outside my LAN? do you mean make up any IP address
outside my LAN so it redirects it away from my internal IP address
192.168.1.40? For example, 99.99.99.99? Do you mean any old IP
address?
thanks,
JRough
>
It also has an option for use this IP address for all protocols.
should I click yes?
JRough
>
I got the web site to work. The router wasn't forwarding the traffic
to my IP address because I didn't have use DHCP on. AT&T blocks it
unless you have DHCP on. I was using set the IP address maually.
Norman Peelman
Yeah, this makes things a real pain.... another option is to alter
the 'hosts' file.
--
Norman
Registered Linux user #461062
-Have you been to www.apache.org yet?-
Kees Nuyt
<jlr...@yahoo.com> wrote:
>On Oct 16, 3:27�pm, Kees Nuyt <k.n...@nospam.demon.nl> wrote:
>> On Fri, 16 Oct 2009 12:10:48 -0700 (PDT), JRough
>>
>> <jlro...@yahoo.com> wrote:
>> >I cannot access my apache web server with my outside IP address.
>> >99.XX.XX.31.
>> >Do you have to put the outside IP address in the listen port
>> >directive?
>> >Listen 99.XX.XX.31:80
>>
>> This should be enough, it will listen on any IP address:
>>
>> Listen 80
>>
>> >My server doesnt' have a registered name.
>> >Would I also put that port number in the ServerName directive?
>> >ServerName 99.XX.XX.31:80
>>
>> >I have the ports unblocked on my router with ATT. �
>>
>> Did you forward port 80 to the server's LAN address in the router
>> (NAT/PAT) ?
>
>
>What does this mean, please explain, I don't think my router has a NAT/
>PAT in the router.
>I only have the option of forwarding it to a port on my local sever.
That is what I mean.
>Should I forward it to port 80?
Yes, port 80 to 192.168.x.y (your PC), port 80
--
) Kees
(
c[_] Never put off till tomorrow
what you can ignore entirely.
-- [#447]
Kees Nuyt
Just for anyone else, bcz you apparently solved your problem
already:
Set up the connection properties in your web browser to LAN
connection and use a HTTP-proxy server.
Make sure you use a proxy that is not on your LAN. Best is to use
the proxy your provider offers (most still do).
Now every request of your browser to your WAN address (your
public IP) is forwarded to the proxy by the browser. The proxy
then forwards the reuqest back to you, so it comes from outside.
Your router should then forward it to the webserver in your PC.
This way the router doesn't have to know how to loopback requests
from your PC to your WAN address back to your PC.
--
) Kees
(
c[_] Unlike biological evolution. 'intelligent design' is
not a genuine scientific theory and, therefore, has
no place in the curriculum of our nation's public
school classes.
-- Ted Kennedy [#566]
Lone Locust of the Apocalypse
JRough <jlr...@yahoo.com> writes:
>I cannot access my apache web server with my outside IP address.
>99.XX.XX.31.
... you do realize that anyone who knows how to look at the
NNTP-Posting-Host: header can form a pretty good guess what your
XX.XX are?