How to fix zammad-nginx to work behind nginx-reverse proxy

I have a nginx reverse-proxy running in docker which automatically provides SSL certs etc.

I need to start zammad with docker-compose BUT need zammad-nginx to NOT expose a public port on the host.

I commented out the

expose:

- “80”

but upon running docker-compose up -d
I still get the following error:

Creating zammad-docker-compose_zammad-nginx_1_e029d67f4ff1 … error

ERROR: for zammad-docker-compose_zammad-nginx_1_e029d67f4ff1 Cannot start service zammad-nginx: b’driver failed programming external connectivity on endpoint zammad-docker-compose_zammad-nginx_1_847758abba69 (204dc99bc62df49f4fc51133fa8b66254fa39faffa0de63f9b5ebe58fb5d41fd): Bind for 0.0.0.0:80 failed: port is already allocated’

ERROR: for zammad-nginx Cannot start service zammad-nginx: b’driver failed programming external connectivity on endpoint zammad-docker-compose_zammad-nginx_1_847758abba69 (204dc99bc62df49f4fc51133fa8b66254fa39faffa0de63f9b5ebe58fb5d41fd): Bind for 0.0.0.0:80 failed: port is already allocated’
ERROR: Encountered errors while bringing up the project.

How can I stop this?

I don’t need to expose a port since the containers are managed by the nginx-reverse-proxy via docker container labels.

Thank you!

Case of RTFM :slight_smile:
https://docs.zammad.org/en/latest/install-docker-compose.html

last paragraph helped me fix it.

1 Like