• 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 Plesk Let's Encrypt extension still leaves garbage behind in .well-known/acme-challenge/ directories

burnley

Regular Pleskian
Posted my question here as well, since it's become a major nuisance for us and we want it fixed:
[FIXED BUG] Let's Encrypt challenge files are not removed from .well-known/acme-challenge/ directories

Just stumbled on this article after a major clean up on our Linux plesk servers, littered with millions of such stale files. Now running Plesk Obsidian
Version 18.0.23 Update #3 with Let's Encrypt extension Version 2.8.6-571 on all of them since 5th of February and we're still seeing thousands of challenge files created and left scattered around. Both in /var/www/vhosts/<vhost>/httpdocs/.well-known/acme-challenge/ as well as /var/www/vhosts/default/htdocs/.well-known/acme-challenge/


How should we configure Plesk to have this issue fixed once and for all? Reading Managing Let’s Encrypt Settings I haven't found anything that tackles the removal of old files. Are we supposed to set up our own cron jobs for this?
 
There should be a cronjob configured to remove these files if they are older than 1 month:

Bash:
$ sudo crontab -l -u psaadm | grep "remove-expired-tokens"

Output should be:
Code:
0       0       *       *       0       /opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/letsencrypt/scripts/remove-expired-tokens.php'
 
Back
Top