Replies: 2 comments 9 replies
-
Try accessing the UI through your proxy. You could be accessing Stalwart using an IP address that is in the same |
Beta Was this translation helpful? Give feedback.
-
same issue, it seems stalwart expects proxy protocol to be present for http requests. But the proxy protocol is not supported for http routing in traefik: traefik/traefik#10608 |
Beta Was this translation helpful? Give feedback.
-
Mauro, thanks for your prompt replies! 🍻
I've set up Stalwart-mail v0.7.0 in Docker with Postgres as the default store, proxied behind Traefik with Proxy Protocol 2. TLS certs have been extracted from Traefik's ACME store and placed in the Stalwart container.
When I set the trusted proxy network to the IP of my Traefik container, I get a
502 Bad Gateway
from the UI with the logs showinginvalid proxy header
. However, with this trusted proxy network set, Implicit TLS for port 465 and 993 works as expected from Roundcube and OpenSSL.When I remove the trusted proxy network, the UI loads but the TCP proxy breaks for all other listeners. Do you have any suggestions on how to resolve this?
Relevant Stalwart logs (172.18.0.10 = IP of Traefik):
With trusted proxy network not set (UI loads, other listeners fail):
With trusted proxy network set (UI doesn't load, other listeners succeed):
Relevant parts of config.toml:
Relevant config:
Stalwart-mail docker-compose.yml
Stalwart-mail full etc/config.toml
Traefik docker-compose.yml
Beta Was this translation helpful? Give feedback.
All reactions