-
My setup is as follows:
- Tectonic Cluster
- Nginx Controller v0.8.3
```kind: DaemonSet
apiVersion: extensions/v1beta1
metadata:
name: nginx-ingress-controller
namespace: kube-system
lab…
-
##### SUMMARY
We currently have three deprecations:
- Support for ACME v1 protocol in the acme_* modules, to be removed in 3.0.0.
- Support for Ansible 2.9 (this allows to remove the slowest CI tar…
-
We managed to get the INWX API to work in Version 2.7.9. after fixing the issues mentioned here: https://github.com/Neilpang/acme.sh/issues/1314
But, when testing it with version 2.8.0. new problem…
-
It would be great if river has the ability to generate valid certificates with Lets encrypt in near future, similar to Nginx Proxy Manager or Traefik.
-
Hello,
I've a wildcard domain (all subhosts shows to the same ip) from my dyndns-hoster. For that domain I tried to get a wildcard certificate from letsencrypt, but my dyndns-hoster had no api for …
-
### Steps to Reproduce
init the step ca with the following dns name xxxlhgroup.de.
I changed the dns name in ca.json and default.json to latest.lhgroup.de.
And now I send a certificate request over…
-
**What's needed and why ?**
Hi All
* As a BunkerWeb User having cert-manager in the Kubernetes Integration would make my experience even more cloud native.
* As a Homelab User on a Kubernetes Clus…
-
Error
------------------
Create new order error. Le_OrderFinalize not found. {"type":"urn:ietf:params:acme:error:malformed","detail":"Parse error reading JWS","status": 400}
Steps to reproduce
-…
Shuro updated
6 years ago
-
Steps to reproduce
------------------
Have an INWX account with more than 20 domains. It may happen that the requested domain is not in the result for "nameserver.list" - depending on the domain ord…
-
This rate limiting could be prevented by not requesting/issuing a certificate when a domain fails authorization.
_Note:_ This bug may be a function of the ACME protocol. If so this would need to b…