-
**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…
-
### Description
I'm using my Raspberry Pi 5 with Coolify, running smoothly by opening ports 80 and 443 to access its dashboard via the instance domain. Today, I added a second server using my Raspber…
-
**Is your feature request related to a problem? Please describe.**
For production environment , it's best to verify the certificate during the replication between each nodes. Currently this is only p…
-
Apparently the NS records were missing, which broke the dns-01 ACME challenge
-
## The problem
After upgrading addon to 1.12.5 version, it can't obtain certificate
## Environment
- Add-on with the issue: DuckDNS
- Add-on release with the issue:
- Last working…
-
The context for this is im trying to setup acme on pfsense to create a wildcard cert using the `DNS-MailinaBox` method, but its failing. But that is just the context of where im hitting this issue i u…
ghost updated
4 weeks ago
-
Since Hashicorp Vault started from 1.14 have ACME support I tried to configure it with dns-01 validation and found that if I'm using private hosted zone in Route53 for some reason plugin cannot find i…
-
When issuing a (new) cert, the configured settings of the 'ACME DNS API' challenge type are not being used.
Instead, it always is using the endpoint 'https://auth.acme-dns.io/update'
I'm using a …
-
**Describe the bug**:
Stuck on this issue from last few days, same setup was working few months ago, recreated cluster and seeing this not working now.
Challenge returning
```
Reason: Wa…
-
Steps to reproduce
------------------
acme.sh --issue --dns dns_cf -d "uploads.domain.com" --server letsencrypt \
--key-file /etc/ssl/uploads.domain.com/privkey.pem \
--fullchain-file /etc/ssl…