Skip to content

Releases: pini-gh/acme-companion

v2.0.2-dns2

24 Jan 23:45
Compare
Choose a tag to compare

Enable standalone certificate configuration for a container when LETSENCRYPT_HOST is set but not VIRTUAL_HOST.
No need for the /app/letsencrypt_user_data file in this case.

v2.0.2-dns1

28 Dec 10:09
Compare
Choose a tag to compare

Rebase against nginx-proxy/docker-letsencrypt-nginx-proxy-companion v2.0.2
Support DNS mode challenge and wildcard domain certificates.

Rebase against nginx-proxy/docker-letsencrypt-nginx-proxy-companion v2.0.1

13 Dec 13:20
Compare
Choose a tag to compare

Support DNS mode challenge and wildcard domain certificates.

Let nginx-proxy handle default certificate generation

27 Jun 18:52
Compare
Choose a tag to compare

The default certificate is needed by nginx-proxy before the letsencrypt companion can generate it.
This version requires pinidh/nginx-proxy.

Updated to nginx-proxy/docker-letsencrypt-nginx-proxy-companion v1.13

27 Jun 15:45
Compare
Choose a tag to compare
  • Rebase against nginx-proxy/docker-letsencrypt-nginx-proxy-companion v1.13
  • Force certificate renewal when the corresponding .companion flag file doesn't exist in the nging-proxy certs volume.

First acme.sh based release

25 Jun 21:53
Compare
Choose a tag to compare

Uses acme.sh as Let's Encrypt client (instead of simp_le) and brings support for:

  • DNS mode challenge
  • Wildcard domain certificates