Somes challenges failed - NGINX proxy manager

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:
/opt/certbot/bin/certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-1" --agree-tos --email "" --preferred-challenges "dns,http" --domains ""

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Some challenges have failed.
Ask for help or search for solutions at See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version):

The operating system my web server runs on is (include version):
Operating System: Ubuntu 20.04.2 LTS
Kernel: Linux 5.4.0-74-generic
Architecture: x86-64

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
Portainer 2.51. for container management
nginx proxy manger dashboard for proxy hosts

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
certbot 1.16.0

Looking for assistance on this as I've been pulling my hair out for the past few hours now. Unable to generate SSL certifcates for hosted websites.

log files can be located here

My end goal is to have SSL ceritficates for locally hosted services and this was my first foray into it as a proof of concept.

Additional inf in case its of any use.
Baremetal Proxmox install > Ubuntu 20.04.2 LTS (VM) > nginx through docker-compose

Update: Got things working. Swapped out to a different image of proxy manager which had the same issue but gave a more substantive error message which allowed to find the exact issue with cloudeflare DNS. Re-did my A name records and disbaled SSL/TLS on Cloudflare webUI (I think this was the culprit tbh) and I now have SSL up and running. For anyone else with a similar issue hopefully this will help.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.