502 Bad Gateway

[Kenneth T. Kjelsnes]

I get 502 Bad Gateway when trying to connect to my fresh install.

I get this error from /var/log/nginx/error.log:

2015/12/17 20:02:09 [crit] 30963#0: *1 connect() to unix:/usr/share/mayan-edms/uwsgi.sock failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: localhost, request: "GET / HTTP/1.1", upstream: "uwsgi://unix:/usr/share/mayan-edms/uwsgi.sock:", host: "localhost"

Both nginx and supervisor is running just fine.

I've followed every instruction given in the deployment article.

[Jonathon Exley]

Did you create a uwsgi.ini file?
If not then see the recent posts to this forum detailing the contents.

--

---
You received this message because you are subscribed to the Google Groups "Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mayan-edms+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kenneth T. Kjelsnes]

That worked. Thanks for pointing me in the right direction.

K.

[Gabriel Diteko]

I have also been getting the same error. I have created the uwsgi.ini file and still no change. First, where should I place the uwsgi.ini file and secondly, are there any other nginx deployment caveats?

[Sander Bastiaansen]

I get this error even when uwsgi.ini is in the right place (/usr/share/mayan-edms/*) and nginx and supervisor start fine. Any other pointers?

Op donderdag 17 december 2015 20:14:15 UTC+1 schreef Kenneth T. Kjelsnes:

[Roberto Rosario]

Post the output of the uwsgi and supervisor logs to see what could be wrong.

[Jayna Tan]

Somehow the order in which the 2 processes are started restarted is important though I do not understand the rationale.

Restart nginx first then supervisor.

I always get a bad gateway error when the order is reversed.