Failed to install mailcow, port 443 in use

jiapei100

Hi, luckily I found mailcow. However, I failed to have it installed on my Digital Ocean droplet:

⋊> /o/mailcow-dockerized on master ◦  sudo docker-compose up -d                                                                                                                                       001:42:05
WARNING: The WATCHDOG_NOTIFY_EMAIL variable is not set. Defaulting to a blank string.
mailcowdockerized_dockerapi-mailcow_1 is up-to-date
mailcowdockerized_watchdog-mailcow_1 is up-to-date
mailcowdockerized_solr-mailcow_1 is up-to-date
mailcowdockerized_memcached-mailcow_1 is up-to-date
mailcowdockerized_unbound-mailcow_1 is up-to-date
mailcowdockerized_redis-mailcow_1 is up-to-date
mailcowdockerized_sogo-mailcow_1 is up-to-date
mailcowdockerized_clamd-mailcow_1 is up-to-date
mailcowdockerized_olefy-mailcow_1 is up-to-date
mailcowdockerized_mysql-mailcow_1 is up-to-date
mailcowdockerized_php-fpm-mailcow_1 is up-to-date
mailcowdockerized_postfix-mailcow_1 is up-to-date
Starting mailcowdockerized_nginx-mailcow_1 ... 
mailcowdockerized_dovecot-mailcow_1 is up-to-date
mailcowdockerized_netfilter-mailcow_1 is up-to-date
Starting mailcowdockerized_nginx-mailcow_1 ... error

ERROR: for mailcowdockerized_nginx-mailcow_1  Cannot start service nginx-mailcow: driver failed programming external connectivity on endpoint mailcowdockerized_nginx-mailcow_1 (739aafa95f6ea0e23e8e592d146effe57763aa587a523edd00c25e682189a908): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use

ERROR: for nginx-mailcow  Cannot start service nginx-mailcow: driver failed programming external connectivity on endpoint mailcowdockerized_nginx-mailcow_1 (739aafa95f6ea0e23e8e592d146effe57763aa587a523edd00c25e682189a908): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use
ERROR: Encountered errors while bringing up the project.

I’ve already started another Nginx service for domain management (multiple domains). So, in my case, nginx should take an additional job: mail server.

Can anybody give me a hand please ???

Cheers
Pei

diekuh

It does not fail to install on Digital Ocean, this is very misleading.

It simply fails to start because port 443 is obviously in use.

If you want to keep your httpd on port 443, you need to use a reverse proxy: https://mailcow.github.io/mailcow-dockerized-docs/firststeps-rp/

jiapei100

diekuh Yes, you are right… I actually hosted a couple of websites on the same digital ocean droplet. For each of those websites, I’m listening to port 443, using listen 443 ssl; # managed by Certbot.

After I configure port 8443 as described https://mailcow.github.io/mailcow-dockerized-docs/firststeps-rp/, it’s now progressed. I’m now moving forward… Thank you very much…. ^_^

jiapei100

diekuh There is still a file question for my mail server: https://www.longervision.com:8443/: Not secure.

I actually followed serverfault to setup my nginx. Can you please give me a hand on how to configure the nginx? for both the webiste and mail server?

# Default server configuration
#
server {

	root /var/www/longervision.com/html;

	# Add index.php to the list if you are using PHP
	index index.html index.htm index.nginx-debian.html;

	server_name longervision.com www.longervision.com;

	location / {
		# First attempt to serve request as file, then
		# as directory, then fall back to displaying a 404.
		try_files $uri $uri/ =404;
	}

    location /packages {
        autoindex on;
    }

    location /x86_64 {
        autoindex on;
    }

    location /arm {
        autoindex on;
    }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/longervision.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/longervision.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot


}


