Re: Development Server Ignores IP-address Parameter

2015-07-16 Thread Ted Thomas
Jonathan, anotherdjangonewby, Thanks. I tried both suggestions, but there in no change in behavior. No matter what I do, the development server only takes requests at 127.0.0.1:8000. I am including my settings.py file below ( with altered secret_key): """ > Django settings

Re: Development Server Ignores IP-address Parameter

2015-07-16 Thread anotherdjangonewby
When switching to debug=False I had also problems connecting my debug-server. For me I had to specify the server IP-address in the settings: ALLOWED_HOSTS = ['localhost', '127.0.0.1', '192.168.1.21'] Maybe this helps. Kai Am 16.07.2015 um 20:28 schrieb John : try: python manage.py [::

Re: Development Server Ignores IP-address Parameter

2015-07-16 Thread John 
try: python manage.py [::]:8001 django will accept any requests on that port (localhost:8001, 127.0.0.1:8001, 192.168.0.102:8001) > On Jul 16, 2015, at 3:26 PM, tdthoma...@gmail.com wrote: > > Sadaf, > > Thanks for your reply. To be clear, my objective is to run tests with other > computers

Re: Development Server Ignores IP-address Parameter

2015-07-16 Thread tdthomas93
Sadaf, Thanks for your reply. To be clear, my objective is to run tests with other computers behind my firewall. Hence the 192.168.0.102 address which will only work on my local network. I tried your idea of specifying 0.0.0.0:8000, but that did not work. The development server still runs w

Re: Development Server Ignores IP-address Parameter

2015-07-16 Thread Sadaf Noor
Actually if you run your django at 0.0.0.0:8000 at your server pc which has a ip 192.168.0.102 > ./manage.py runserver 0.0.0.0:8000 then from another pc of the same network (as 192.168.0.102 is a local ip) if you type http://

Development Server Ignores IP-address Parameter

2015-07-15 Thread tdthomas93
For some reason, my Django Development Server ignores the IP:Port parameter when I start it. No matter what I enter for that parameter, it always uses 127.0.0.1:8000. I think (but am not sure) this started happening when I upgraded from Django-1.7 to Django-1.8.2. I am running on Slackware Lin