docker-compose up -d conflict with existing nginx server.

Directory

Ill just be honest here, i have no idea about anything related to email or docker etc so dont expect my to understand verbose questions. But heres whats going on, i have a web server already running on the root of the domain (lets say site.com). its using nginx as the reverse proxy. i already have it configured. the config file for that server uses this as its server name.server_name site.com www.site.com. I also have mail.site.com as a working subdomain. I do not know why, but when i go to that subdomain my website still displays on it. it shouldn’t since the nginx server block does not specify to use that, just www and the main domain. What i want is for the mailcow web interface admin panel to be accessible only through mail.site.com and the rest of the website to be as is. i also specified mail.site.com as the FDQN thing during the generate_config.sh setup but im not sure if that was correct. however when i run sudo docker-compose up -d it errors out on the nginx step. The error log is as follows

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 (not_sure_if_i_should_redact_this): 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 (not_sure_if_i_should_redact_this): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use
ERROR: Encountered errors while bringing up the project.

Its obvious whats happening here, the mailcow dockerized version of nginx conflicts with the existing nginx running. When i systemctl stop nginx on the server and then run docker-compose up -d it works, and the mailcow admin panel shows up on all domains however, mail.site.com, site.com, www.site.com.

What i need is for mailcows nginx to not conflict with the existing nginx running. and also for my existing nginx website to not show up on the “mail.” subdomain (because right now it is and idk why), and for the mailcow web interface to show up only on the mail. subdomain. For the record of what im doing, i own my website, and i want to create a support@site.com email address that users of the site can contact, and i, through the sites web interface, and communicate and respond back to.🙂

MAGIC

You may want to use your local NGinx as reverse proxy: https://mailcow.github.io/mailcow-dockerized-docs/firststeps-rp

azakero

BusterB

azakero Basically, he’s to run mailcow at different ports by changing the settings in the mailcow.conf to something like this:
HTTP_BIND=127.0.0.1 HTTP_PORT=8080 HTTPS_BIND=127.0.0.1 HTTPS_PORT=8443
Then on his nginx reverse proxy, he forwards requests to the mail server at ports 8080 and/or 8443. Mailcow’s nginx won’t start up if port 80 or 443 are currently being used by the host. Since the mailcow nginx instance will now run at ports 8080 and 8443 it won’t conflict with his other nginx instance and everything should work.