server {
    if ($host = www.longervision.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    if ($host = longervision.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


	listen 80;
	listen [::]:80;

	server_name longervision.com www.longervision.com;
    return 404; # managed by Certbot


}


server {
   listen 8080;
   server_name mail.longervision.com;

   location /.well-known {
        proxy_pass http://127.0.0.1:8080/.well-known ;
        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 100m;

   }

   location / {
        rewrite ^(.*) https://$server_name$1 permanent;
   }

}



server {
 listen 8443 ssl;
 server_name mail.longervision.com;

 ssl_certificate     /opt/mailcow-dockerized/data/assets/ssl/cert.pem;
 ssl_certificate_key /opt/mailcow-dockerized/data/assets/ssl/key.pem;
 ssl_protocols       TLSv1 TLSv1.1 TLSv1.2;
 ssl_ciphers         HIGH:!aNULL:!MD5;

 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 100m;
 }

}

Thank you very much…

diekuh

Did you place a valid certificate in /opt/mailcow-dockerized/data/assets/ssl/cert.pem?

If not, how would mailcow be able to request a certificate without using port 80? 🙂

You need to setup your reverse proxy correctly. mailcow cannot request a certificate over port 8080 (and neither 8443).

In your posted Nginx configs (! only there) change 8443 to 443 and 8080 to 80. Restart Nginx. Run docker-compose down and docker-compose up -d afterwards.

jiapei100

diekuh Yeah, I definitely have /opt/mailcow-dockerized/data/assets/ssl/cert.pem. And if I change

HTTP_PORT=8080
HTTP_BIND=0.0.0.0

HTTPS_PORT=8443
HTTPS_BIND=0.0.0.0

back to

HTTP_PORT=80
HTTP_BIND=0.0.0.0

HTTPS_PORT=443
HTTPS_BIND=0.0.0.0

I’ll get the question (1st post) again as:

Starting mailcowdockerized_nginx-mailcow_1 ... error

ERROR: for mailcowdockerized_nginx-mailcow_1  Cannot start service nginx-mailcow: driver failed programming external connectivity on endpoint mailcowdockerized_nginx-mailcow_1 (739aafa95f6ea0e23e8e592d146effe57763aa587a523edd00c25e682189a908): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use

ERROR: for nginx-mailcow  Cannot start service nginx-mailcow: driver failed programming external connectivity on endpoint mailcowdockerized_nginx-mailcow_1 (739aafa95f6ea0e23e8e592d146effe57763aa587a523edd00c25e682189a908): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use
ERROR: Encountered errors while bringing up the project.

diekuh

Okay, you don’t understood it.

I wrote previously: “In your posted Nginx configs (! only there)”

Now you changed it in mailcow.conf and - obviously - the port is in use.

If you cannot manage it, consider support, we will help you. You need to understand what a reverse proxy is and what it does.

jiapei100

diekuh hmmmm… Still problematic… Yeah, I may need a support… My current progress is:

website: longervision.com
mail server: mail.longervision.com , which is a subdomain of longervision.com
I also got some other websites hosted on the same droplet.

What I expect:

Host all websites, as well as the web server on the same droplet, and I can visit all sites and mail server .
I used to be able to visit all sites, but with my own nginx service running, NOT from within mailcow docker.

Current situation:

In order to run mailcow services, I’ve got to stop my nginx, postfix, dovecot services outside the mailcow docker.
Now, mailcow is running successfully, but all my websites, including longervision.com, are now ALL pointing to mail.longervision.com .

Can you please give me some further suggestions?

Cheers
Pei

D4niel

You need so setup a reverse proxy as 🐄 already said. That’s certainly nothing we can cover here in one thread. You can either get the knowledge yourself or buy a mailcow support package.

jiapei100

D4niel Yup… The COW’s answer is correct. Problem solved.

Solution :

Add a A record mail.longervision.com to domain longervision.com
Since mail.longervision.com is also a subdomain, add it under folder /etc/nginx/site-available, here use 80/443 by default
In file /opt/mailcow-dockerized/mailcow.conf, use 8080/8443.

Thank you very much. And thank The COW.