starred/mailpit

Fork 0

mirror of https://github.com/axllent/mailpit.git synced 2026-04-26 00:35:51 +03:00

[GH-ISSUE #19] Allow Mailpit to run at a non-root app context such as /mailpit/ #18

New issue

Closed

opened 2026-03-15 12:07:03 +03:00 by kerem · 7 comments

kerem commented

2026-03-15 12:07:03 +03:00

Owner

Originally created by @dforrest-es on GitHub (Oct 17, 2022).
Original GitHub issue: https://github.com/axllent/mailpit/issues/19

Is there a way to configure an application context? I need to serve Mailpit behind a proxy at https://{hostname}/mailpit/. However, the app artifacts (dist/app.js, etc) do not include that context.

This behavior would be similar to MailHog's MH_UI_WEB_PATH (docs)

Originally created by @dforrest-es on GitHub (Oct 17, 2022). Original GitHub issue: https://github.com/axllent/mailpit/issues/19 Is there a way to configure an application context? I need to serve Mailpit behind a proxy at `https://{hostname}/mailpit/`. However, the app artifacts (`dist/app.js`, etc) do not include that context. This behavior would be similar to MailHog's `MH_UI_WEB_PATH` ([docs](https://github.com/mailhog/MailHog/blob/master/docs/CONFIG.md))

kerem

2026-03-15 12:07:03 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-15 12:07:19 +03:00

Author

Owner

@axllent commented on GitHub (Oct 17, 2022):

The artefacts themselves should be relative to the entry point , so this should not be a problem and works fine here (at work we also use it as a virtual subdirectory which is proxies). Have you checked the http requests in your browser's debug tools to see what path it is using for those assets?

@axllent commented on GitHub (Oct 17, 2022): The artefacts themselves should be relative to the entry point , so this should not be a problem and works fine here (at work we also use it as a virtual subdirectory which is proxies). Have you checked the http requests in your browser's debug tools to see what path it is using for those assets?

kerem commented

2026-03-15 12:07:24 +03:00

Author

Owner

@macau23 commented on GitHub (Oct 28, 2022):

We currently also want to use Mailpit both behind a proxy, and directly.

Previously we used the option -ui-web-path, e.g. -ui-web-path mailpit to do this, but now this no longer works.

@macau23 commented on GitHub (Oct 28, 2022): We currently also want to use Mailpit both behind a proxy, and directly. Previously we used the option `-ui-web-path`, e.g. `-ui-web-path mailpit` to do this, but now this no longer works.

kerem commented

2026-03-15 12:07:29 +03:00

Author

Owner

@axllent commented on GitHub (Oct 28, 2022):

I don't understand how your proxy is set up. I use one that that is simply like this which works perfectly fine:

    <Location "/mail/">
        ProxyPass "http://localhost:8025/"
        ProxyPassReverse "http://localhost:8025/"
    </Location>

@axllent commented on GitHub (Oct 28, 2022): I don't understand how your proxy is set up. I use one that that is simply like this which works perfectly fine: ```apache <Location "/mail/"> ProxyPass "http://localhost:8025/" ProxyPassReverse "http://localhost:8025/" </Location> ```

kerem commented

2026-03-15 12:07:34 +03:00

Author

Owner

@macau23 commented on GitHub (Oct 31, 2022):

For us, we need to access the application at http://somehost:8025/mailpit/ (i.e. direct) and http://someproxy/mailpit/ so that does not work.

@macau23 commented on GitHub (Oct 31, 2022): For us, we need to access the application at http://somehost:8025/mailpit/ (i.e. direct) and http://someproxy/mailpit/ so that does not work.

kerem commented

2026-03-15 12:07:39 +03:00

Author

Owner

@axllent commented on GitHub (Oct 31, 2022):

I have added a --webroot flag for you in v1.2.7

@axllent commented on GitHub (Oct 31, 2022): I have added a `--webroot` flag for you in v1.2.7

kerem commented

2026-03-15 12:07:45 +03:00

Author

Owner

@dforrest-es commented on GitHub (Nov 5, 2022):

Thank you @axllent, and thanks to @macau23 for explaining our similar use cases. The changes are working well for me.

@dforrest-es commented on GitHub (Nov 5, 2022): Thank you @axllent, and thanks to @macau23 for explaining our similar use cases. The changes are working well for me.

kerem commented

2026-03-15 12:07:50 +03:00

Author

Owner

@saurabhnanda commented on GitHub (Jan 16, 2025):

thank you @axllent -- came here looking for this exact use-case.

@saurabhnanda commented on GitHub (Jan 16, 2025): thank you @axllent -- came here looking for this exact use-case.