title: 404 on Nginx running on docker (uwsgi)
body: <p>I have been battling with this and can't get my head around it.</p>
  
  <p>I have a simple Dockerfile which works and I use <strong>supervisord</strong> as CMD to start nginx and uwsgi. And it does the job but I get back 404. So what I do is to instead <strong>start the docker with <code>/bin/bash</code> and manually start things and debug</strong>, e.g.:</p>
  
  <pre><code>sudo docker run -t -i -p 8095:80  myimage /bin/bash
  </code></pre>
  
  <p>So this is my nginx conf (in sites-available and then a link in sites-enabled):</p>
  
  <pre><code>server {
      listen 80;
      server_name 0.0.0.0;
  
      location / {
          include uwsgi_params;
          uwsgi_pass unix:/WikiRockWord2Vec/WikiRockWord2Vec.sock;
      }
  }
  </code></pre>
  
  <p>and this is my uwsgi ini:</p>
  
  <pre><code>[uwsgi]
  module = wsgi
  
  master = true
  processes = 5
  
  
  socket = /WikiRockWord2Vec/WikiRockWord2Vec.sock
  chmod-socket = 777
  vacuum = true
  uid = www-data
  
  die-on-term = true
  </code></pre>
  
  <p>Socket does get created and I have changed permission to 777 to make sure all nginx has access to. But it seems nginx does not send to upstream anyway. </p>
  
  <p>Browsing to localhost:8095 brings the nginx homepage find but any other route returns 404. <strong>Nginx error log is empty</strong>.</p>
  
  <p><em>I have confirmed that nginx <strong>reads the .conf</strong> (by adding spelling mistake and see the error in the nginx log) but changing socket location has no impact as if it does not even care about that section.</em> <strong>In similar cases on my ubuntu box when the sock file does not exist or there is a permission issue, I get 502 and some hint in the logs.</strong> <strong>But here I get nothing, as if UWSGI NOT CONFIGURED AGAINST NGINX.</strong></p>
  
  <p>I am lost, can you please help? Am I missing module configuration in nginx (similar to apache)? I am new to nginx. </p>