Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
Ye
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 not the most proficient User so this might as well be sorted by deleting by hand or something else but im cautious to not delete something important (like current working certificates)
In the Past, I have had Issues with my Domain not pointing correctly to my Server or my Server didnt respond correspondigly.
I have tried to set up NPM anyways. The Configuration might have worked but there where some issues.
I have since deleted this configuration via the NPM GUI. Now, when I try to create a Certificate for the same Domain again, I get an error Message. I do NOT get this Error Message when I use any other subdomain.
What I believe is that the deletion will not actually delete every entry of this certificate from nginx (maybe like folders or something).
When then trying to create this domain again, it will detect that this folder actually exists and give out an error.
Nginx Proxy Manager Version
jc21/nginx-proxy-manager:latest
Try to Create a new SSL Certificate with the same configuration as Step 1
See error
Expected behavior
Create a working SSL Certificate.
When I use "ha.redacted.lol" (which I have used in the past) I get an error message.
When I try ah.redacted.lol (which I havent used in the past) it works perfectly fine.
Perhaps there is a way of purging all unused certificates ?
Operating System
24.04.1 LTS (GNU/Linux 6.8.0-44-generic x86_64)
On a Lenovo Thinclient.
Error Message from GUI:
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:519:28)
at maybeClose (node:internal/child_process:1105:16)
at ChildProcess._handle.onexit (node:internal/child_process:305:5)
Fulle letsencrypt.log can be accessed in this pastebin: https://pastebin.com/yssWnaWB
(please tell me if you can access my DNS Credentials if I have to redact something else!)
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug I am not the most proficient User so this might as well be sorted by deleting by hand or something else but im cautious to not delete something important (like current working certificates)
In the Past, I have had Issues with my Domain not pointing correctly to my Server or my Server didnt respond correspondigly. I have tried to set up NPM anyways. The Configuration might have worked but there where some issues. I have since deleted this configuration via the NPM GUI. Now, when I try to create a Certificate for the same Domain again, I get an error Message. I do NOT get this Error Message when I use any other subdomain.
What I believe is that the deletion will not actually delete every entry of this certificate from nginx (maybe like folders or something). When then trying to create this domain again, it will detect that this folder actually exists and give out an error.
Nginx Proxy Manager Version jc21/nginx-proxy-manager:latest
v2.11.3 © 2024 [jc21.com]
To Reproduce Steps to reproduce the behavior:
Expected behavior Create a working SSL Certificate.
When I use "ha.redacted.lol" (which I have used in the past) I get an error message. When I try ah.redacted.lol (which I havent used in the past) it works perfectly fine.
Perhaps there is a way of purging all unused certificates ?
Operating System 24.04.1 LTS (GNU/Linux 6.8.0-44-generic x86_64) On a Lenovo Thinclient.
Error Message from GUI: 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.
Fulle letsencrypt.log can be accessed in this pastebin: https://pastebin.com/yssWnaWB (please tell me if you can access my DNS Credentials if I have to redact something else!)