starred/modoboa-modoboa
1
0
Fork 0
mirror of https://github.com/modoboa/modoboa.git synced 2026-04-25 00:46:03 +03:00
Code Issues 60 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #1680] Unable to login with admin user when IMAP is forwarded from WAN #1323

New issue
Closed
opened 2026-02-27 11:16:31 +03:00 by kerem · 5 comments
kerem commented 2026-02-27 11:16:31 +03:00
Owner
Copy link

Originally created by @Razorblade12 on GitHub (Feb 22, 2019).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1680

Impacted versions

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

Steps to reproduce

Enable Port Forwarding for IMAP(s) to local mail server on firewall. Login with user that has any administrative role

Current behavior

Unable to login, error message 504 Gateway Time-Out

Expected behavior

Administrative user is able to login

Additional information

As soon as the Port forwarding rule is disabled on the firewall login is possible.
Login with any user that does not have an administrative role is always possible.

You can even try a simple user with the firewall rule active. That user is able to login. When the user's role is then changed to Domain Administrator or Super Administrator the login is not possible.

Originally created by @Razorblade12 on GitHub (Feb 22, 2019). Original GitHub issue: https://github.com/modoboa/modoboa/issues/1680 # Impacted versions * Modoboa: 1.12.2 * installer used: Yes * Webserver: Nginx # Steps to reproduce Enable Port Forwarding for IMAP(s) to local mail server on firewall. Login with user that has any administrative role # Current behavior Unable to login, error message 504 Gateway Time-Out # Expected behavior Administrative user is able to login # Additional information As soon as the Port forwarding rule is disabled on the firewall login is possible. Login with any user that does not have an administrative role is always possible. You can even try a simple user with the firewall rule active. That user is able to login. When the user's role is then changed to Domain Administrator or Super Administrator the login is not possible.
kerem 2026-02-27 11:16:31 +03:00
kerem commented 2026-02-27 11:16:31 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (Feb 25, 2019):

@Razorblade12 Strange... Are you talking about authentication to the web frontend? What is the first url the user is redirected to after authentication?

<!-- gh-comment-id:466948515 --> @tonioo commented on GitHub (Feb 25, 2019): @Razorblade12 Strange... Are you talking about authentication to the web frontend? What is the first url the user is redirected to after authentication?
kerem commented 2026-02-27 11:16:31 +03:00
Author
Owner
Copy link

@Razorblade12 commented on GitHub (Feb 27, 2019):

@tonioo Yes, the authentication to the web frontend.
After entering credentials and pressing enter the message "504 Gateway Time-Out" appears with the "/dashboard" URL after several seconds.

<!-- gh-comment-id:467765933 --> @Razorblade12 commented on GitHub (Feb 27, 2019): @tonioo Yes, the authentication to the web frontend. After entering credentials and pressing enter the message "504 Gateway Time-Out" appears with the "/dashboard" URL after several seconds.
kerem commented 2026-02-27 11:16:31 +03:00
Author
Owner
Copy link

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

Was this issue ever resolved, I am currently experiencing the same error?

<!-- gh-comment-id:490440864 --> @johnmays4545 commented on GitHub (May 8, 2019): Was this issue ever resolved, I am currently experiencing the same error?
kerem commented 2026-02-27 11:16:31 +03:00
Author
Owner
Copy link

@Razorblade12 commented on GitHub (May 12, 2019):

@johnmays4545
No, unfortunately not. I did not hear anything since my last post.
I think this might be a nginx configuration issue as I recently had the same issue with a different nginx site. So there must be something specific with the webserver.

<!-- gh-comment-id:491626787 --> @Razorblade12 commented on GitHub (May 12, 2019): @johnmays4545 No, unfortunately not. I did not hear anything since my last post. I think this might be a nginx configuration issue as I recently had the same issue with a different nginx site. So there must be something specific with the webserver.
kerem commented 2026-02-27 11:16:31 +03:00
Author
Owner
Copy link

@stale[bot] commented on GitHub (Oct 23, 2020):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

<!-- gh-comment-id:715534817 --> @stale[bot] commented on GitHub (Oct 23, 2020): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
fix/sievefilters-allow-email-in-rule-name
dependabot/npm_and_yarn/frontend/axios-1.15.0
translations_04c0b653215cb5fa48ab101eae1a1917_ja_JP
translations_5d93982e9fd6dab991db4faf93ce9ded_ja_JP
fix/login-issue-3995
fix/sievefilters-issues
add-vitepress-openapi
2974-dmarc-empty-email
2.3.x
updated-doc-2.3.0
feature/OIDC
delete-all-alarms
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_af_ZA
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_ar
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_ca
1.x
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_sk
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_tr
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_es_ES
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_uk
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_zh_CN
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_de_DE
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_da_DK
1.8.x
1.7.x
1.6.x
1.4.x
1.3.x
1.2.x
2.8.2
2.8.1
2.8.0
2.7.2
2.7.1
2.7.0
2.6.5
2.6.4
2.6.3
2.6.2
2.6.1
2.6.0
2.5.1
2.5.0
2.4.11
2.4.10
2.4.9
2.4.8
2.4.7
2.4.6
2.4.5
2.4.4
2.4.3
2.4.2
2.4.1
2.4.0
2.3.6
2.3.5
2.3.4
2.3.3
2.3.2
2.3.1
2.3.0
2.3.0-beta.4
2.3.0-beta.3
2.3.0-beta.2
2.3.0-beta.1
2.2.4
2.2.3
2.2.2
2.2.1
2.2.0
2.1.2
2.1.1
2.1.0
2.0.5
2.0.4
2.0.3
2.0.2
2.0.1
2.0.0
2.0.0-beta.3
2.0.0-beta.2
2.0.0-beta.1
1.17.0
1.16.1
1.16.0
1.15.0
1.14.0
1.13.1
1.13.0
1.12.2
1.12.1
1.12.0
1.11.1
1.11.0
1.10.7
1.10.6
1.10.5
1.10.4
1.10.3
1.10.2
1.10.1
1.10.0
1.9.1
1.9.0
1.8.3
1.8.2
1.8.1
1.8.0
1.7.4
1.7.3
1.7.2
1.7.1
1.7.0
1.6.3
1.6.2
1.6.1
1.6.0
1.5.3
1.5.2
1.5.1
1.5.0
1.4.5
1.4.4
1.4.3
1.4.2
1.4.1
1.4.0
1.3.5
1.3.4
1.2.2
1.3.3
1.3.2
1.3.1
1.3.0
1.2.1
1.2.0
1.2.0-rc2
1.2.0-rc1
1.1.7
1.1.6
1.1.5
1.1.4
1.1.3
1.1.2
1.1.1
1.1.0
1.0.1
1.0.0
0.9.5
0.9.4
0.9.3
0.9.2
0.9.1
0.9
0.8.8
0.8.7
0.8.6.1
0.8.6
0.8.5
0.8.4
0.8.3
0.8.3-rc1
0.8.2
0.8.1
0.8
0.8-rc2
0.8-rc1
0.7.2
0.7.1
0.7
0.6.1
0.6
0.5
0.3
0.2
0.1
Labels
Clear labels   
bug

   
bug

   
dependencies

   
design

   
documentation

   
duplicate

   
enhancement

   
enhancement

   
enhancement

   
feedback-needed

   
help-needed

   
help-needed

   
installer

   
invalid

   
looking-for-sponsors

   
modoboa-contacts

   
new-ui

   
new-ui

   
pr

   
pull-request

Mirrored from GitHub Pull Request

  
pyconfr

   
python

   
question

   
security

   
stale

   
webmail

   
wontfix
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#1323
No description provided.