Nicolas Duchon

Okay, I think I got it this time. I'll have to think about it, I don't wan't ending up merging https://github.com/buchdag/letsencrypt-nginx-proxy-companion-compose into this repo. I know that @JrCs wasn't really...

@steilerDev is the renewal date given by acme.sh in the acme-companion logs correct or not ? @hufhend this issue is about using acme-companion with a custom ACME CA, not with...

Those lines in the nginxproxy/acme-companion container logs: ```console [Sat Aug 14 14:34:00 UTC 2021] Skip, Next renewal time is: Fri Sep 24 20:41:17 UTC 2021 ```

I'm starting to suspect that the default `acme.sh` minimum validity before renewal isn't properly handling certificate issued with a validity < 1 month. Could you try issuing certificates with a...

At the moment no, but contributions are welcome 👍

@frasche if you provided a valid email address as `DEFAULT_EMAIL` you're supposed to receive mail notifications from Let's Encrypt when the certificate(s) obtained with the related ACME account are reaching...

SAN indeed works only by discrete container, there is currently no alternative names merging logic across containers. The idea is interesting but I doubt it will be feasible any time...

@Byh0ki sorry for the very late reply `nginx-proxy` is doing this on nginx.tmpl : ``` {{ if $enable_ipv6 }} listen [::]:{{ $external_https_port }} ssl http2; {{ end }} ``` I...

Correct me if I'm wrong but I guess the two options for the problem at hand would be to either detect if `nginx-proxy` [has IPv6 enabled](https://github.com/nginx-proxy/nginx-proxy#ipv6-support) or use our own...

Hi. The only way to solve this I can think of would be to run two identical apachephp container, each with their own slice of your 100+ domains. I'm not...