-
Wildcard DNS challenge stopped working after update to Caddy 2.8.
The minimum reproducible setup:
Caddy config:
```
{
storage consul {
prefix "caddytls"
}
admin :2019
debug
…
-
I have used this in the past to successfully geenrate certificates but i think something changed recently
I get this error from the challenge
```
Error presenting challenge: namecheap.acme.name…
-
ACME challenges stopped working on our Openshift cluster after operator upgrade to 1.13/1.14 version. It was working without problems with operator version 1.12 and stopped working after operator upda…
-
Bei mir ist Port 80 in der Fritzbox für ein anderes Gerät im Heimnetz freigegeben. Außerdem nutzt der plenticore Adapter 24/7 den Port.
Beides verhindert aktuell die Verwendung von acme mit LE Cert. …
-
**Describe the issue**
I'm running the basic tutorial, but I can't manage to make Let's encrypt work:
```bash
$ cd /var/lib/openreplay/openreplay/scripts/helmcharts && bash certmanager.sh
enter …
-
Steps to reproduce
------------------
acme.sh --issue --dns dns_autodns -d example.org
Debug log
-----------------
most likely this line:
`autodns_response='Parser error.EF00000errorXML parser…
-
I'm getting this error while running 'letsencrypt-vesta admin mydomain.com':
> Failed authorization procedure. www mydomain.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient a…
-
None of the big name ACME implementations support this TLS based challenge type.
(NGiNX, Certbot, Apache, etc.)
So it would be a nice bonus for Membrane as one of the only ACME capable gateways/reve…
-
Not sure if this was by-design or not, but the changes in #190 have made it impossible for the API domain that HTTP clients interact with to be different from the domain that the dns challenges are se…
-
[RFC 8738](https://datatracker.ietf.org/doc/html/rfc8738) add support for certificate having IP address in their SANs.
It would be nice to support that since people might have some servers using IP…