starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #3791] Cannot read property '1' of null - signed with windows ca #2496

New issue

Closed

opened 2026-02-26 07:35:46 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 07:35:46 +03:00

Owner

Originally created by @tomse on GitHub (Jun 4, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3791

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

ref bug #1013 It's pretty old so won't stir up an old pot.

trying to use custom SSL certs, signed by Windows AD CA. I'm getting the same error

but forcecn mentioned in #1013 should only be checked if there are no cn.
since there is a cn and alternative names.. this shouldn't be a problem.

cert works perfectly in production on an nginx web server

Nginx Proxy Manager Version

2.11.2

To Reproduce
Steps to reproduce the behavior:

create key using openssl
create signing request with defaults and CN, subjectAltName (IP.1, DNS.1, DNS.2) filled out
sign using windows ca
upload cert + key to npm
see error

Expected behavior

acceptance of ssl cert

Screenshots

Operating System

Using Windows to upload cert

Additional context

Originally created by @tomse on GitHub (Jun 4, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3791  **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**  ref bug #1013 It's pretty old so won't stir up an old pot. trying to use custom SSL certs, signed by Windows AD CA. I'm getting the same error but forcecn mentioned in #1013 should only be checked if there are no cn. since there is a cn and alternative names.. this shouldn't be a problem. cert works perfectly in production on an nginx web server **Nginx Proxy Manager Version**  2.11.2 **To Reproduce** Steps to reproduce the behavior: 1. create key using openssl 2. create signing request with defaults and CN, subjectAltName (IP.1, DNS.1, DNS.2) filled out 3. sign using windows ca 4. upload cert + key to npm 5. see error **Expected behavior**  acceptance of ssl cert **Screenshots**  **Operating System**  Using Windows to upload cert **Additional context**

kerem

2026-02-26 07:35:46 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 07:35:47 +03:00

Author

Owner

@tomse commented on GitHub (Jun 7, 2024):

Adding the optional ca chain (pem) did the trick

@tomse commented on GitHub (Jun 7, 2024): Adding the optional ca chain (pem) did the trick

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#2496

No description provided.

Rows
Columns