-
Hi all,
I wanted to open discussion on a change I am proposing to the API spec which I think is overall a very good idea. At launch Open MPIC supported a method called http-generic which allowed fo…
-
Steps to reproduce
------------------
当前acme.sh是v3.0.8最新了
acme.sh --issue -d www.example.com -d example.com --nginx /www/server/nginx/conf/nginx.conf --debug 2
Debug log
-----------------
…
-
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…
-
ACME certificate generation DNS Challenge from DeSec.io doesn't wait enough time for the propagation to occur, hence fails.
I tried to set the environment variable DESEC_PROPAGATION_TIMEOUT in my d…
-
**Is your feature request related to a problem? Please describe.**
ACME DNS validation with deSEC failed multiple times. It seems the timeout is too tight.
In Proxmox, I faced the same problem, addi…
-
I tried few times but I get Acme-Dns Server Failures :
root@k8s-eu-1-control-plane-node-1:~# git clone https://github.com/joohoi/acme-dns
Cloning into 'acme-dns'...
remote: Enumerati…
-
After getting certificates for about 45 domains, caddy suddenly stopped and I got this error:
```
[INFO] [mydomain.com] acme: Obtaining bundled SAN certificate
http: TLS handshake error from 127.…
-
When I use the `ingressClassName` ClusterIssuer setting (introduced in #5849) together with the `acme.cert-manager.io/http01-ingress-class` Ingress annotation, I get the following error on my challeng…
-
**Describe the bug**
I'm trying to get a certificate for a domain using Cloudflare.
The process takes long and eventually fails.
Using similar approach with HaProxy (pfSense) and NPM works fine.
…
-
I've been using the GoDaddy webhook with cert-manager on an on-prem cluster and I've encountered a situation that I'm hoping to get some clarification on.
We're running an internal DNS server w…