-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add reverse proxy documentation to the website #72
Comments
not knowing how to use github, I just pushed something before I was ready. sorry for the admin overhead. I need to add info about regeneration from the github comment: The configuration must be regenerated/reloaded before this takes effect. You can do so by navigating to Web within the admin panel and clicking on any of the Change buttons or simply run sudo ~/mailinabox/tools/web_update. |
Hi @kingwarrick. You actually didn't open a pull request, so I never saw your changes. |
I think I got it! |
Still can't get this to work. Clearly I'm thick, but I've tried pretty much every variation on the topic @kingwarrick has linked to and nothing seems to work. While I know they're used a lot in programming, I think the foo bar baz is just confusing me. I need a real world example if I'm ever going to get my other internal servers talking to the outside world without using non-standard ports. |
You might want to check mail-in-a-box/mailinabox#1837 (comment) |
Over the years, a number of users, including myself, have asked for clarification about reverse proxy setup. Some information is found in discourse.miab, but the most substantive is on github
I think a third section in the advanced tips/configuration on the website might be helpful, based on the above linked comment.
The text was updated successfully, but these errors were encountered: