Nicolas Duchon

To anyone affected by this, could you: - pull and use a recent version of the container, let's say `nginxproxy/nginx-proxy:0.9.3` - run it with in `--net=host` mode with the environment...

Hi. This does not look like a container related issue but like a host OS related issue. Is it okay if I convert this issue to a discussion ?

Well if going back to `0.8.0` fix the problem, I'd rather keep this as an issue. Do you experience the issue with `0.9.0` as well ?

@halan, @etopian do you have more informations I could work with ? Host OS, Docker version ? @etopian container logs ? Are you all using the `debian` or `alpine` version...

The only change I see between https://github.com/nginx-proxy/nginx-proxy/compare/0.9.1...0.9.2 that could be relevant to this issue is the upgrade from nginx `1.19.10` to `1.21.0`.

@etopian I might be wrong but I don't think that's the same issue or linked to the issue that @indapublic experienced.

I confirm this is an issue with the base nginx image: ```console [nduchon@host ~]$ docker run --rm -it nginx:1.21.3 bash root@f88797fb24d5:/# nginx 2021/10/21 06:38:58 [notice] 8#8: using the "epoll" event...

> {{- /* TODO: Replace the next few lines with a call to `join` once nginx-proxy has a version of > docker-gen that includes https://github.com/nginx-proxy/docker-gen/pull/418. */}} I'm on it: #1940

Thanks for the PR, unfortunately we can't make this behaviour a default one because a lot of people have custom configurations that rely on upstream names being equal to the...

Relevant previous PR for context : #41 and #587. I'm not really confortable about calling it a "rare use case" (based on what metric ?), breaking backward compatibility and calling...