Otdfbt

If every company in the economy earns zero economic profit, can they contribute to real economic growth?

Teaching a class likely meant to inflate the GPA of student athletes

Getting UPS Power from One Room to Another

Soft question: Examples where lack of mathematical rigour cause security breaches?

bmatrix: how to align elements' subscripts?

US doctor working in Tripoli wants me to open online account

How did old MS-DOS games utilize various graphic cards?

A word that means "blending into a community too much"

Why was this person allowed to become Grand Maester?

1980s live-action movie where individually-coloured nations on clouds fight

貧しい【まずしい】 poor 貧乏【びんぼう】な poor What's the difference?

How to trick the reader into thinking they're following a redshirt instead of the protagonist?

What ways have you found to get edits from non-LaTeX users?

Why can my keyboard only digest 6 keypresses at a time?

Why not invest in precious metals?

How to decline a wedding invitation from a friend I haven't seen in years?

You have (3^2 + 2^3 + 2^2) Guesses Left. Figure out the Last one

Changing Out a "Vintage" Dimmer Switch

Is an entry level DSLR going to shoot nice portrait pictures?

How can I get an unreasonable manager to approve time off?

What is the actual quality of machine translations?

Why 1,2 printed by a command in $() is not interpolated?

How to hide rifle during medieval town entrance inspection?

Is it possible for a vehicle to be manufactured without a catalytic converter?

Uwsgi/nginx unix socket refusing connections

Ubuntu 11.10 with Nginx and uWSGIUWSGI, Django, nginx cookie issue - causes 405 ErrorDeploying Flask application with nginx, uWSGI and virtualenvBottle.py app can't be found by nginx+uwsgi502 bad gateway nginx. uwsgi, flaskwhy django project failed deploying? - django + nginx + uwsgiuWSGI is ignoring uid, gid and chown-socketNginx cannot see unix socketWhat to set uwsgi uid and gid to?Connection refused by Unix socket file

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

0

I have a python project that I am trying to serve with uWSGI and Nginx. I'm trying to connect the two with a Unix IPC socket (debian stretch), but the socket refuses connections whenever Nginx tries to connect to it. It's not an issue of proper permissions or Nginx being pointed to the wrong location; I've already checked for that. What I believe may be the problem is that Nginx/the system does not see it as the proper socket file type to connect to. I considered this as a possibility when I did ls -l on the directory containing it, and it showed "-rw-rw-r--". With all the sockets I've seen, they have some variation of that with a "s" where the first hyphen is. How can I fix this issue?

linux nginx debian unix uwsgi

share|improve this question

asked May 23 at 16:04

uwsgiissuesuwsgiissues

1

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Typically, the directory containing the socket needs to have the execute permission for the user needing to access it, as well as any parent directories. For example, if the socket file is /run/uwsgi/django.sock, owned by "uwsgi:uwsgi", and the user accessing the socket was "nginx", then you'd want to ensure /run/uwsgi/ has others execute permissions, via chmod -c o+x /run/uwsgi/. Would you be able share the permissions of the directory itself?
  
  – Alan Ivey
  May 23 at 16:38
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Are you saying the containing directory doesn't have x permissions? Or that the path that is supposed to be the socket doesn't have an s? Or is it both? Your description is not clear, and you didn't actually include any ls -l output, which would be helpful.
  
  – Michael Hampton♦
  May 23 at 17:24
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  As a response to @Alan Ivey- Yes. The permission for the directory is located is "drwxr-xr-x" with root as the owner.
  
  – uwsgiisues
  May 23 at 17:25
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Can you append relevant lines from the Nginx error log to your original question?
  
  – Alan Ivey
  May 24 at 17:12
  

  
  
  
  

add a comment | 

0

I have a python project that I am trying to serve with uWSGI and Nginx. I'm trying to connect the two with a Unix IPC socket (debian stretch), but the socket refuses connections whenever Nginx tries to connect to it. It's not an issue of proper permissions or Nginx being pointed to the wrong location; I've already checked for that. What I believe may be the problem is that Nginx/the system does not see it as the proper socket file type to connect to. I considered this as a possibility when I did ls -l on the directory containing it, and it showed "-rw-rw-r--". With all the sockets I've seen, they have some variation of that with a "s" where the first hyphen is. How can I fix this issue?

linux nginx debian unix uwsgi

share|improve this question

asked May 23 at 16:04

uwsgiissuesuwsgiissues

1

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Typically, the directory containing the socket needs to have the execute permission for the user needing to access it, as well as any parent directories. For example, if the socket file is /run/uwsgi/django.sock, owned by "uwsgi:uwsgi", and the user accessing the socket was "nginx", then you'd want to ensure /run/uwsgi/ has others execute permissions, via chmod -c o+x /run/uwsgi/. Would you be able share the permissions of the directory itself?
  
  – Alan Ivey
  May 23 at 16:38
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Are you saying the containing directory doesn't have x permissions? Or that the path that is supposed to be the socket doesn't have an s? Or is it both? Your description is not clear, and you didn't actually include any ls -l output, which would be helpful.
  
  – Michael Hampton♦
  May 23 at 17:24
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  As a response to @Alan Ivey- Yes. The permission for the directory is located is "drwxr-xr-x" with root as the owner.
  
  – uwsgiisues
  May 23 at 17:25
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Can you append relevant lines from the Nginx error log to your original question?
  
  – Alan Ivey
  May 24 at 17:12
  

  
  
  
  

add a comment | 

I have a python project that I am trying to serve with uWSGI and Nginx. I'm trying to connect the two with a Unix IPC socket (debian stretch), but the socket refuses connections whenever Nginx tries to connect to it. It's not an issue of proper permissions or Nginx being pointed to the wrong location; I've already checked for that. What I believe may be the problem is that Nginx/the system does not see it as the proper socket file type to connect to. I considered this as a possibility when I did ls -l on the directory containing it, and it showed "-rw-rw-r--". With all the sockets I've seen, they have some variation of that with a "s" where the first hyphen is. How can I fix this issue?

linux nginx debian unix uwsgi

share|improve this question

asked May 23 at 16:04

uwsgiissuesuwsgiissues

1

share|improve this question

asked May 23 at 16:04

uwsgiissuesuwsgiissues

1

share|improve this question

asked May 23 at 16:04

uwsgiissuesuwsgiissues

1

asked May 23 at 16:04

uwsgiissuesuwsgiissues

1

asked May 23 at 16:04

uwsgiissuesuwsgiissues

1