Issues with creating a subdomain for my mailcow server

laurenttaieb

Hi, I’m using NPM to create a subdomain mail.mydomain.fr to access to the soGO web interface from my LAN and from the Internet and I’m getting a “too many redirect” error messages. I looked around and couldn’t find the right setup to avoid this.
Had anyone has this issue and found a fix ? I have. single public IP address and this is the onlly way for me to access to the Web Interface.
Thanks

ETNyx

First what i would check is to follow the redirects what is happening, my bet is juggling whit https/http and back maybe due to hsts, so check those redirects

curl -I -L https://mail.mydomain.fr/SOGo

if you see something like

HTTP/2 302
location: https://mail.mydomain.fr/SOGo

HTTP/2 302
location: http://192.168.1.10/SOGo

HTTP/1.1 302
location: https://mail.mydomain.fr/SOGo

that’s it,..

laurenttaieb

Hi ETNyx,

I have error 301 in sequence, not 302:

curl -I -L https://mail.mydomain.fr/SOGo
HTTP/2 301
server: openresty
date: Tue, 25 Nov 2025 11:58:34 GMT
content-type: text/html
location: https://mail.mydomain.fr/SOGo
x-served-by: mail.mydomain.fr

HTTP/2 301
server: openresty
date: Tue, 25 Nov 2025 11:58:34 GMT
content-type: text/html
location: https://mail.mydomain.fr/SOGo
x-served-by: mail.mydomain.fr

ETNyx

Can you show us your NPM configuration?

laurenttaieb

Sure.. attached

presentation11.pdf

692kB

Please let me know if you can see.
Thanks
L

ETNyx

Did you set TRUSTED_PROXIES ?

laurenttaieb

Nope… didn’t see this parameter…
Is it in the main config file ?

added it to the main config file so that it gets propagated to the container yaml one…No change to the bad behaviour

ETNyx

And HTTP_BIND ? did you get through docs? Post what you did,…

laurenttaieb

The solution was just to use https instead of http on the client side. Mailcow npm was also redirecting itself…
Thanks
Laurent