OK, let's do a little Networking 101. 127.0.0.1 is an unroutable address (that means you'll never see it on the Internet) that *always* means the local host; in fact it's called 'localhost' in your 'hosts' file. For Linux this is /etc/hosts, for Windows it's in c:/windows/system32/drivers/etc/hosts. So anything running at 127.0.0.1 is only reachable by processes running on the same system. The error message "Firefox can't establish a connection to the server at 127.0.0.1:8000" means that your Django dev server is either not running at all *or* it is not running **on the same machine as Firefox.**
The error message "Error: That IP address can't be assigned-to." is from Django. It's in django/core/management/commands/runserver.py, line 84, and is returned when it gets the system error 99 (EADDRNOTAVAIL). It means that the machine you are on is not at the address 156.56.137.131. Do you know the external address of the machine you are on? How about the address/domain name of the machine your django dev server is on? This is important stuff to know. Let's say you do "python manage.py runserver 0.0.0.0:8000". This tells the dev server to make itself available on *all possible IP addresses* that the machine has. If you know the name/address of the machine you should be able to get to your server now. ... Unless there's a firewall between you and the server that does like unusual addresses, such as port 8000. Dealing with unknown firewalls is an incredibly frustrating thing because they are sort of like The Man Behind the Curtain -- they do stuff but you don't even know they exist. Talk to your instructor/sysadmin. So, one last question: You said "Could the fact that I am using a university computer make any difference (is there a way they can keep this from being used?) " Short answer: yes. The longer answer is based on the answers to a lot of questions: 1. What kind of computer are you on? 2. Are you typing at the console (ie. the keyboard is directly connected to the computer where you are trying to run Django) or are you logged in remotely using SSH (or Putty or something like that)? If you're at the console then the 127.0.0.1 should have worked. By the way, if you are on a remote machine and others are working on the same assignment you are, you may see the error "That port is already in use." in which case you can try 8001, or some other number above 1024. (Below 1024 you must be the root user to open that port.) 3. Does the system you are trying to run the dev server on permit you to have "long running processes"? Many hosting companies explicitly prohibit this and will auto-terminate anything that runs longer than N seconds. Ask you system administrator and/or course instructor. Bottom line: you need to get a better understanding of where your machine lives relative to the system you are trying to run Django on. Good luck! -- 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.
