Http-Recirect: Some trouble

omexlu

Hello,

As mentioned by @diekuh in the following thread I make a new post what I have considered so far:
https://community.mailcow.email/d/569-http-to-https-redirect

MailCow redirects to https by default by the following setting:
https://github.com/mailcow/mailcow-dockerized/blob/master/data/conf/nginx/includes/site-defaults.conf#L14

However, the actual problem I have is with the instructions here:
https://mailcow.github.io/mailcow-dockerized-docs/u_e-80_to_443/

I followed the introduction exactly and everything is exactly as expected, my installation is all on default (no custom modifications).

As soon as I create redirect.conf and reload nginx the panel is not reachable anymore in the nginx logs I find then following entry:

2021/01/08 07:44:03 [emerg] 18#18: a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2
nginx-mailcow_1 | nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2
nginx-mailcow_1 | nginx: configuration file /etc/nginx/nginx.conf test failed

I assume that there is a problem somewhere in the mailcow (nginx) configurations, even if HSTS is set by mailcow, the redirect.conf should still work.

On my root server i have similar configurations (not mailcow) also work without problems.

Would be grateful for help that together we can solve the problem 🙂

Thanks

omexlu

I tried again, no success:
2021/01/08 13:35:08 [emerg] 18#18: a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2 nginx-mailcow_1 | nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2 nginx-mailcow_1 | nginx: configuration file /etc/nginx/nginx.conf test failed nginx-mailcow_1 | 2021/01/08 13:35:09 [emerg] 18#18: a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2 nginx-mailcow_1 | nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2 nginx-mailcow_1 | nginx: configuration file /etc/nginx/nginx.conf test failed nginx-mailcow_1 | 2021/01/08 13:35:10 [emerg] 18#18: a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2 nginx-mailcow_1 | nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2 nginx-mailcow_1 | nginx: configuration file /etc/nginx/nginx.conf test failed nginx-mailcow_1 | 2021/01/08 13:35:12 [emerg] 18#18: a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2 nginx-mailcow_1 | nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2 nginx-mailcow_1 | nginx: configuration file /etc/nginx/nginx.conf test failed nginx-mailcow_1 | 2021/01/08 13:35:13 [emerg] 18#18: a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2 nginx-mailcow_1 | nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2 nginx-mailcow_1 | nginx: configuration file /etc/nginx/nginx.conf test failed nginx-mailcow_1 | 2021/01/08 13:35:16 [emerg] 19#19: a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2 nginx-mailcow_1 | nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2 nginx-mailcow_1 | nginx: configuration file /etc/nginx/nginx.conf test failed nginx-mailcow_1 | 2021/01/08 13:35:20 [emerg] 18#18: a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2 nginx-mailcow_1 | nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/site.conf:2 nginx-mailcow_1 | nginx: configuration file /etc/nginx/nginx.conf test failed

Stevie

Hello @omexlu ,
I have exactly the same problem as you, have you already wound a solution to it?
After I insert the redirect and reload nginx the panel doesn’t work anymore….

omexlu

Unfortunately not, it just does not want to work :/ Get the error that was mentioned above and more does not happen.

As soon as I remove the redirect again and reload everything works again.

diekuh

STS is not a HTTPS redirect! It works very different.

I installed a fresh mailcow, inserted the redirect and it works.

omexlu

Hi,

The redirect might come from cloudflare as it is a 301 as described at cloudflare (also for entries that are not proxified).

However, this should have no effect on the redirect.conf.

Then I also don’t know, as soon as I insert the redirect.conf and nginx reload the panel is no longer accessible and I shine not to be the only one 🙈

Don’t know what else to do here, then I will just leave it as it is redirected anyway.

The panel URL is: https://mx.s3cured.pw

Maybe you can do something with it and find out why it is redirected.

However, too bad because I wanted to include the redirect.conf as absolute security.

Edit: somewhere the nginx failed that’s because of the panel aren’t reachable but I have all default.

omexlu

So I don’t know who’s right now 😅
But redirect may not be affected to this 😭

Check this Screenshot from cloudflare community: