can't make a wildcard SSL certificate

[Schlotfeldt91]

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 you searched for similar issues (both open and closed)?
  • Yes

Describe the bug

i am trying to make a wildcard certificate and set it up with Cloudflare.
but when it's trying to generate the certificate, then i get this error message:

---

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

at /app/lib/utils.js:16:13
at ChildProcess.exithandler (node:child_process:430:5)
at ChildProcess.emit (node:events:518:28)
at maybeClose (node:internal/child_process:1104:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5)

---

and i don't know what that means? the API token is correct and i have tried to reinstall Nginx Prox Manager a few times now and i get the same error every time, i have also make a new virtual machine to see if that helped, but got the same error.

i am useing the docker compose file:

---

services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
- '80:80'
- '81:81'
- '443:443'
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt

Nginx Proxy Manager Version

v2.12.2 © 2024 jc21.com. Theme by Tabler

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior

Screenshots

Operating System

Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble

Additional context

Docker version 27.4.1, build b9d17ea

[timkolloch]

I have the same issue trying to use Strato.

Edit

For the comment from Loma0815 under #1154 solved my problem

[Trust996]

Unfortunately, I have the same problem.
There is a workaround that works.
Hopefully the developers will fix the problem soon :)

Thanks @Loma0815
exec in to the container
apt update
apt install pip
apt install nano
pip install certbot-dns-strato==0.2.2 --break-system-packages
cd global/
nano certbot-dns-plugins.json
change the version from Strato 0.2.1 to 0.2.2 and save it
restart the container
Request a new Wildcard within NPM

[Schlotfeldt91]

Okay i will try that 👍

[Schlotfeldt91]

Unfortunately, I have the same problem. There is a workaround that works. Hopefully the developers will fix the problem soon :)

Thanks @Loma0815 exec in to the container apt update apt install pip apt install nano pip install certbot-dns-strato==0.2.2 --break-system-packages cd global/ nano certbot-dns-plugins.json change the version from Strato 0.2.1 to 0.2.2 and save it restart the container Request a new Wildcard within NPM

Now i have tried what you suggested, but it did not work on my setup.

[timkolloch]

Now i have tried what you suggested, but it did not work on my setup.

This only solves the problem for the Strato DNS as you are trying to use Cloudfare the issue is likely to be with something else.

[Schlotfeldt91]

Now i have tried what you suggested, but it did not work on my setup.

This only solves the problem for the Strato DNS as you are trying to use Cloudfare the issue is likely to be with something else.

Ahh okay, didn't know it was a DNS 😅

[timkolloch]

Now i have tried what you suggested, but it did not work on my setup.

This only solves the problem for the Strato DNS as you are trying to use Cloudfare the issue is likely to be with something else.

Ahh okay, didn't know it was a DNS 😅

By trying to create a wildcard certificate you are trying to do a DNS-01 challenge which ensures you are controlling the DNS entry the domain points to so it needs to access it via your DNS provider :D

[Schlotfeldt91]

Now i have tried what you suggested, but it did not work on my setup.

This only solves the problem for the Strato DNS as you are trying to use Cloudfare the issue is likely to be with something else.

Ahh okay, didn't know it was a DNS 😅

By trying to create a wildcard certificate you are trying to do a DNS-01 challenge which ensures you are controlling the DNS entry the domain points to so it needs to access it via your DNS provider :D

I am using the API from cloudflare and I'm adding that API in Nginx Proxy Manager. So isn't that confirming the ownership of the domain? 😅

[Schlotfeldt91]

I have resolved the issue.

Apparently the public dns provider wasn't pointing correctly to Cloudfare.