[GH-ISSUE #1838] ssl wildcard certificate internal error dns challenge #1351

Closed
opened 2026-02-26 07:30:38 +03:00 by kerem · 5 comments
Owner

Originally created by @okuzlu on GitHub (Feb 8, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1838

Tried to create an ssl certificate with cloudflare dns challenge but I get a internal error.

internal error message on webgui
`Error: Command failed: /usr/sbin/nginx -t -g "error_log off;"
nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-3/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-3/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
nginx: configuration file /etc/nginx/nginx.conf test failed

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

nginx container log
[2/8/2022] [10:48:23 AM] [Express ] › ⚠ warning Command failed: /usr/sbin/nginx -t -g "error_log off;" nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-3/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-3/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) nginx: configuration file /etc/nginx/nginx.conf test failed

Originally created by @okuzlu on GitHub (Feb 8, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1838 Tried to create an ssl certificate with cloudflare dns challenge but I get a internal error. **internal error message on webgui** `Error: Command failed: /usr/sbin/nginx -t -g "error_log off;" nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-3/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-3/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) nginx: configuration file /etc/nginx/nginx.conf test failed at ChildProcess.exithandler (node:child_process:397:12) at ChildProcess.emit (node:events:390:28) at maybeClose (node:internal/child_process:1064:16) at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)` **nginx container log** `[2/8/2022] [10:48:23 AM] [Express ] › ⚠ warning Command failed: /usr/sbin/nginx -t -g "error_log off;" nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-3/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-3/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) nginx: configuration file /etc/nginx/nginx.conf test failed`
kerem 2026-02-26 07:30:38 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@jakemauer commented on GitHub (Aug 3, 2022):

I'm also encountering this error and just came here searching for it. Have you found any way to create a wildcard cert from within the GUI?

<!-- gh-comment-id:1203558845 --> @jakemauer commented on GitHub (Aug 3, 2022): I'm also encountering this error and just came here searching for it. Have you found any way to create a wildcard cert from within the GUI?
Author
Owner

@okuzlu commented on GitHub (Aug 3, 2022):

I'm also encountering this error and just came here searching for it. Have you found any way to create a wildcard cert from within the GUI?

I deleted the volumes and reinstalled the nginx proxy. After that I was again able to create a cert.

<!-- gh-comment-id:1203646169 --> @okuzlu commented on GitHub (Aug 3, 2022): > I'm also encountering this error and just came here searching for it. Have you found any way to create a wildcard cert from within the GUI? I deleted the volumes and reinstalled the nginx proxy. After that I was again able to create a cert.
Author
Owner

@jakemauer commented on GitHub (Aug 4, 2022):

I figured it out, this isn't a bug, it was (at least in my case) due to the Cloudflare "Credentials File Content" being malformed. I had accidentally formatted it as one line and thus it was just a single commented out line like this:

# Cloudflare API token dns_cloudflare_api_token = 0123456789abcdef0123456789abcdef01234567

When it should look like this:

# Cloudflare API token 
dns_cloudflare_api_token = 0123456789abcdef0123456789abcdef01234567

or a single line like this:
dns_cloudflare_api_token = 0123456789abcdef0123456789abcdef01234567

<!-- gh-comment-id:1205650129 --> @jakemauer commented on GitHub (Aug 4, 2022): I figured it out, this isn't a bug, it was (at least in my case) due to the Cloudflare "Credentials File Content" being malformed. I had accidentally formatted it as one line and thus it was just a single commented out line like this: `# Cloudflare API token dns_cloudflare_api_token = 0123456789abcdef0123456789abcdef01234567` When it should look like this: ``` # Cloudflare API token dns_cloudflare_api_token = 0123456789abcdef0123456789abcdef01234567 ``` or a single line like this: `dns_cloudflare_api_token = 0123456789abcdef0123456789abcdef01234567`
Author
Owner

@github-actions[bot] commented on GitHub (Aug 13, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2285198071 --> @github-actions[bot] commented on GitHub (Aug 13, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Aug 18, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:3194890123 --> @github-actions[bot] commented on GitHub (Aug 18, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1351
No description provided.