Hi community, my cow is running smooth so far behind a nginx-proxy/acme-companion combination. All required certificate handling is established via a docker-compose.override.yml. Now I decided to give roundcubemail a chance and added the needed docker services (app and mariadb) to this docker-compose.override.yml. In my opinion IMAP authentication should work behind the proxy via existing mailcow network aliases without ssl/tls. I defined roundcube environment like this: - ROUNDCUBEMAIL_DEFAULT_HOST=dovecot - ROUNDCUBEMAIL_SMTP_SERVER=postfix I'm able to access the login page of roundcubemail under https://webmail.mydomain.de but it does not work at all. It takes my credentials without error message and shows the empty mask again. I tried several other combinations for both environment strings: tls://webmail.mydomain.de, ssl://webmail.mydomain.de But the result is always the same. Is anyone running a similar configuration?

mailcow and roundcube behind nginx proxy

seligmanns

Hi community,
my cow is running smooth so far behind a nginx-proxy/acme-companion combination.
All required certificate handling is established via a docker-compose.override.yml.
Now I decided to give roundcubemail a chance and added the needed docker services (app and mariadb) to this docker-compose.override.yml.
In my opinion IMAP authentication should work behind the proxy via existing mailcow network aliases without ssl/tls.
I defined roundcube environment like this:

ROUNDCUBEMAIL_DEFAULT_HOST=dovecot
ROUNDCUBEMAIL_SMTP_SERVER=postfix

I’m able to access the login page of roundcubemail under https://webmail.mydomain.de but it does not work at all. It takes my credentials without error message and shows the empty mask again.
I tried several other combinations for both environment strings:
tls://webmail.mydomain.de, ssl://webmail.mydomain.de
But the result is always the same.
Is anyone running a similar configuration?

cjwalsh

seligmanns

Hi seligmanns,

Would you mind sharing details of your configuration for having mailcow behind an nginx-proxy/acme-companion combination? I am having some trouble getting this to work - even just the basic reverse proxying element isn’t working for me.

I am using a docker-compose.override.yml file to add the additional VIRTUAL_HOST and VIRTUAL_PORT environment settings for nginx-proxy, and to attach to the network in my separate reverse proxy docker project, and I have changed mailcow.conf to bind to 127.0.0.1 and ports 8080 and 8443 for http and https, but I just get a 500 error from the reverse proxy.

I am using this approach because I would like to use the reverse proxy docker project to be able to handle both mailcow’s docker project and other docker projects for other virtual hosts - but maybe this is just being too complex.

Many thanks,
Ciaran.

accolon

There are installation instructions for a more integrated Roundcube in the mailcow docs:
https://mailcow.github.io/mailcow-dockerized-docs/third_party/third_party-roundcube/

Even if you don’t follow these instructions, you can probably use the configuration example for your setup.

seligmanns

Hi Ciaran,
I’m sorry. I switched to Traefik 2 meanwhile.

Stefan

kwisatz

For your information, the recent releases of roundcube are making this unnecessarily complicated. See for instance roundcube/roundcubemail8170 which made a perfectly fine working setup for me break on me and my users.

Now I’m also seeing problems with new users, which is not related to the reverse proxy, but still something that must’ve recently changed on roundcube’s part.

Also, for those wondering, there doesn’t seem to be any up to date roundcube docker container integration guide at the moment, at least not when I looked for it today. There is https://docs.mailcow.email/third_party/roundcube/third_party-roundcube/ but it’s not targetting a docker setup.