Proxy Host config uses wrong path for certificate file when using LetsEncrypt certificates not generated by nginx proxy manager

[gutyex]

• I have a wildcard SSL certificate from LetsEncrypt, which is managed by a separate docker container running certbot-cloudflare.
• The storage from the certbot container is mounted in the certs storage location for nginx proxy manager.
• I have two proxy hosts configured to use this certificate, stored at /etc/letsencrypt/live/mydomain.tld/
  • the certificate shows up in nginx proxy manager's list of SSL certificates as expected.
• The two proxy hosts have been working in this config for several months, including through restarts & updates of the container.
• After opening the config for one of the proxy hosts to check something, I clicked save rather than cancel and the host started showing as offline.
  • No config was changed but I take it that clicking save caused the config file to be re-generated anyway.
  • The other proxy host continues to work with the same certificate
• The error message shown is 'Cannot load certificate "/etc/letsencrypt/live/npm-1/fullchain.pem"'
  • Rather than using "/etc/letsencrypt/live/mydomain.tld/fullchain.pem" it's looking where the certificate would be if it was one that nginx proxy manager generated.

This is running on the TrueNAS Scale App, which is currently on nginx proxy manager version 2.12.1