-
Notifications
You must be signed in to change notification settings - Fork 1k
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
MailHog not working when using nginx proxy pass #117
Comments
@prazmok |
@prazmok Add this to your nginx config ... That should do the trick. You must ensure that your mime.types are well configured
|
I've added a note to the configuration section of the docs - it's probably not in the most obvious place, but hopefully it'll help someone out! |
Here is the equivalent config for the Apache
|
Related comment about Apache proxy configuration #142 (comment) |
Websocket configuration added to nginx.conf fixed issue. See: - https://www.nginx.com/blog/websocket-nginx/ - mailhog/MailHog#117 Also fixed ENV variable for MailHog. Should be HOSTNAME. More-less just cosmetic change - used for EHLO/HELO & mail header. Default value is mailhog.example. remp/remp#149
Below block worked for me
|
I used this inside a new server block together with my rails app configuration, i've added its own server_name and only |
I am using MailHog as a Docker container (using docker-compose) and for default configuration everything is OK. Unfortunately when I created Nginx proxy pass I get an error in browser console
I guess it is bad configuration problem but as far as I know there is no option to configure MailHog image for docker-compose.
The text was updated successfully, but these errors were encountered: