-
## Expected Behavior
Authenticated requests should be forwarded to the upstream without a certificate error.
## Current Behavior
Users successfully authenticated with GitHub Enterprise rece…
-
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…
-
I have deployed hysteria2 server and it shows the logs of server up and running
but when I try to connect t…
-
**Is your feature request related to a problem? Please describe.**
We're using a lot of python automation scripts, but when error rates increase on API calls it is difficult to identify the calling s…
-
**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 yo…
-
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 …
-
#### Bug Report Checklist
- [x] Have you provided a full/minimal spec to reproduce the issue?
- [x] Have you validated the input using an OpenAPI validator ([example](https://apidevtools.org/swagg…
-
Hello,
.net 8
I have a solution with an API .Api project with all the DTOs within, with [TranspilationSource] on them.
It works well.
I have put all my DTOs within another project, .Core (w…
-
Steps to reproduce
------------------
Use ACME.SH with OPNSENSE >=22.1 and HTTP/TLS validation
When I use the acme.sh plugin with OPNSENSE Verison 22.1 it stops working. It worked well with t…
-
OS: Ubuntu 20.04.3 LTS
Caddy Version: 2.4.6
Dockerfile:
```
FROM caddy:builder AS builder
WORKDIR .
RUN xcaddy build --with github.com/caddy-dns/namecheap
FROM caddy:latest
COPY --from=b…