404 Response Code

[nickschuch]

I am trying to use this as a backend behind a load balancer.

The backend returns a 404, I am able to replicate with a curl request (works via my browser).

$ curl -I http://127.0.0.1:8025
HTTP/1.1 404 Not Found
Content-Type: text/plain; charset=utf-8
X-Content-Type-Options: nosniff
Date: Sat, 26 Aug 2017 11:40:42 GMT
Content-Length: 19

I am going to do some debugging, wanted to create an issue to see if others have seen this behavior.

[Nakilon]

-I is a HEAD request -- yes, it gives me 404 too.

[tyndyll]

Can you provide some details on what you mean by "behind a load balancer"? This will help us reproduce

[nakilon-idwell]

This is enough to reproduce:

$ curl -s http://user:password@...:8025 -o /dev/null -w '%{http_code}\n'
200
$ curl -s http://user:wrongpassword@...:8025 -o /dev/null -w '%{http_code}\n'
401
$ curl -sI http://user:password@...:8025 -o /dev/null -w '%{http_code}\n'
404

The last request is HEAD, not GET. The mailhog server had to respond with 200, not 404.

[vaisov]

Same happens to me when using behind Nginx. Nginx config I'm using: https://gist.github.com/blakethepatton/7928abb131593fd192606b681ee47b2b

Started with this, but it didn't work either: #117 (comment)

Found the solution for nginx at least. Instead of

location /mail {
       proxy_pass                        http://localhost:8080;

using (added trailing slash)

location /mail/ {
       proxy_pass                        http://localhost:8080/;

[voyc-jean]

Additional note. If you're running Mailhog behind a reverse proxy / loadbalancer and you're binding it to a different path, the MH_UI_WEB_PATH env var (or -ui-web-path parameter) should be set.

Example with Caddy:

localhost.com/mail* {
    reverse_proxy 0.0.0.0:8025
    tls internal
}

~/go/bin/MailHog -ui-web-path mail

[UncleTawnos]

The same problem here
Scenario:
kubernetes, regular nginx ingress controller with rewrite-target set to /
path /mailhog directs to mailhog ui and MH_UI_WEB_PATH is set to 'mailhog'
I get 404

api has started with correct path:
[HTTP] Binding to address: 0.0.0.0:8025
Creating API v1 with WebPath: /mailhog
Creating API v2 with WebPath: /mailhog
[APIv1] KEEPALIVE /api/v1/events