Updating Plesk Onyx to Plesk Obsidian now also replaces the old default pages with brand new ones introduced in Plesk Obsidian 18.0.21 (unless the default pages have been customized, in which case they are not replaced).
Plesk Administrator can now force all subscriptions to only use the Dynamic, Active, or Classic list by adding the following lines to the panel.ini file:
[navigation]
forceWebsiteList = dynamic (or = active, or = classic)
It is also possible to hide one or more options from the list:
[navigation]
hideWebsiteList = active, classic
The FileServer component is no longer supported. It will no longer be installed on new Plesk Obsidian servers, but updating to Plesk Obsidian 18.0.24 will not affect this component if it was already installed.
A new SDK method pm_Domain::getHostingParam has been introduced. It is used for retrieving information about hosting settings of domains. The method enables user-created extensions to use SDK instead of API RPC or direct database queries.
File indexing was improved for the purposes of creating backups. Plesk no longer tries to include removed files in backups. (PPPM-6486)
When moving addon domains between subscriptions, users are now warned that any databases owned by those domains must be reassigned manually.
.webp files can now be used with the plesk bin branding_theme utility to apply custom themes to Plesk Obsidian. (PPPM-11426)
Accidentally removed SSL/TLS certificates are now automatically restored from the Plesk database when a domain’s hosting settings are changed.
Backing up a subscription with one or more mail accounts with the autoresponder enabled no longer results in the “Unable to back up autoresponder settings.” error if no mail server is installed. (PPP-47307)
Plesk no longer allows the creation of non-TXT DNS records containing the underscore (“_”) character. Having one or more such records in a DNS zone hosted in Plesk caused the bind DNS server fail to start. (PPPM-11448)
Email notifications sent by Plesk servers no longer contain the duplicate “Content-Type” header, which caused them to be bounced during local delivery. (PPPM-11530)
Dumps of MySQL databases are now correctly included in server-wide Plesk backups. (PPPM-11575)
Creating a backup no longer fails if usernames of one or more clients being backed up contain the ampersand (“&”) character. (PPP-47205)
Passive mode is now turned on by default in the FTP storage settings. (PPPM-11461)
Creating a full server backup no longer produces misleading error messages if the cuBackupRestoreHelper.php file is corrupted. (PPP-47304)
Backing up a subscription no longer results in an invalid backup if the subscription’s DNS zone contains one or more DNS records of the type “none”. (PPP-47209)
Backing up a subscription no longer fails if one or more files or directories owned by the subscription could not be read at the time of backup creation (Note: unreadable files and directories are not included in the resulting backup). (PPP-47164)
Creating a full server backup no longer results in an invalid backup if certain fields in the backup properties have empty values. (PPP-47207)
Plesk email notifications are now shown in Thunderbird 68.4.2. (PPP-47282)
It is now possible to upload a file whose name contains square brackets ([ or ]) via File Manager. (PPPM-5294)
Replaced the “Call to a member function getErrorObjects() on null” error message with a more meaningful one when a backup, under certain circumstances, fails to be created. (PPP-47502)
It is no longer possible to secure anything with an invalid SSL/TLS certificate whose *.crt part is missing. (PPPM-11458)
If the mail service for a domain or a subscription (for example, example.com) is disabled, the plesk bin subscription -i example.com command no longer fails. (PPP-45257)
A directory with the “0” name can now be opened in File Manager. (PPPM-11541)
A reseller can now install an SSL/TLS certificate via an XML-RPC request without specifying the ip_address option value. (PPPM-11577)
Updating to Plesk Obsidian now preserves a custom branding and color scheme (if it is set) and no longer changes it to the default Obsidian color scheme. (PPPM-11511)
If the DNS component is not installed, running the plesk repair all -y command no longer shows the “The NS configuration file … is absent” error. (PPPM-11479)
Access from property now works again in API RPC. (PPPM-11559)
Linux
Accessing AWStats data for domains hosted in Plesk no longer results in the “404 Not Found” error. (PPPM-11342)
Creating a backup on a Plesk Server with the “Acronis Backup” extension installed no longer results in the “Not all the data from /usr/local/psa/var/modules/acronis-backup/ was backed up successfully.” error. (PPPM-11587)
Creating a backup on a Plesk Server with the “Fail2Ban” component removed no longer results in an unnecessary warning. (PPPM-11521)
Restoring a subscription no longer results in a warning if the subscription’s system user is using the “bash (chrooted)” shell and the chrooted template has been customized. (PPPM-11515)
Downloading a large backup file (10 GB or more) from Plesk no longer fails with the the “Network Error” message shown in a browser. (PPP-44962)
The issue with the plesk repair utility that could not fix issues with the missing libmyodbc5.so package is no longer relevant because Plesk now uses its own plesk-libmaodbc driver. (PPP-37827)
“Mail for Non-Existent Users” can now be enabled even if the “Bounce with message” text field is empty. (PPPM-11556)
When restoring a number of domains from a backup, SSL/TLS certificates that secure these domains are now also restored. (PPPM-9686)
Webserver Configuration Troubleshooter no longer shows that some configs are broken when they are actually not after reconfiguration (for example, after domain’s hosting settings were changed but these changes did not propagate yet). (PPPM-6752)
Plesk now shows an explicit message what to do with custom web server configuration templates (if any) during update to Plesk Obsidian. (PPPM-11580)
SSL/TLS certificates from Let’s Encrypt can now be used for client certificate authorization. (PPPM-11544)
Custom error pages now work when nginx-only hosting is enabled. (PPPM-8889)
