Now I understand you, Stuart. Thanks to both yours and Tom's advices i was
able to notice my network was fine and that still my apache did not get any
external requests. I suspected that my ISP was blocking the port 80 and so i
changed to 85 and everything is running smoothly.
Thank you very
The idea behind using telnet was simply to verify the network
connections - that the web server is listening on the correct port and
that your router was working correctly.
Stuart
I am not sure I got your suggestion and I don't have telnet working
but i have similar rules for django
I am not sure I got your suggestion and I don't have telnet working but i
have similar rules for django production server on port 8000 and ssh and
they works just fine from external hosts. Does that help?
Thanks.
2011/5/10 Stuart MacKay
> Can you telnet to the
Can you telnet to the web server: telnet 80
(assuming it is listening on port 80). That would at least tell you
whether your LAN setup was correct.
Stuart MacKay
Lisboa, Portugal
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to
I guessed that the problem was at my httpd.conf because i am a newbie at
apache configuration. But i looked at both logs you indicated and they show
absolutely no response to external request. I checked my router again and
the port 80 is forwarded to the right internal IP and the router firewall
On Tue, May 10, 2011 at 12:39 PM, Renato Beserra
wrote:
> Hi,
>
> I think I have a really basic problem but I didn't find a solution searching
> the web.
>
> I have a Django application running on my local apache, and I can access
> everything locally whitout any
Hi,
I think I have a really basic problem but I didn't find a solution searching
the web.
I have a Django application running on my local apache, and I can access
everything locally whitout any problems. But when i try to access it from an
external host, the server timeout.I guess it has
7 matches
Mail list logo