Replies: 3 comments 9 replies
-
|
I'm not familiar with Traefik but try setting Stalwart's log level to |
Beta Was this translation helpful? Give feedback.
-
|
@mdecimus I have same issue with Stalwart and Fast Reverse Proxy. I read logs and found out that Stalwart blocks one IP address and it is 172.18.0.1 - Gateway of docker network. So i guess when Stalwart works behind reverse proxy and after some time someone DDOSing it Stalwart see and blocks wrong IP. I think whitelisting private IP ranges will solve the problem of 502 but not the problem of blocking invalid addresses. |
Beta Was this translation helpful? Give feedback.
-
|
I had the same issue. For some reason, stalwart blocked my docker internal IP address. Removing it from the blocked list fixed the problem. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone, I've been trying to setup stalwart on my NAS lately, and trying to connect it to my Traefik network. With the configuration files that I'm going to show, everything worked fine for a moment, until it doesn't and I become unable to connect to the Admin page. I don't really understand what is going on here, and I really need help. I tried to follow what was written here because it apparently come from someone that had a similar issue, without success.
Here are my different configuration files:
docker-compose.yml (Traefik)
traefik.yml (Traefik)
docker-compose.yml (Stalwart)
config.toml (Stalwart)
Every time I try to connect to the admin panel, I get the error:
DBG github.com/traefik/traefik/v3/pkg/proxy/httputil/proxy.go:113 > 502 Bad Gateway error=EOFBeta Was this translation helpful? Give feedback.
All reactions