Nicolas Duchon

@oktango if you follow the same logic you should be able to edit the `letsencrypt_service_data.tmpl` to use `LETSENCRYPT_HOST_1` instead of `LETSENCRYPT_HOST`, then bind the `nginx-proxy` container to a specific host...

Thanks for the tips @polarathene, I'll look into all of this 😃

Thats pretty much what I had in mind long term (migrating to `pytest` instead of the jury-rigged bash test suite I wrote), but yeah that will be some heavy work.

Hi. Thanks for the contribution. Have you tested it ? Do you think you could add documentation for this feature to your PR ?

> I added a short documentation under `docs/Container-configuration.md`. I hope it is the right place. Yep, that's perfect, thanks. > I tested this on my own servers, which are configured...

Hi, isn't this caused by the [DST Root CA X3 expiration](https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/) ?

@gurumark @fluffyst `nginxproxy/acme-companion:2.1.1` has been updated to use a newer version of `acme.sh` ([`2.8.8` -> `2.9.0`](https://github.com/acmesh-official/acme.sh/compare/2.8.8...2.9.0)), could you test again with this version of the container ?

Just to clarify: the `cert_status` function is a small utility that was hastily written a while ago, it's not meant to actually reflect the internal state of acme.sh in any...

I could update the doc with the Docker compose v3 files used here if that suits you : https://github.com/buchdag/letsencrypt-nginx-proxy-companion-compose edit: wrong URL

> It'd probably help to be a self contained example instead of only referencing the container you want to add. I didn't get that part 😶