[Minor Bug]: Wrong dates (Created/Expires) shown on custom SSL certificate

[agent-ck]

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image? => Yes (Repulling the image was exactly the reason, I reviewed the configuration.)
• Are you sure you're not using someone else's docker image? => Yes (The original is the best one!)
• Have you searched for similar issues (both open and closed)? => Yes, but not very deep.

Describe the bug

• When using a custom SSL certificate which will be feed from external by automation scripts,
  the wrong dates (Created/Expires) will be shown.
• Functionality is not affected as the right certificate will be provided in configured clients.
• Therefore it's a minor bug with absolute no priority.

Nginx Proxy Manager Version

• v2.10.3 © 2022 jc21.com.

To Reproduce Steps to reproduce the behavior:

1. Configure a Custom SSL certificate. (No need to assign it.)
2. Notice the dates (Created/Expires)
3. Wait until the certificate has been renewed
4. Deploy the certificate by exchanging the files directly
5. Restart npm
6. Review the custom certificate
7. See the initial displayed dates instead of the real dates of the certificate.

Expected behavior

• Expected is, that the dates will be read directly from the certificate, at least when npm application is started.
• Instead it looks like, that the certificate will be read only once when uploaded and then never again.

Screenshots

• Certifcate configuration:

• Real certificate:

Operating System

• Docker on Debian11

Additional context

• In the affected environment, an internal Certificate is used, which will be created and deployed 100% automatically. The deployment is done by exchanging the certificate files directly and restarting the containers afterwards.

[Heisenberg2024]

While it doesn't really affect the usage, I would also like him to update the date automatically, or manually update the date by executing a certain command from inside the container

[github-actions[bot]]

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

[wakawakaaa]

yes please this issue needs to be fixed.