Tom Wiesing

You could look at [Custom Nginx Configuration](https://github.com/nginx-proxy/nginx-proxy#custom-nginx-configuration), or if that isn't sufficient you can always [adapt the template](https://github.com/nginx-proxy/nginx-proxy/blob/main/nginx.tmpl).

This is still an issue although the line numbers in `nginx.tmpl` have changed. Source line at the time the issue was created: https://github.com/nginx-proxy/nginx-proxy/blob/d74a4146c82e14664bf7da80260b6e3a01be8276/nginx.tmpl#L78 Current source line: https://github.com/nginx-proxy/nginx-proxy/blob/2f82265891f1dc70c9fc815ded5bfa2920016054/nginx.tmpl#L300

`zlib1g` doesn't get installed into the image explicitly. It's probably a dependency of some other package, and a simple image rebuild should fix this.

I don't think multiple services in the same container are supported at the moment. A workaround might be to have "dummy" containers for each additional port, that do nothing but...

@jakata007 @first087: Here is a workaround until a new feature is implemented. ```bash # start the nginx proxy docker run -d -p 80:80 -v /var/run/docker.sock:/tmp/docker.sock:ro \ --name my-nginx-proxy --network=mynetwork jwilder/nginx-proxy...

Is this still an issue?

This sounds like a very specific usecase that could be achieved with [Custom Nginx Configuration](https://github.com/nginx-proxy/nginx-proxy#custom-nginx-configuration).

For wildcard certificates, see https://github.com/nginx-proxy/nginx-proxy/issues/176#issuecomment-1100616417. A workaround might be to use `-e CERT_NAME=""` on the container in question.

This looks like something that should be implemented in https://github.com/nginx-proxy/docker-gen

I am not sure why the log is incorrectly showing the file was generated. However, I can see some issues with the `docker-compose.yml`. 1. You must make the docker daemon...