Button not working for Add Certificate --> Custom

[ctrlzed]

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

[krautech]

Fix doesnt work

[moeik]

Fix doesnt work

Me too.

[felixoswald]

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

console log on chrome

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

[chaptergy]

@krause3284 @moeik See #1677 (comment)

[krautech]

@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!

[hoochster]

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.

[averyhox]

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.

[robertfraefel]

same here:

does not work with a brand new installation :latest

[chaptergy]

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