-
In a scenario where you are trying to renew a new certificate or failing the TLS-ALPN-01 challenge for the first time (human error in config, networking in docker container non-standard, etc), it woul…
-
I'm running Caddy to manage wildcard certificates using route53 as a DNS provider.
This is running inside an AWS ECS task, where the task role has all the permissions on Route53 for all resources.
…
-
**Describe the bug**
Hi,
When I try to create a certificate for my own domain under the DNS provider IPv64, i get the following error. It works with a domain from IPv64, but not with my own. Dennis,…
-
**Describe the bug**
Hi,
I tried to add a certificate via ACME Tool and DNS-Challenge for "Amazon Route 53" and get the following error:
```
ACME] [system:error] Unable to resolve DNS challeng…
-
## 1. Environment
### 1a. Operating system and version
```
Windows 10
```
### 1b. Caddy version (run `caddy version` or paste commit SHA)
```
v2.8.4 h1:q3pe0wpBj1OcHFZ3n/1nl4V4bxBrYoS…
-
for those who internaly host an authoritative DNS server (e.g. Technitium DNS), it is not possible to get the acme process working with dns challange. The only solution is to offer an option to enter …
-
failed to set up TLS certificates: www.egjesg3g3.online: obtaining certificate: [www.egjesg3g3.online] Obtain: [www.egjesg3g3.online] solving challenges: www.egjesg3g3.online: no solvers available for…
-
I'm trying to get the hetzner dns provider cert to work with a wildcarded subdomain, but I'm having issues with provisioning the cert for a four-segment domain. A normal subdomain does work properly w…
-
**Checklist**
- Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image?
- Yes
- Are you sure you're not using someone else's docker image?
- Yes
- Have …
-
**Describe the bug**:
Issuing a new certificate fails on `error waiting for authorization` and `unexpected non-ACME API error`.
controller logs:
```
I1005 19:55:21.630885 1 conditions.go:203…