[GH-ISSUE #1624] Admin Login in Webinterface Gateway Timeout #1276

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

Originally created by @Dogy007 on GitHub (Nov 24, 2018).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1624

  • Modoboa: Version not sure (1 Month old installation)
  • installer used: Yes
  • Webserver: Nginx

Current behavior

Login in Webinterface works with all users

Login in Webinterface doesn't work with admin. Modoboa responds with Gateway Timeout

In /var/log/nginx mail.domain.ch-error.log

2018/11/24 00:14:40 [error] 508#508: *698 upstream timed out (110: Connection timed out) while reading response header from upstream, client: <192.X.X.X>, server: mail.Domain.ch, request: "GET /dashboard/ HTTP/1.1", upstream: "uwsgi://unix:/run/uwsgi/app/modoboa_instance/socket", host: "mail.Domain.ch", referrer: "https://mail.Domain.ch/accounts/login/?next=/"

If the password is wrong we get a "Username and Password do not match"
(Keep in mind, it works with users...)

It did work for a Month, and suddenly stopped working without configuration changes

Mails do get delivered still and can be accessed with a mail client

Originally created by @Dogy007 on GitHub (Nov 24, 2018). Original GitHub issue: https://github.com/modoboa/modoboa/issues/1624 * Modoboa: Version not sure (1 Month old installation) * installer used: Yes * Webserver: Nginx # Current behavior Login in Webinterface works with all users Login in Webinterface doesn't work with admin. Modoboa responds with Gateway Timeout In /var/log/nginx mail.domain.ch-error.log 2018/11/24 00:14:40 [error] 508#508: *698 upstream timed out (110: Connection timed out) while reading response header from upstream, client: <192.X.X.X>, server: mail.Domain.ch, request: "GET /dashboard/ HTTP/1.1", upstream: "uwsgi://unix:/run/uwsgi/app/modoboa_instance/socket", host: "mail.Domain.ch", referrer: "https://mail.Domain.ch/accounts/login/?next=/" If the password is wrong we get a "Username and Password do not match" (Keep in mind, it works with users...) It did work for a Month, and suddenly stopped working without configuration changes Mails do get delivered still and can be accessed with a mail client
kerem closed this issue 2026-02-27 11:16:15 +03:00
Author
Owner

@tonioo commented on GitHub (Nov 26, 2018):

@Dogy007 Could you please set DEBUG to True inside settings.py, reload uwsgi and retry? You should see a more verbose output.

<!-- gh-comment-id:441766185 --> @tonioo commented on GitHub (Nov 26, 2018): @Dogy007 Could you please set DEBUG to True inside settings.py, reload uwsgi and retry? You should see a more verbose output.
Author
Owner

@Dogy007 commented on GitHub (Nov 26, 2018):

The soultion was allow modoboa connection to it's api. Otherwise logins in the admin user portal wasn't possible

<!-- gh-comment-id:441770073 --> @Dogy007 commented on GitHub (Nov 26, 2018): The soultion was allow modoboa connection to it's api. Otherwise logins in the admin user portal wasn't possible
Author
Owner

@johnmays4545 commented on GitHub (May 8, 2019):

How do we allow modoboa connection to it's api? What config file do I need to modify

<!-- gh-comment-id:490437909 --> @johnmays4545 commented on GitHub (May 8, 2019): How do we allow modoboa connection to it's api? What config file do I need to modify
Author
Owner

@johnmays4545 commented on GitHub (May 8, 2019):

Solution for this issue on my server was to disable Firewall blocking countries outside the USA

<!-- gh-comment-id:490510652 --> @johnmays4545 commented on GitHub (May 8, 2019): Solution for this issue on my server was to disable Firewall blocking countries outside the USA
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#1276
No description provided.