> First question: are you really running the development server on your
> local box?
Yes, definitely the local box. Well, let me clarify... I've got Python
and Apache on the local box but my Apache Web root is actually on a
share on another box (my file server). But I just point to /home/rob/
path/to/file/server/sites and everything's good. I've built a number
of Web apps using other tools, such as PHP and Drupal without any
issues.
> If you're sshing to another machine, then it won't work.
> 127.0.0.1 is always the machine it is referenced from. You can change
> where the development server is being run by locating your ip address
> (use the ifconfig command and look for the address associated with
> eth0), and running the dev server like this:
eth0 Link encap:Ethernet HWaddr 00:1C:25:10:A9:6B
inet addr:192.168.1.115 Bcast:192.168.1.255 Mask:
255.255.255.0
inet6 addr: fe80::21c:25ff:fe10:a96b/64 Scope:Link
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
Navigating to http://192.168.1.115:8000 fails with the same message.
So I don't think the local box vs remote box is the issue.
> Your /etc/hosts don't define ip addresses, they define hostnames-- it
> seems like you understood it backwards.
Ack. I think I knew that. Evidently not well enough. :)
So... still stuck.
r.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
