• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Let's Encrypt Saving New Certificates under different Name

smpnjn

New Pleskian
Hi there,

I am not sure if this is solvable, but I have a website encrypted with Let's Encrypt. I use these certificates somewhere else in my application (within the Javascript itself). My Let's Encrypt certificates go out of date about every 3 months, and every time the new certificate is named differently in the /usr/local/psa/var/modules/letsencrypt/etc/archive/ directory. So when I got the first one, it was privkey1.pem, and now I'm onto privkey9.pem.

Whenever this changes, I have to change my application so that the file name is correct. So for example, when privkey8.pem expired, I updated my application to use privkey9.pem. As you can imagine this is manual, and quite annoying to do.

I'd prefer if Let's Encrypt overwrote the previous key, so I only ever had one privkey.pem/fullchain.pem/chain.pem. Is this possible? I would've thought there was a setting somewhere to update how old certificates are dealt with.
 
You could simply use the automatically created symlink to the current certificate files. You'll find the symlinks here:
/usr/local/psa/var/modules/letsencrypt/etc/live/yourdomain.tld

In there, there is a symlink to /usr/local/psa/var/modules/letsencrypt/etc/archive/yourdomain.tld/fullchainXX.pem etc.
The name of the symlink never changes, so you won't have to do any manual work when a cert was renewed.
 
Back
Top