title: Connect refused in response to Django runserver
body: <p>Working my way through a <a href="https://docs.djangoproject.com/en/1.11/intro/tutorial01/#the-development-server" rel="noreferrer">Django tutorial</a>, I have run <code>django-admin startproject mysite</code>. Now I cannot get the next step to work. </p>
  
  <pre><code>$ python manage.py runserver
  
  &gt;&gt;&gt;
  $
  </code></pre>
  
  <p>where the blank line is where <code>Ctrl-C</code> was entered to break the loop.  The <code>&gt;&gt;&gt;</code> was the prompt I defined for the virtualenv. In other words, no output.</p>
  
  <p>Most importantly, I get a connection refused error when connecting to <code>http://127.0.0.1:8000</code>. I do not get the the "'Welcome to Django' page, in pleasant, light-blue pastel" as described in the tutorial.</p>
  
  <p>For other commands <code>python manage.py</code> works correctly. For example:</p>
  
  <pre><code>$ python manage.py check
  System check identified no issues (0 silenced).
  
  $ python manage.py shell --command 'import sys; print(sys.version)'
  3.5.0 (v3.5.0:374f501f4567, Sep 13 2015, 02:27:37) [MSC v.1900 64 bit (AMD64)]
  
  $/ python manage.py shell --command 'import django; print(django.__version__)'
  1.11.2
  </code></pre>
  
  <p>I am at loss for how explore further. I have tried:</p>
  
  <ol>
  <li>Using multiple browsers</li>
  <li>Varying the IP and port, including using <code>LOCALHOST</code>.</li>
  <li>Turning off the proxy</li>
  <li>Consulting other Stack Overflow, such as <a href="https://stackoverflow.com/questions/32634259/django-errno-111-connection-refused">here</a> and <a href="https://stackoverflow.com/questions/5802189/django-errno-111-connection-refused">here</a></li>
  <li>Rebooting my computer</li>
  <li>Exploring Chrome's log's. Perhaps someone else can get something valueable out of these: <a href="https://i.stack.imgur.com/M3Lc5.jpg" rel="noreferrer">Request Headers</a> &amp; <a href="https://i.stack.imgur.com/sjKRn.jpg" rel="noreferrer">Timing Diagram</a>.</li>
  </ol>
  
  <p>I am at loss for other steps to debug this problem.</p>