problem creation ssl certificate

[orangege59]

hi, i'm on raspberry pi, i installed nginx proxy manager and when i create a certificate it gives me this type of error

Error: Command failed: certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-2" --agree-tos --authenticator webroot --email "**********@gmail.com" --preferred-challenges "dns,http" --domains "coucoutoutlemonde.duckdns.org"
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

at ChildProcess.exithandler (node:child_process:397:12)
at ChildProcess.emit (node:events:394:28)
at maybeClose (node:internal/child_process:1064:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)

[thebiblelover7]

@orangege59 Could you post the output of the log? /var/log/letsencrypt/letsencrypt.log (from inside docker)

[orangege59]

I don't have letsencrypt in /var/log/

[Galileon-venta]

To add some Information; I've setup today and I am facing kind of the same issue...

Im not able to copy the whole file from portainer at my phone right now, but it says:

Authority reports follwing problems:
Domain: demo.demo.org
Type: connection
Detail Fetching http://demo.demo.org/.well-known/acme-challenge/abcde...xyz: Connection refused

[ptichalouf]

same error for me

this is the log from docker container

"certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-5" --agree-tos --authenticator webroot --email "@gmail.com" --preferred-challenges "dns,http" --domains ".xyz"
[9/17/2021] [8:49:23 AM] [Nginx ] › ℹ info Reloading Nginx
[9/17/2021] [8:49:23 AM] [Express ] › ⚠ warning Command failed: certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-5" --agree-tos --authenticator webroot --email "*******@gmail.com" --preferred-challenges "dns,http" --domains "ptichalouf.xyz"

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Some challenges have failed.

Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
"

[kamegami13]

I am having a similar issue. Running version 2.9.9 on OMV 5 docker image. Here is the full /var/log/letsencrypt/letsencrypt.log

https://pastebin.com/LFVL8s0k

EDIT: Quick update. While trying more things I discovered I had issues logging into my router. I did a complete hard reboot of my router and modem and then the cert challenges worked. Seems my router managed to crash in a partially working state.

[Galileon-venta]

@ALL Users with this Issue; can you confirm, that your IP Config is correct for ipv6 or no ipv6 Record exists for the domain youre trying to secure? I found out, that for my domain host new subdomains get a placeholder ipv6 record created and i deleted them directly after creation but it seems that some servers still cached it already...

Waiting 24 Hours (yes horrible cache length) did fix it for me

[ptichalouf]

personnaly i don't have any ipv6 record on the domain seems really an error with the challenge. I have an unraid server everything working great before but i make a new install and i didn't change anything from the past config, just make a reinstall. i hope that could help you

[jacktho]

I also am running into this issue. No ipv6 records.

[dirtymike0330]

Same issue here

e

[dirtymike0330]

@ALL Users with this Issue; can you confirm, that your IP Config is correct for ipv6 or no ipv6 Record exists for the domain youre trying to secure? I found out, that for my domain host new subdomains get a placeholder ipv6 record created and i deleted them directly after creation but it seems that some servers still cached it already...

Waiting 24 Hours (yes horrible cache length) did fix it for me

Are you referring to this? (attached). If so, I believe that is attached to a google sites website I created and there is no option to delete just that ipv6 record, it will delete that entire section (and I'm not sure if that will affect my website negatively or not)

.

[chaptergy]

Okay, so when not using a dns challenge make sure port 80 of your npm instance is available from the outside, so from the public internet! For this your domain needs to point to your npm home network and your router needs port forwarding set up for at least port 80. If your setup is not your home network, just make sure port 80 is available publicly.

For people using duckdns or similar services where you just have a subdomain, not the entire domain, see #1350 (comment)

[dirtymike0330]

Same issue here

e

For my quoted reply, I personally solved my issue by changing HTTP to HTTPS in the drop down menu in NPM on the details page.

[meiremans]

I had the same issue.

What solved it for me, was that there was one domain name not resolving and i removed that domain.

The certbot log gave this:
Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Domain: XXX
Type: dns
Detail: DNS problem: NXDOMAIN looking up A for XXXX - check that a DNS record exists for this domain

Apparently, it stops there, instead of creating it for the domains who are resolving(I think this was the behavior in earlier versions)