A
A
Artemy Antipin2016-10-06 21:42:35
Nginx
Artemy Antipin, 2016-10-06 21:42:35

The already annoying “502 Bad Gateway” error appears, everything on the server is configured correctly, what could be the problem?

There is a problem 502 errors on the server everything is configured correctly in logs/nginx_error shows this:
2016/10/06 23:36:10 [crit] 20142#20142: *3774 connect() to unix:///home/mysaite/run /uwsgi.sock failed (13: Permission denied) while connecting to upstream, client: 78.29.26.66, server: saite-te.tk, request: "GET /favicon.ico HTTP/1.1", upstream: "uwsgi:// unix:///home/mysaite/run/uwsgi.sock:", host: "saite-te.tk" ,
2016/10/06 23:50:10 [error] 20142#20142: *3774 connect() to unix:///home/mychelsea/run/uwsgi.sock failed (111: Connection refused) while connecting to upstream, client: 78.29.26.66, server: panfilova-te.tk, request: "GET /favicon.ico HTTP/ 1.1", upstream: "uwsgi://unix:///home/mychelsea/run/uwsgi.sock:", host: "panfilova-te.tk"
what does this error mean?
also constantly pops up in the browser 2 errors:
1) Failed to load resource: the server responded with a status of 502 (Bad Gateway) saite-te.tk/favicon.ico
2) Failed to load resource: the server responded with a status of 502 (Bad Gateway) saite-te.tk
I can't think of what to do anymore, what could be the conflict?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
S
sim3x, 2016-10-06
@Mrchelsea

Permission denied
your nginx does not have permission to read the socket uwsgi
chmod-socket=664
stackoverflow.com/questions/22071681/permission-de...

D
Dimonchik, 2016-10-06
@dimonchik2013

replace it with gunicorn
here is one of the best recipes
and the reason is most likely in the ports

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question