I checked and no proxy is in place. I tried the other IPs, two wouldn't let me assign it and the third went through but gave me the same error that I began with. How odd.
On Dec 8, 11:24 am, Shawn Milochik <sh...@milochik.com> wrote: > I don't think they can prevent you from using it locally. The fact that I can > ping the IP address you provided means that it's publicly available. This > either means that your machine has its own direct connection to the Internet, > or ipconfig returned multiple addresses, including the address of your > router, and you chose that one to try. > > It's probably the latter, because that would definitely cause the error you > showed from manage.py runserver. There should be a local IP address for your > machine as well. Just try the different ones ipconfig shows until manage.py > runsever works with it. I supposed it's possible that a proxy server is in > place in your browsers by default, although I'd expect them to ignore > 127.0.0.1. But out of curiosity, please check your Firefox settings to see if > any proxying is taking place. > > Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
