Open adocampo opened 1 year ago
I get a similar error with ClouDNS. This is the error I get:
`Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-14" --agree-tos --email "REDACTED" --domains "*.REDACTED,REDACTED" --authenticator dns-cloudns --dns-cloudns-credentials "/etc/letsencrypt/credentials/credentials-14" --dns-cloudns-propagation-seconds 120 Traceback (most recent call last): File "/usr/bin/certbot", line 5, in from certbot.main import main File "/opt/certbot/lib/python3.7/site-packages/certbot/main.py", line 6, in from certbot._internal import main as internal_main File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/main.py", line 28, in from certbot import crypto_util File "/opt/certbot/lib/python3.7/site-packages/certbot/crypto_util.py", line 42, in from certbot import interfaces File "/opt/certbot/lib/python3.7/site-packages/certbot/interfaces.py", line 21, in from acme.client import ClientBase ImportError: cannot import name 'ClientBase' from 'acme.client' (/opt/certbot/lib/python3.7/site-packages/acme/client.py)
at ChildProcess.exithandler (node:child_process:402:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1100:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)`
Did you manage to create the certificates using ACME-DNS ? I am facing the same error.
Issue is now considered stale. If you want to keep it open, please comment :+1:
i have same
samme here
i have the same :-( There is no mention of DNS Challenge anywhere in the documentation
samme here
Turns out my issue was related to a geo-location filter.:
“What is Multi-Perspective Validation?
Let's Encrypt needs to connect to your DNS server, and in most cases (for the HTTP-01 or TLS-ALPN-01 challenge type 11) also your web server, in order to validate that your client requesting a certificate actually has control over the domain name it's asking for. This is what's meant by "Validation"; see the How It Works 13 documentation page for more details. What "Multi-Perspective" means is that Let's Encrypt checks from multiple places, to make sure that control over the domain is established the same way when looking from different parts of the Internet.”
https://community.letsencrypt.org/t/multi-perspective-validation-geoblocking-faq/218158
I'm trying to create both a wildcard and host certificate through NPM, and I can't get it to work. I couldn't find any instructions to set up properly, so I've searched on GitHub and Reddit, but if someone has any issue I wasn't able to find anything similar.
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug Since a month or so, I migrated my email from gmail to my own server hosted in a VPS with mail-in-a-box (MiaB), which has its own DNS server. It is working just fine, not just with email, but all my services hosted on my home server were working as well, jut by creating the DNS entries on my MiaB.
Then Let's Encrypt certificates expired. I was running a normal nginx server, and had a cron to renew my old LE wildard certificate when my DNS was on OVH, but now I wanted to migrate from nginx to NPM and use its LE integration.
So after reading the possibilities, I found ACME-DNS was the right tool to create/renew the certificates. I found no documentation anywhere, so that's what I did, perhaps I did it wrong and that's why it isn't working, so please, if anyone can point me in the right direction, would be awesome (my Home Assistant is now inaccessible, and I can't even control the lights!)
First, following the ACME-DNS instructions, I asked the API for credentials with
Then, i'd created the CNAME entry
075264b8-a3a7-4f7a-b7f7-290e473f696f.auth.acme-dns.io
as_acme-challenge.mydomain.net
Withdig
I could see that was created properlyThen, on NPM's GUI, I created a reverse proxy And on the SSL tab, tried to create a certificate like this Setting the
dns_acmedns_api_url
tohttps://auth.acme-dns.io/
which is the URL I used on the aforementioned step and I created the credentials json file as I saw on #946:Clicked on "Save" on the GUI and after a while, appeared this error
NOTE: I don't know why is trying to use
/etc/letsencrypt/credentials/credentials-15
which doesn't exist, shouldn't it be/data/acme-registration.json
?On the
/tmp/letsencrypt-log/letsencrypt.log
appeared thisNginx Proxy Manager Version v2.10.4
NOTE2: I've tried both using
*.mydomain.net
andhome.mydomain.net
, modifying accordingly the/data/acme-registration.json
to point to the proper domain.Operating System Arch Linux Host. Dockers for all the services. In this example, Home Assistant is using a Host Network, so it has the IP of the hosts, which is reachable from the NPM container. NPM container has its own static IP, which is in the same docker network of all the other docker services which doesn't need to has a host network.
Additional context Docker version 24.0.5