• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

8.2 does not expire hostings

tkalfaoglu

Silver Pleskian
It seems at times PLESK does not disable the hostings whose expiration date has passed.
Apart from that, the 8.2 has been running trouble-free.

Does anyone know what to check? For example, is there a cron job that does this expiration check once a day that I could run manually to see if it issues an error message, or perhaps it's somehow disabled in cron?

Thanks! -turgut
 
BUMP!

I also have a new glitch: The notification message that is CC:'ed to me when a domain expiration occurs comes BLANK. that is, the subject is filled, but the message body is empty :(
EDIT: FIXED - if you use national characters, the notification goes out BLANK.

However, the previous problem of not shutting down expired hostings, continue.
 
Back
Top