[GH-ISSUE #4008] Impossible to upload custom certificate #2614

Open
opened 2026-02-26 07:36:13 +03:00 by kerem · 3 comments
Owner

Originally created by @trisosamu on GitHub (Sep 19, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4008

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)?
    • No

Describe the bug

Nginx Proxy Manager Version

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'SSL Certificate'
  2. Click on '.Ass SSL Certificate'
  3. Scroll down to '.Custom'
  4. Upload all file with .pem extension

Screenshots

Operating System

Originally created by @trisosamu on GitHub (Sep 19, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4008 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **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)? - No **Describe the bug** <!-- Impossible to upload custom certificate like let's encrypt wildcard with .pem extension --> **Nginx Proxy Manager Version** <!-- v2.11.3 --> **To Reproduce** Steps to reproduce the behavior: 1. Go to 'SSL Certificate' 2. Click on '.Ass SSL Certificate' 3. Scroll down to '.Custom' 4. Upload all file with .pem extension **Screenshots** <!-- <img width="484" alt="Screenshot 2024-09-19 alle 10 45 33" src="https://github.com/user-attachments/assets/bf0c7b45-3e7b-4179-8c3a-222c9782cb5d"> --> **Operating System** <!-- Mac, Chrome. -->
Author
Owner

@github-actions[bot] commented on GitHub (May 17, 2025):

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

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

@SQ9MDD commented on GitHub (Nov 12, 2025):

Same issue here

I’m experiencing the exact same problem.
When I try to add a custom certificate, the Certificates interface freezes or breaks — it stops loading completely afterward.

I tried uploading valid .pem and key files, but after clicking Save the UI hangs and the certificate never appears. Restarting the container or clearing cache doesn’t help.

<!-- gh-comment-id:3524060674 --> @SQ9MDD commented on GitHub (Nov 12, 2025): Same issue here I’m experiencing the exact same problem. When I try to add a custom certificate, the Certificates interface freezes or breaks — it stops loading completely afterward. I tried uploading valid .pem and key files, but after clicking Save the UI hangs and the certificate never appears. Restarting the container or clearing cache doesn’t help.
Author
Owner

@moseslecce commented on GitHub (Nov 13, 2025):

When I try to upload a custom wildcard certificate, I notice in the logs it does not include a domain name:

id: 12,
expires_on: '2026-07-21 23:59:59',
domain_names: [ null ]

and upon reloading the certificate page it will go blank due to an error:

Uncaught TypeError: Cannot read properties of null (reading 'includes')
at h (DomainsFormatter-DRGLydBn.js:1:109)
at ld (index-BBAG1AZl.js:49:48769)
at M0 (index-BBAG1AZl.js:49:71656)
at nS (index-BBAG1AZl.js:49:82048)
at LS (index-BBAG1AZl.js:49:117928)
at aI (index-BBAG1AZl.js:49:116966)
at tg (index-BBAG1AZl.js:49:116794)
at xS (index-BBAG1AZl.js:49:113564)
at qS (index-BBAG1AZl.js:49:125603)
at Ad (index-BBAG1AZl.js:49:124155)

Here is the relevant code snippet:

import {j as e, d as c, ad as m, c as d} from "./index-BBAG1AZl.js";
const h = ({domain: s, color: n}) => {
let a;
return s.includes("*") && (a = l => l.preventDefault()),
e.jsx("a", {
href: http://${s},
target: "_blank",
onClick: a,
className: d("badge", n ? bg-${n}-lt : null, "domain-name", "me-2"),
children: s
}, s)
}

<!-- gh-comment-id:3528598387 --> @moseslecce commented on GitHub (Nov 13, 2025): When I try to upload a custom wildcard certificate, I notice in the logs it does not include a domain name: id: 12, expires_on: '2026-07-21 23:59:59', domain_names: [ null ] and upon reloading the certificate page it will go blank due to an error: Uncaught TypeError: Cannot read properties of null (reading 'includes') at h (DomainsFormatter-DRGLydBn.js:1:109) at ld (index-BBAG1AZl.js:49:48769) at M0 (index-BBAG1AZl.js:49:71656) at nS (index-BBAG1AZl.js:49:82048) at LS (index-BBAG1AZl.js:49:117928) at aI (index-BBAG1AZl.js:49:116966) at tg (index-BBAG1AZl.js:49:116794) at xS (index-BBAG1AZl.js:49:113564) at qS (index-BBAG1AZl.js:49:125603) at Ad (index-BBAG1AZl.js:49:124155) Here is the relevant code snippet: import {j as e, d as c, ad as m, c as d} from "./index-BBAG1AZl.js"; const h = ({domain: s, color: n}) => { let a; return s.includes("*") && (a = l => l.preventDefault()), e.jsx("a", { href: `http://${s}`, target: "_blank", onClick: a, className: d("badge", n ? `bg-${n}-lt` : null, "domain-name", "me-2"), children: s }, s) }
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#2614
No description provided.