If it still doesn't work after doing what James suggested, you can look to see if python is actually 'listening' on port 8000.
>From an 'elevated' command prompt (start->type 'cmd', right-click 'cmd' and hit 'run as administrator') type 'netstat -abno > netstat.txt' and hit enter. Then type 'notepad netstat.txt' and you will see a list of all the ports and programs that are using them. Use the 'find' feature in notepad to look for a program running on '8000'. If you don't see Python, something is not working correctly. Occasionally you might see another app that is using the port. A few years back, Windows Small Business Server would occasionally seize random ports used by other applications for use for DNS queries. -A On Fri, Jan 16, 2015 at 11:52 AM, James Schneider <jrschneide...@gmail.com> wrote: > You should be running 'python manage.py runserver' from inside the > directory of your project root , not using the django-admin.py command. The > manage.py file should have been automatically generated when you created > the project using django-admin.py. I hadn't even realized that > django-admin.py supported the 'runserver' argument. It doesn't work for me, > but 'python manage.py runserver' runs fine (and is what is recommended in > the tutorial). > > It should look something like this: > >> $ cd <project root> > > $ python manage.py runserver >> Validating models... >> 0 errors found >> January 16, 2015 - 04:17:18 >> Django version 1.6.6, using settings 'project_name.settings' >> Starting development server at http://127.0.0.1:8000/ > > Quit the server with CONTROL-C. > > > The command should 'hang' without displaying any errors if it is running > correctly. It stays open to accept HTTP requests to http://127.0.0.1:8000. > As you make requests, they should show up under the command with the URL's > that you are requesting and the response codes from the development server. > > See the section here: > https://docs.djangoproject.com/en/1.7/intro/tutorial01/#the-development-server > > -James > > > On Jan 16, 2015 10:02 AM, "KamalKanta Majhi" <aagust...@gmail.com> wrote: > >> Hi Kirby, >> >> Thanks for the reply. The same Error is throwing at >> http://localhost:8000/ . >> >> >> -- Kamal >> >> On Friday, January 16, 2015 at 10:27:51 PM UTC+5:30, C. Kirby wrote: >>> >>> Try localhost:8000 >>> >>> >>> On Friday, January 16, 2015 at 8:51:50 AM UTC-6, KamalKanta Majhi wrote: >>>> >>>> I h'v just run the django-admin.py runserver command to setup django >>>> dev server. But dev server is not running at http://127.0.0.1:8000/. >>>> Also i h'v tested at http://0.0.0.0:8000/ and >>>> http://192.168.0.106:8000/. Throwing same error like below screen >>>> shot. Please help if anybody already resolved the same. >>>> >>>> >>>> <https://lh3.googleusercontent.com/-jIDRD7NFOo4/VLkiqW8wIxI/AAAAAAAAAT4/XvE62OCgbEo/s1600/django-error.png> >>>> >>>> >>>> -- Kamal >>>> >>>> >>>> >>>> On Monday, August 27, 2012 at 1:23:23 PM UTC+5:30, nav wrote: >>>>> >>>>> Dear Folks, >>>>> >>>>> I am running my django development server on 127.0.0.1:8000 and >>>>> accessing this address from my web browser on the same machine. In the >>>>> past >>>>> few days I have found thet the web browsers keep prepending the address >>>>> with "www." when using the above address. 127.0.0.1 without the prot >>>>> number >>>>> works fine but the django development server requires a port number. >>>>> >>>>> I have not encountered this problem before and am puzzled by what is >>>>> happening. I am working on a Kubuntu 12.04 linux box and my /etc/hosts/ >>>>> file is below if that helps: >>>>> >>>>> ==================== >>>>> 127.0.0.1 localhost >>>>> 127.0.1.1 <mymachinename> >>>>> >>>>> # The following lines are desirable for IPv6 capable hosts >>>>> ::1 ip6-localhost ip6-loopback >>>>> fe00::0 ip6-localnet >>>>> ff00::0 ip6-mcastprefix >>>>> ff02::1 ip6-allnodes >>>>> ff02::2 ip6-allrouters >>>>> ==================== >>>>> >>>>> TIA >>>>> Cheers, >>>>> nav >>>>> >>>> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-users+unsubscr...@googlegroups.com. >> To post to this group, send email to django-users@googlegroups.com. >> Visit this group at http://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/cc0c84af-b413-4a76-a572-b3498ff350c4%40googlegroups.com >> <https://groups.google.com/d/msgid/django-users/cc0c84af-b413-4a76-a572-b3498ff350c4%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/CA%2Be%2BciVUP4FKrqr05R%3DS1r%2Bvm5xrHzhFMO4Bttv4%2ByD56Jd0aA%40mail.gmail.com > <https://groups.google.com/d/msgid/django-users/CA%2Be%2BciVUP4FKrqr05R%3DS1r%2Bvm5xrHzhFMO4Bttv4%2ByD56Jd0aA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAEE%2BrGpZLv5u%2Bs3P0n0XxLtqPzvHK%3DfA5ch1UJ77v_GHgF%2BbSg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
