[GH-ISSUE #1716] 502 Bad Gateway #1354

Closed
opened 2026-02-27 11:16:41 +03:00 by kerem · 4 comments
Owner

Originally created by @Dablakbandit on GitHub (Apr 10, 2019).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1716

Impacted versions

  • Modoboa: Latest
  • installer used: Yes
  • Webserver: Nginx

Steps to reproduce

Install on Ubuntu 18.04.2 LTS

Current behavior

Link to log:
test.log

Video/Screenshot link (optional)

image

Originally created by @Dablakbandit on GitHub (Apr 10, 2019). Original GitHub issue: https://github.com/modoboa/modoboa/issues/1716 # Impacted versions * Modoboa: Latest * installer used: Yes * Webserver: Nginx # Steps to reproduce Install on Ubuntu 18.04.2 LTS # Current behavior Link to log: [test.log](https://github.com/modoboa/modoboa/files/3064434/test.log) # Video/Screenshot link (optional) ![image](https://user-images.githubusercontent.com/5752611/55889988-0a11ab00-5c06-11e9-8ba0-d9032d09d8d4.png)
kerem closed this issue 2026-02-27 11:16:41 +03:00
Author
Owner

@tonioo commented on GitHub (Apr 29, 2019):

@Dablakbandit Have you checked if uwsgi is running?

<!-- gh-comment-id:487527383 --> @tonioo commented on GitHub (Apr 29, 2019): @Dablakbandit Have you checked if uwsgi is running?
Author
Owner

@codywarmbo commented on GitHub (Jun 4, 2019):

I also get this sporadically. Sometimes all is well, but my webmail solution often fails to authenticate and when I check the admin interface this error appears, only to go away moments later and all is operational again.

<!-- gh-comment-id:498684371 --> @codywarmbo commented on GitHub (Jun 4, 2019): I also get this sporadically. Sometimes all is well, but my webmail solution often fails to authenticate and when I check the admin interface this error appears, only to go away moments later and all is operational again.
Author
Owner

@peterchibunna commented on GitHub (Jul 31, 2019):

I get this too. Checking the error log yields

connect() to unix:/run/uwsgi/app/modoboa_instance/socket failed (13: Permission denied) while connecting to upstream
<!-- gh-comment-id:516833091 --> @peterchibunna commented on GitHub (Jul 31, 2019): I get this too. Checking the error log yields ``` connect() to unix:/run/uwsgi/app/modoboa_instance/socket failed (13: Permission denied) while connecting to upstream ```
Author
Owner

@peterchibunna commented on GitHub (Jul 31, 2019):

I finally figured out why. uwsgi is opening a socket it cannot read from. Change the chmod-socket parameter from 660 to 666 in /etc/uwsgi/apps-enabled/modoboa_instance.ini and /etc/uwsgi/apps-enabled/automx_instance.ini

<!-- gh-comment-id:516861585 --> @peterchibunna commented on GitHub (Jul 31, 2019): I finally figured out why. **uwsgi** is opening a socket it cannot read from. Change the `chmod-socket` parameter from `660` to `666` in `/etc/uwsgi/apps-enabled/modoboa_instance.ini` and `/etc/uwsgi/apps-enabled/automx_instance.ini`
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/modoboa-modoboa#1354
No description provided.