-
Steps to reproduce
------------------
I am using a Chinese IDN domain name for my website, and using acme.sh build-in dns_ali to verify my domain for issuing certificate. Of course, I am using t…
-
I've just installed the script and got the error below with DigitalOcean. Detailed log attached.
```
# /root/.acme.sh/acme.sh --issue --dns dns_dgon -d cryptoclimate.io -d "*.cryptoclimate.io"
[F…
dandv updated
2 years ago
-
Following the guide, I don't get the details that the wiki provides.
Complete-ACMEChallenge stocknfo -ChallengeType http-01 -Handler manual
Renders below.
![image](https://user-images.githubu…
-
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…
-
The below snipped works for port 80 for letsencrypt challlenges, but fails to work for port 180 for example.
```
const Redbird = require('redbird');
const redbird = new Redbird( {
port: 180,…
awb99 updated
4 years ago
-
Hi there! Thanks for making this :)
I'm trying to build a server that's really easy to setup. Doing acme using the HTTP-01 challenge can be highly automated. This is great for end-users, as they do…
-
When neither DNS nor HTTP is possible (in very hardened setups), the TLS in-place validation on port 443 comes in mind;
https://letsencrypt.org/docs/challenge-types/
(https://datatracker.ietf.org/…
-
I have installed acme.sh on an Ubuntu 18.04 VM in Azure.
I have configured the Tenant ID, Subscription ID, App ID and Secret.
Our DNS is hosted by Azure. We have a bunch of domains, plus some subdom…
-
On a brand new setup the certificate generation challgen fails due to 404/403 errors.
I found a similar issue which was never resolved: https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy…
-
I ran into an issue, resolving it was tricky so I'll share.
I got let's encrypt site extension working with a Web App running PHP/Wordpress.
Ran into the error: "The Lets Encrypt ACME server was…