I want to start this by saying, I feel really dumb that I cannot understand how custom Nginx configuration works and I feel like I have searched the whole internet to try and understand them but I am just not able to comprehend what I am doing wrong. I am aware there is a page dedicated to the configuration of Mailcow behind an Nginx reverse proxy (https://docs.mailcow.email/post_installation/reverse-proxy/r_p-nginx/) but my issue is where do I actually put this configuration? When I customise this configuration to what I believe is my correct details and add it to the Advanced section on the Nginx proxy host for my mail server it goes instantly offline when I push save. I have added it to a .conf file and added it as an additional volume on my Nginx docker container then specified it as a custom location for Mailcow on Nginx but I get the same issue. restarting both Mailcow and Nginx or removing and recomposing the containers still yields the exact same issues of being offline. I am using Mailcow in docker using this guide https://github.com/christianlempa/videos/tree/main/mailcow-tutorial for installing Mailcow. I changed Mailcow HTTP to 85 and HTTPS to 445 and have 80 and 443 ported forward to my Nginx reverse proxy. I have swapped the listening ports of the config below to both 80 and 85 and 443 and 445 for testing but still cannot get it to work. server { listen 80 default_server; listen [::]:80 default_server; server_name mail.mydomain.com autodiscover.mydomain.com autoconfig.mydomain.com; return 301 https://$host$request_uri; } server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name mail.mydomain.com autodiscover.mydomain.com autoconfig.mydomain.com; ssl_certificate docker_volumes/mailcow-dockerized/data/assets/ssl/cert.pem; ssl_certificate_key docker_volumes/mailcow-dockerized/data/assets/ssl/key.pem; ssl_session_timeout 1d; ssl_session_cache shared:SSL:50m; ssl_session_tickets off; # See https://ssl-config.mozilla.org/#server=nginx for the latest ssl settings recommendations # An example config is given below ssl_protocols TLSv1.2; ssl_ciphers HIGH:!aNULL:!MD5:!SHA1:!kRSA; ssl_prefer_server_ciphers off; location /Microsoft-Server-ActiveSync { proxy_pass http://192.168.50.250:85/Microsoft-Server-ActiveSync; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_connect_timeout 75; proxy_send_timeout 3650; proxy_read_timeout 3650; proxy_buffers 64 512k; # Needed since the 2022-04 Update for SOGo client_body_buffer_size 512k; client_max_body_size 0; } location / { proxy_pass http://192.168.50.250:85/; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; client_max_body_size 0; # The following Proxy Buffers has to be set if you want to use SOGo after the 2022-04 (April 2022) Update # Otherwise a Login will fail like this: https://github.com/mailcow/mailcow-dockerized/issues/4537 proxy_buffer_size 128k; proxy_buffers 64 512k; proxy_busy_buffers_size 512k; } } Thank you in advance and any help in understanding how custom configurations work would be greatly appreciated!

Rightio, so here is everything I have learned! This is everything you need to configure in the Advanced tab (adjust the IP and port according to your setup for both locations.) Everything else above this from the Mailcow website is already configured elsewhere in Nginx Reverse Proxy so you are doubling up and causing issues if you try to use it. Well done to @"DocFraggle"#1599 for giving me the complete answer without me realising. location /Microsoft-Server-ActiveSync { proxy_pass http://127.0.0.1:8080/Microsoft-Server-ActiveSync; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_connect_timeout 75; proxy_send_timeout 3650; proxy_read_timeout 3650; proxy_buffers 64 512k; # Needed since the 2022-04 Update for SOGo client_body_buffer_size 512k; client_max_body_size 0; } location / { proxy_pass http://127.0.0.1:8080/; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; client_max_body_size 0; # The following Proxy Buffers has to be set if you want to use SOGo after the 2022-04 (April 2022) Update # Otherwise a Login will fail like this: https://github.com/mailcow/mailcow-dockerized/issues/4537 proxy_buffer_size 128k; proxy_buffers 64 512k; proxy_busy_buffers_size 512k; } Port any other ports you need for mail server 25, 465, 587, 993, 4190, etc to the IP of docker host. make sure you add all 3 hostnames (mail.domain.com, autodiscover.domain.com and autoconfig.domain.com) to the domains names section on your Nginx reverse proxy host as well as on the SSL certificate tab. You will need to download the SSL certificate, copy it to YOUR_MAILCOW_PATH//data/assets/ssl/ and rename the cert and key file to cert.pem and key.pem then restart your container. You will need to copy the new certificate every 3 months to this location manually, I have not figured out a way do get the ACME request to work through proxy. I hope this helps someone! Huge shoutout to @"DocFraggle"#1599 especially for his persistence and patience! If anyone has any ideas how to maybe get the certificate request to work, let me know and we might be able to work it out together.

Please, PLEASE use the "Insert code" button to wrap your config, nobody can read this... What exactly did you configure in your mailcow.conf, especially this part as stated in the overview page (example below): ``` HTTP_BIND=127.0.0.1 HTTP_PORT=8080 HTTPS_BIND=127.0.0.1 HTTPS_PORT=8443 ``` You set the proxy_pass part to an upstream IP address (192.168.50.250), that's why I'm asking. If you used 127.0.0.1 in your mailcow.conf this can't work

Thank you for replying, I really appreciate it! This is what I currently have configured in that section. I have tried with the loopback address and the actual IP in the BIND section but still no good. HTTP_PORT=85 HTTP_BIND= HTTPS_PORT=445 HTTPS_BIND=

@"EverythingBySam"#p15648 Set this in mailcow.conf: ``` HTTP_BIND=127.0.0.1 HTTP_PORT=8080 HTTPS_BIND=127.0.0.1 HTTPS_PORT=8443 ``` ### **_RESTART mailcow afterwards!!!_** ``` docker compose down docker compose up -d ``` And this in your prox_pass lines: ``` location /Microsoft-Server-ActiveSync { proxy_pass http://127.0.0.1:8080/Microsoft-Server-ActiveSync; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_connect_timeout 75; proxy_send_timeout 3650; proxy_read_timeout 3650; proxy_buffers 64 512k; # Needed since the 2022-04 Update for SOGo client_body_buffer_size 512k; client_max_body_size 0; } location / { proxy_pass http://127.0.0.1:8080/; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; client_max_body_size 0; # The following Proxy Buffers has to be set if you want to use SOGo after the 2022-04 (April 2022) Update # Otherwise a Login will fail like this: https://github.com/mailcow/mailcow-dockerized/issues/4537 proxy_buffer_size 128k; proxy_buffers 64 512k; proxy_busy_buffers_size 512k; } ``` Just like in the docs,

That seems to of worked and did not knock it offline so thank you but I would like Autodiscover to work as well if possible.

Autodiscover should work as well then as long as you set your DNS config according to the docs, and the certificate was enrolled correctly

@"DocFraggle"#p15651 I have a CNAME autodiscover record for autodiscover.domain.com to go to mail.autodiscover.com. I do not have anything configured on my Nginx itself to recognise autodiscover.domain.com When I add those extra lines from the recommend config it goes offline again.

> @"EverythingBySam"#p15652 When I add those extra lines from the recommend config What do you mean? These lines? `server_name CHANGE_TO_MAILCOW_HOSTNAME autodiscover.* autoconfig.*;`

@"DocFraggle"#p15653 nah this whole section: server { listen 80 default_server; listen [::]:80 default_server; server_name CHANGE_TO_MAILCOW_HOSTNAME autodiscover.* autoconfig.*; return 301 https://$host$request_uri; } server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name CHANGE_TO_MAILCOW_HOSTNAME autodiscover.* autoconfig.*; ssl_certificate MAILCOW_PATH/data/assets/ssl/cert.pem; ssl_certificate_key MAILCOW_PATH/data/assets/ssl/key.pem; ssl_session_timeout 1d; ssl_session_cache shared:SSL:50m; ssl_session_tickets off; # See https://ssl-config.mozilla.org/#server=nginx for the latest ssl settings recommendations # An example config is given below ssl_protocols TLSv1.2; ssl_ciphers HIGH:!aNULL:!MD5:!SHA1:!kRSA; ssl_prefer_server_ciphers off;

Yes, just use the config from here: https://docs.mailcow.email/post_installation/reverse-proxy/r_p-nginx/ And of course replace CHANGE_TO_MAILCOW_HOSTNAME with your mailserver's FQDN

@"DocFraggle"#p15655 I did use that but if I add the top section I put in my previous comment it takes the proxy offline and no longer works.

Nginx Reverse proxy configuration

stefan21

Thx anybody for sharing.

Meanwhile I changed this setup from docker npm to native caddy. For the moment it works flawless. Caddy accepts “localhost” for the reverse configuration.

Becker884

stefan21 I’ve also considered using Caddy instead of Nginx, but apparently Caddy isn’t designed to publish (wildcard) certificates, so I can´t copy them to Mailcow.
Is that possible?

I use certbot with dns challenge and copy the certificates to mailcow with a script at “/etc/letsencrypt/renewal-hooks/deploy/mailcow.sh”

stefan21

IDK - I don’t need wildcard certs.

I’m copying (script post-hook.sh) the certs to mailcow:
..
CADDY_CERTS_DIR=/var/lib/caddy/.local/share/caddy/certificates/acme-v02.api.letsencrypt.org-directory
..

« Previous Page