[GH-ISSUE #1676] Button not working for Add Certificate --> Custom #1254

Closed
opened 2026-02-26 06:36:25 +03:00 by kerem · 9 comments
Owner

Originally created by @ctrlzed on GitHub (Dec 23, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1676

Describe the bug
On the SSL Certificates tab, adding a custom certificate does not open a drop-down dialog, hence custom certificates cannot be added.
Adding a Let's Encrypt certificate via the same button works fine.

Nginx Proxy Manager Version
v2.9.13

To Reproduce
Steps to reproduce the behavior:

  1. Go to the "SSL Certificates" tab
  2. Click on "Add SSL Certificate"
  3. Click on "Custom"
  4. No action occurs.

Expected behavior
A drop down dialog is presented to allow the user to add a certificate

Screenshots
N/A - No error or screen of any kind is presented. But something should happen when you click this button.

Operating System
Unraid 6.9.2 (via Docker)

Additional context

Originally created by @ctrlzed on GitHub (Dec 23, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1676 **Describe the bug** On the SSL Certificates tab, adding a custom certificate does not open a drop-down dialog, hence custom certificates cannot be added. Adding a Let's Encrypt certificate via the same button works fine. **Nginx Proxy Manager Version** v2.9.13 **To Reproduce** Steps to reproduce the behavior: 1. Go to the "SSL Certificates" tab 2. Click on "Add SSL Certificate" 3. Click on "Custom" 4. No action occurs. **Expected behavior** A drop down dialog is presented to allow the user to add a certificate **Screenshots** N/A - No error or screen of any kind is presented. But something should happen when you click this button. **Operating System** Unraid 6.9.2 (via Docker) **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. -->
kerem 2026-02-26 06:36:25 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@krautech commented on GitHub (Dec 24, 2021):

Fix doesnt work

<!-- gh-comment-id:1000596448 --> @krautech commented on GitHub (Dec 24, 2021): Fix doesnt work
Author
Owner

@moeik commented on GitHub (Dec 24, 2021):

Fix doesnt work

Me too.

<!-- gh-comment-id:1000600170 --> @moeik commented on GitHub (Dec 24, 2021): > Fix doesnt work Me too.
Author
Owner

@felixoswald commented on GitHub (Dec 24, 2021):

can confirm this with docker :latest image (v2.9.13)

console log on chrome
image

edit:
with #1677 (docker :github-pr-1677) and clearing cache it works again

<!-- gh-comment-id:1000778749 --> @felixoswald commented on GitHub (Dec 24, 2021): can confirm this with docker :latest image (v2.9.13) console log on chrome ![image](https://user-images.githubusercontent.com/52625423/147344882-c9a7f719-bc43-4eac-9bdb-d4116d9e67a2.png) edit: with #1677 (docker :github-pr-1677) and clearing cache it works again
Author
Owner

@chaptergy commented on GitHub (Dec 24, 2021):

@krause3284 @moeik See https://github.com/jc21/nginx-proxy-manager/pull/1677#issuecomment-1000866294

<!-- gh-comment-id:1000867214 --> @chaptergy commented on GitHub (Dec 24, 2021): @krause3284 @moeik See https://github.com/jc21/nginx-proxy-manager/pull/1677#issuecomment-1000866294
Author
Owner

@krautech commented on GitHub (Dec 24, 2021):

@chaptergy after pulling it twice and clearing the cache a bunch of times, it decided to work. Not sure why the initial clearing of cache didn't work. Thank you!

<!-- gh-comment-id:1000907530 --> @krautech commented on GitHub (Dec 24, 2021): @chaptergy after pulling it twice and clearing the cache a bunch of times, it decided to work. Not sure why the initial clearing of cache didn't work. Thank you!
Author
Owner

@hoochster commented on GitHub (Dec 25, 2021):

I am having this issue as well, have tried clearing cache multiple times, different browsers etc. Have wiped/reinstalled multiple times all having same issue. This worked just fine a couple days ago. Let me know if you need me to provide anything. One thing I have noted that might not be related, but first time connecting to site, gives a Warning of invalid signature in the log.

[12/25/2021] [6:42:03 PM] [SSL ] › ℹ info Renew Complete
[12/25/2021] [6:42:18 PM] [Express ] › ⚠ warning invalid signature

I apologize, I mispoke this. I saw others state the fix posted above not working so being typical, didn't even try it. But just did and cleared cache and it worked. Thank you so much.

<!-- gh-comment-id:1001060548 --> @hoochster commented on GitHub (Dec 25, 2021): I am having this issue as well, have tried clearing cache multiple times, different browsers etc. Have wiped/reinstalled multiple times all having same issue. This worked just fine a couple days ago. Let me know if you need me to provide anything. One thing I have noted that might not be related, but first time connecting to site, gives a Warning of invalid signature in the log. [12/25/2021] [6:42:03 PM] [SSL ] › ℹ info Renew Complete [12/25/2021] [6:42:18 PM] [Express ] › ⚠ warning invalid signature I apologize, I mispoke this. I saw others state the fix posted above not working so being typical, didn't even try it. But just did and cleared cache and it worked. Thank you so much.
Author
Owner

@averyhox commented on GitHub (Dec 26, 2021):

After using the #1677 fix, it did not initially work on Edge browser, showing the same errors as above. However, once I swapped to a privacy window it worked fine. The next day, when I re-loaded my npm and database, it worked fine without a privacy window.

I believe #1677 does fix the issue (at least for me), but something was hanging in my browser (cache) preventing it from working.

<!-- gh-comment-id:1001216797 --> @averyhox commented on GitHub (Dec 26, 2021): After using the #1677 fix, it did not initially work on Edge browser, showing the same errors as above. However, once I swapped to a privacy window it worked fine. The next day, when I re-loaded my npm and database, it worked fine without a privacy window. I believe #1677 does fix the issue (at least for me), but something was hanging in my browser (cache) preventing it from working.
Author
Owner

@robertfraefel commented on GitHub (Dec 29, 2021):

same here:
image

does not work with a brand new installation :latest

<!-- gh-comment-id:1002433936 --> @robertfraefel commented on GitHub (Dec 29, 2021): same here: ![image](https://user-images.githubusercontent.com/33721995/147637553-db5ccd1f-412b-473c-97cb-a7724aa8e285.png) does not work with a brand new installation :latest
Author
Owner

@chaptergy commented on GitHub (Dec 29, 2021):

@robertfraefel There hasn't been a new release yet, you'll have to wait for 2.9.14 or use the pr image.

<!-- gh-comment-id:1002454101 --> @chaptergy commented on GitHub (Dec 29, 2021): @robertfraefel There hasn't been a new release yet, you'll have to wait for 2.9.14 or use the pr image.
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#1254
No description provided.