Certificate tab stays empty: Uncaught TypeError DomainsFormatter.js

[bentschrader]

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 After the update to version 2.13.x my certficate tab stays empty.

The console of my browser give me this error mesage:

Nginx Proxy Manager Version Bug starting from version 2.13.0, could reproduce the behaviour since 2.13.4.

To Reproduce Steps to reproduce the behavior:

1. Update to version 2.13.x'
2. Click on 'Certificates'
3. See error - the page is empty, console shows the error

Expected behavior This is what the certficates tab shows me still version 2.12.6

[lastsamurai26]

Strange i updated from 2.16.3 to the lastest. And at the moment i can't reproduce it.

Can you try the spinup a new instance the 2.16.x and update this again ?

[baszied]

I just deployed NginxProxyManager for the very first time with ProxmoxVE helper script and encountered the same issue. Couldn't find a similar issue yesterday but glad to see it's not just me... I see the script pull latest which is 2.13.4... The screen becomes blank after I add a first custom certificate

Chrome devtools tells me that this is the exception DomainsFormatter-BoT6f4EV.js:1 Uncaught TypeError: Cannot read properties of null (reading 'includes') at h (DomainsFormatter-BoT6f4EV.js:1:109) at ud (index-gIHubYKY.js:49:48769) at M0 (index-gIHubYKY.js:49:71656) at rT (index-gIHubYKY.js:49:82048) at DT (index-gIHubYKY.js:49:117928) at iO (index-gIHubYKY.js:49:116966) at ag (index-gIHubYKY.js:49:116794) at CT (index-gIHubYKY.js:49:113564) at YT (index-gIHubYKY.js:49:125603) at Ad (index-gIHubYKY.js:49:124155)

[bentschrader]

I can confirm the behaviour. I deployed a fresh LXC container and did run the Proxmox VE Helper Script (https://community-scripts.github.io/ProxmoxVE/scripts?id=nginxproxymanager). Calling the certificate page (which worked one time) and added my custom certificate ended up again in the same failure. Same exception in Edge as in Chrome. I have another instance running (with version 2.13.4) with Letsencrypt HTTP certificates which does not have any problem so far.

[jc21]

This is probably a cert that doesn't have domains defined in the meta data. I'll try myself.

[jacogasp]

Hello,

I stumbled on this issue since I'm experiencing the certificates page "crash". I'm happy that @jc21 already found the issue and came up with a fix.

Just wanted to confirm that the issue is on the empty domain name. I manually edited the sqlite row in the database like

sqlite> update certificate set domain_names='["wireguard.lan"]' where id=7;

and the page starts to work again.