mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-25 17:06:01 +03:00
[GH-ISSUE #1296] Webmail contents not showing when using NGINX as Reverse Proxy #1047
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#1047
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jasonaleski on GitHub (Nov 13, 2017).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1296
This really isn't an issue (anymore), but thought I'd share a solution to a problem I have been having. Modoboa was installed with the installer, but NGINX was reconfigured to be used as a Reverse Proxy; mainly for SSL offloading. I've had this issue with prior version of Modoboa installer, but never took the time to truly troubleshoot it...until now. For the most part, Modoboa back-end would work, except when displaying email content. It would display the headers, but not the actual content. The fix, at least for me, is below.
Impacted versions
Steps to reproduce/Current Problem
Webmail content unable to display while running behind Nginx (acting as a Reverse Proxy).
Expected behavior
Show email contents via webmail.
Proposed solutions that did not work:
In the /srv/modoboa/instance/instance/settings.py, the following X_FRAME_OPTIONS did NOT work (different instances of the configuration):
Solution that worked
In the /srv/modoboa/instance/instance/settings.py, set the following:
X_FRAME_OPTIONS = "ALLOW-FROM https://mailserver.yourdomain.com"I originally thought the configuration error was in Nginx, but then realized that the UWSGI server was confused due to the nature of the Reverse Proxy request.
Hopefully this will help someone in the future.
@jasonaleski commented on GitHub (Nov 13, 2017):
Just passing information to be documented.
@guillim commented on GitHub (Nov 29, 2017):
Had the same issue. your trick solved it. tks
@ntninja commented on GitHub (May 9, 2019):
Thank you, this helped me figure out why viewing messages did not work on my instance.