• 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.

Plesk time and licence failure

S

sunmacet

Guest
Hello,

I just adjusted our server clock to correct time (4 minutes backwards) and now Plesk says that our licence is expired. There was almost one year left of our licence.

How I can fix this issue and adjust our clock to correct time? This is just stupid that this small adjustment can do this...

Thanks for any help.

Regards.
 
same thing just happened to me. Seem that the system time jumped ahead one year!

a php date function shows "2008-12-02 10:12:41" - should be 2007

anyone got a fix?
 
To set the system clock under Linux, use the date command. As an example, to set the current time and date to July 31, 11:16pm, type ``date 07312316'' (note that the time is given in 24 hour notation). If you wanted to change the year as well, you could type ``date 073123161998''. To set the seconds as well, type ``date 07312316.30'' or ``date 073123161998.30''. To see what Linux thinks the current local time is, run date with no arguments.
 
Thanks hostingguy

that did the trick!!!

It seems that when updating the sys time in plesk - the year field is defaulting to "2008"
 
Back
Top