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

Resolved Invalid Time Stamps post 18.0.53 Upgrade

nmdpa3

Regular Pleskian
Username:

TITLE

Invalid Time Stamps post 18.0.53 Upgrade

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 18.0.5.3, Ubuntu 22.04

PROBLEM DESCRIPTION

After upgrading Ubuntu 22.04 to Plesk 18.0.53 from Plesk 18.0.52 Update #3, domain logs are showing log entries with UTC timestamps. Additionally, Plesk GUI displayed times, like the last date/time the system was checked for updates (on the main Plesk screen), are also now displaying with a UTC timestamp. Prior to the 18.0.53 update, all mentioned times were displayed as our system and Plesk defined timezone, which was displaying EST.

STEPS TO REPRODUCE

Upgrade any Ubuntu 22.04 system from Plesk 18.0.52 Update #3 to Plesk 18.0.53

ACTUAL RESULT

Times displayed in UTC and not in the expected system and Plesk set timezone.

EXPECTED RESULT

Timestamps being properly displayed to match the system and Plesk defined timezone.

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Researching on this a bit more showed that it is indeed a known issue. A hotfix is on the way and should be applied to affected servers soon. PPP-61655 and PPP-61654.
 
Back
Top