Juju bootstrap with letsencrypt fails | ACME client deprecated

Just bootstrapped a new 2.7.2 controller on maas cloud.

I noticed that the certificate isn’t signed and reviewing the machine log it seems that some of the intergrations are dated.

2020-02-25 21:10:17 ERROR juju.worker.httpserver tls.go:96 cannot get autocert certificate for "juju.maas.devzero.co.za": 403 urn:acme:error:unauthorized: Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details.

Command to bootstrap:

juju bootstrap maas.devzero.co.za juju.maas.devzero.co.za --constraints tags=juju-maas --config autocert-dns-name=juju.maas.devzero.co.za --credential new

:smiley: update

https://bugs.launchpad.net/juju/+bug/1864900

2 Likes

Thanks for reporting this. It looks like a fix has been approved for release:

https://github.com/juju/juju/pull/11299