[GH-ISSUE #4270] can't make a wildcard SSL certificate

kerem commented

2026-02-26 07:36:41 +03:00

Owner

Originally created by @Schlotfeldt91 on GitHub (Dec 30, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4270

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

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
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

Originally created by @Schlotfeldt91 on GitHub (Dec 30, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4270  **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](https://jc21.com/?utm_source=nginx-proxy-manager). Theme by [Tabler](https://tabler.github.io/?utm_source=nginx-proxy-manager) **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior**  **Screenshots**  ![image](https://github.com/user-attachments/assets/efbed791-c4f4-4a25-bbaf-90cee751b814) **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

kerem

2026-02-26 07:36:41 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 07:36:41 +03:00

Author

Owner

@timkolloch commented on GitHub (Jan 4, 2025):

I have the same issue trying to use Strato.

Edit

For the comment from Loma0815 under #1154 solved my problem

@timkolloch commented on GitHub (Jan 4, 2025): I have the same issue trying to use Strato. ### Edit For the [comment from Loma0815](https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1154#issuecomment-2378735815) under #1154 solved my problem

kerem commented

2026-02-26 07:36:41 +03:00

Author

Owner

@Trust996 commented on GitHub (Jan 9, 2025):

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

@Trust996 commented on GitHub (Jan 9, 2025): 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

kerem commented

2026-02-26 07:36:41 +03:00

Author

Owner

@Schlotfeldt91 commented on GitHub (Jan 9, 2025):

Okay i will try that 👍

@Schlotfeldt91 commented on GitHub (Jan 9, 2025): Okay i will try that 👍

kerem commented

2026-02-26 07:36:41 +03:00

Author

Owner

@Schlotfeldt91 commented on GitHub (Jan 9, 2025):

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.

@Schlotfeldt91 commented on GitHub (Jan 9, 2025): > 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. ![image](https://github.com/user-attachments/assets/2779c1e4-5474-4c3a-8f32-20d66f6eec71) ![image](https://github.com/user-attachments/assets/2ba8e168-2938-404a-92fe-df81192514e9)

kerem commented

2026-02-26 07:36:41 +03:00

Author

Owner

@timkolloch commented on GitHub (Jan 10, 2025):

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.

@timkolloch commented on GitHub (Jan 10, 2025): > 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.

kerem commented

2026-02-26 07:36:41 +03:00

Author

Owner

@Schlotfeldt91 commented on GitHub (Jan 10, 2025):

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 😅

@Schlotfeldt91 commented on GitHub (Jan 10, 2025): > > 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 😅

kerem commented

2026-02-26 07:36:41 +03:00

Author

Owner

@timkolloch commented on GitHub (Jan 10, 2025):

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

@timkolloch commented on GitHub (Jan 10, 2025): > > > 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](https://letsencrypt.org/docs/challenge-types/#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

kerem commented

2026-02-26 07:36:41 +03:00

Author

Owner

@Schlotfeldt91 commented on GitHub (Jan 10, 2025):

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 commented on GitHub (Jan 10, 2025): > > > > 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](https://letsencrypt.org/docs/challenge-types/#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? 😅

kerem commented

2026-02-26 07:36:41 +03:00

Author

Owner

@Schlotfeldt91 commented on GitHub (Jan 12, 2025):

I have resolved the issue.

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

@Schlotfeldt91 commented on GitHub (Jan 12, 2025): I have resolved the issue. Apparently the public dns provider wasn't pointing correctly to Cloudfare.

kerem commented

2026-02-26 07:36:41 +03:00

Author

Owner

@jumadilabdulrahmanselian commented on GitHub (Jan 29, 2025):

I resolve it too,

Point your Root Domain to DNS only in Cloudflare.
Ensure that the DNS propagation has directed to your server, then try requesting the SSL certificate again.
If errors persist, update pip and other dependencies. Access your NPM container, manually update the required applications, and once the update is complete, try requesting the SSL certificate again.

Good luck!

@jumadilabdulrahmanselian commented on GitHub (Jan 29, 2025): I resolve it too, 1. Point your Root Domain to DNS only in Cloudflare. 2. Ensure that the DNS propagation has directed to your server, then try requesting the SSL certificate again. 3. If errors persist, update pip and other dependencies. Access your NPM container, manually update the required applications, and once the update is complete, try requesting the SSL certificate again. Good luck!

Rows
Columns

[GH-ISSUE #4270] can't make a wildcard SSL certificate #2754

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

Edit

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