Learn how to install Plesk updates

Legend:

new feature

functionality improved

issue resolved

pay attention

23 November 2017

Plesk Onyx 17.5.3 Update 31

Linux

  • On AWS, a new instance, created from a snapshot of Plesk on Ubuntu 16.04 instance, had wrong IP mapping, which made websites on the instance unavailable. (PPPM-7517)

21 November 2017

Extension Updates

WordPress Toolkit 2.4.1

  • The option to turn off rsync usage for synchronization on Linux was added to Global Settings.
  • Addendio service was displaying detached WordPress instances in its drop-down menu. (EXTWPTOOLK-899)
  • Successful server backup was adding a warning in the log. (EXTWPTOOLK-991)

16 November 2017

Plesk Onyx 17.5.3 Update 30

Linux

  • On CentOS 7, Red Hat Enterprise Linux 7 and CloudLinux 7 with Roundcube webmail, files could not be attached to mail messages. (PPPM-7470)

Plesk Onyx 17.0.17 Update 41

Linux

  • On CentOS 7, Red Hat Enterprise Linux 7 and CloudLinux 7 with Roundcube webmail, files could not be attached to mail messages. (PPPM-7470)

Extension Updates

WordPress Toolkit 2.4.0

  • Users can specify custom administrator login URL on the “Login Settings” page. This complements various WordPress plugins that change the login URL for security reasons.
  • Server Administrator can create sets of themes and plugins for preinstallation with WordPress on new subscriptions.
  • On Linux, rsync is now used to synchronize files between instances. This improves performance and adds two more sync options: one allows replacing newer files modified on target (enabled by default), another allows removing files from target that were removed from the source.
  • Hosting plans have a new option to preinstall WordPress with an optional predefined set of themes and plugins on newly created subscriptions.
  • Multiple WordPress Toolkit settings previously available only via editing panel.ini file can now be changed by the server administrator on the Global Settings page of WordPress Toolkit.
  • WP-CLI utility was updated to version 1.4.
  • WordPress Toolkit could not update secret keys in wp-config.php if some of the keys were missing. (EXTWPTOOLK-795)
  • Mass update procedure was stopped if a single theme or plugin could not be updated. We have convinced the procedure to continue as usual in this case, and display a warning instead. (EXTWPTOOLK-943)
  • Broken WordPress instances registered in WPT could not be repaired by performing data sync from a working instance. (EXTWPTOOLK-904)
  • WordPress Drop-Ins were displayed on the “Manage Plugins” page as inactive plugins without descriptions. Attempting to activate them from this page resulted in errors. Now Drop-Ins are not displayed in the plugin list. (EXTWPTOOLK-967)
  • When securing database for a WordPress instance, wp_ substring was replaced not only in the beginning, but also in the middle of table names. (EXTWPTOOLK-905)
  • Some operations performed by customers were logged as if they were performed by the server administrator. (EXTWPTOOLK-774)
  • On Windows servers it was impossible to clone WordPress instances with files that had spaces in their names. (EXTWPTOOLK-785)
  • Under certain circumstances, switching languages took up to several minutes. (EXTWPTOOLK-797)
  • After removing a domain that had a subdomain with a WordPress instance registered in WordPress Toolkit, the user could still see this instance in WordPress Toolkit. (EXTWPTOOLK-784)
  • Setting skip_name_resolve = on in the MySQL server configuration resulted in failure to clone instances. (EXTWPTOOLK-806)
  • In some cases WordPress Toolkit did not detect and notify users that a website stopped responding after WordPress instance synchronization. (EXTWPTOOLK-778)
  • Addendio service sometimes tried to install Addendio PLUS plugin when it was already installed, which resulted in a warning in the panel.log file. (EXTWPTOOLK-913)
  • When Resellers used system-wide search, they could see WordPress instances that did not belong to them or their customers. (EXTWPTOOLK-917)

14 November 2017

Plesk Onyx 17.5.3 Update 29

  • Users logging in to a cloud service Plesk instance that is being deployed will now be greeted by a maintenance screen. They can start using Plesk once the deployment is finished and the maintenance screen is removed.

Third-Party Component Updates

Linux
  • Roundcube was updated from version 1.2.5 to 1.2.7. This is a security update, related to a serious vulnerability in Roundcube (see the details).

    We encourage all Plesk for Linux users to upgrade Plesk.

Plesk Onyx 17.0.17 Update 40

Third-Party Component Updates

Linux
  • Roundcube was updated from version 1.2.5 to 1.2.7. This is a security update, related to a serious vulnerability in Roundcube (see the details).

    We encourage all Plesk for Linux users to upgrade Plesk.

7 November 2017

Plesk Onyx 17.5.3 Update 28

  • Users now can add, remove, and replace plan items on demand using the extensions SDK.
  • Under certain circumstances, an attempt to move directory or file in File Manager resulted in an error. (PPPM-6398)

Linux

  • The Cgroups Manager did not allow to set the CPU limit value above 999% on machines with 10 or more CPU threads. (PPPM-5953)
  • In File Manager, copying directory to a path where another directory with the same name existed resulted in former directory added as a subdirectory of the latter, instead of overwriting it. (PPPM-6398)
  • A subscription, having invalid v4 and v6 IP’s assigned to it, was shown twice on the subscriptions page. (PPPM-6950)

Windows

  • Under certain circumstances, the C:\Program Files (x86)\Plesk\admin\repository\registry.xml file became empty, which resulted in Plesk becoming inaccessible. (PPPM-7233)
  • Under certain circumstances, the plesksrv service crashed with an unhanded exception 0xE06D7363 resulting in Plesk becoming inaccessible. (PPPM-7135)

Plesk Onyx 17.0.17 Update 39

  • Users now can add, remove, and replace plan items on demand using the extensions SDK.

Linux

  • The Cgroups Manager did not allow to set the CPU limit value above 100%. (PPPM-5953)

2 November 2017

Extension Updates

Plesk Migrator 2.12.0

  • Now you can run pre-migration checks in the advanced migration mode. Successfully passing all checks automatically starts a migration.
  • Performance of scanning source server contents before importing sites has been drastically improved.
  • When preparing for a site import, one of the applications being unavailable resulted in failure to detect other applications and list them on the site import page. (PMT-4061)
  • When transferring a subscription from Plesk Onyx, only a single scheduled task was transferred to the target server. (PMT-3894)
  • When migrating a subscription from Plesk 11.5 or later, the password for site application database was not decrypted on the target server, which resulted in the application unable to work on the target server. (PMT-4026)
  • When migrating from a Linux server with Plesk Onyx, pre-migration checks did not detect it when the webmail, used on the source server, was missing on the target server. (PMT-3145)
  • A component, required by Plesk Migrator, was not bundled with it but instead downloaded before first site import. This could result in migration failure in case of network problems. Now the component is a part of Plesk Migrator and does not require separate downloading. (PMT-3735)
  • When migrating from Plesk servers, the APS applications were transferred only as content and not registered in Plesk. (PMT-4000)
Linux
  • The migration process was aborted if any customer’s login name did not conform to the Plesk requirements (only alphanumeric characters and -.'%_). Now subscriptions owned by such customers are skipped during the migration. (PMT-3959)
  • Migration to a server with administrator’s id different than the default one (1) resulted in failure to repeatedly migrate subscriptions or synchronize their content. (PMT-3078)
  • When migrating from Confixx, each transferred SSL certificate was installed as default certificate for all domains on the IP address, which resulted in all domains using the certificate of the latest migrated domain. (PMT-4043)
Windows
  • When migrating a subscription with a database and ODBC DSN (Data Source Name) from Plesk for Windows of version 12.5 or later, the DSN was not migrated. (PMT-3891)
  • Migration failed from a server having IP addresses with netmask set in short notation. (PMT-4048)
  • When migrating a subscription with web.config containing non-ASCII characters from a server with .NET 2.0 or 3.x to a server with only .NET 4.x, adjusting the web.config to the target server failed. (PMT-4029)

30 October 2017

Plesk Onyx 17.8 Preview 7

  • All newly installed Plesk servers now come with a preinstalled Plesk Onyx Web Pro edition trial license valid for 14 days.
  • The PHP extension ionCube Loader is now shipped with Plesk PHP 7.1.
  • The Plesk Welcome screen has been redesigned. Now, when customers log in to Plesk for the first time, they need to provide only the contact name, email, and password.
  • Users now can add, remove, and replace plan items on demand using the extensions SDK.
  • Multiple performance improvements related to backing up to cloud remote storages.
  • Users logging in to a cloud service Plesk instance that is being deployed will now be greeted by a maintenance screen. They can start using Plesk once the deployment is finished and the maintenance screen is removed.
  • The functionality of Plesk File Manager editors (Code Editor, Text Editor, and HTML Editor) has been improved. Now, when users save changes (by clicking “Apply” or using the CTRL+S key combination), the editor page is not reloaded, the text cursor keeps its position, and the editor does not lose focus. In addition, the editor windows now adjust their height to the screen size.
  • The “Hide controls for rejection messages for non-existent mail addresses” checkbox in “Tools & Settings” > “Interface Management” > the “Interface Controls Visibility” tab did not work. (PPP-31117)
  • It was not possible to create a customer with the contact name containing the exclamation mark character (!) via the CLI. (PPP-27385)
  • Backup Manager did not display any information in the “System notes” column for backups created by users other than the Plesk session owner. (PPP-31703)
  • It was not possible to create a domain with the name containing IDN characters if the DNS template contained a TXT record including the <domain> placeholder. (PPP-32897)

Linux

  • Phusion Passenger was updated to version 5.1.11.
  • The plesk repair utility with the web aspect now detects and disables missing or corrupted Apache modules.
  • Using passive FTP on Plesk servers deployed from Cloud providers images now requires opening the TCP port range recommended by IANA (49152-65535) in the firewall.
  • Starting with Plesk Onyx 17.8 Preview 7, Debian 7 is no longer supported.
  • Changing the number of entries per page and searching on the “Users” tab of the Plesk file server extension resulted in an error. (PPP-30822)
  • The creation of wildcard subdomains failed if the DNS template contained an SRV record. (PPP-30766)
  • Adding or removing domains on overloaded servers with more than 100 subscriptions could result in an error. (PPP-33098)
  • While specifying the File Sharing settings, it was possible to include invalid characters (for example, the whitespace character) to the web folder root URL, which resulted in nginx failing to start. (PPP-30508)
  • Apache graceful restart failed to stop orphaned php-cgi processes. (PPP-31050)
  • Certain configuration files were not accessible when opening an FTP session. (PPP-28246)
  • On Debian-based OSes, certain information in AWStats (Operating Systems, Browsers, and so on) was not displayed correctly because the “LogFormat” parameter was set to “4” by default. (PPP-32682)
  • The “Tools & Settings” > “Server information” page could be inaccessible if the /etc/mtab file contained an excessively large number of records. (PPP-29199)
  • The /usr/local/psa/bin/reconfigurator.pl utility did not remap IP addresses of domain aliases. (PPP-17104)
  • Sorting log files in the Log Browser by modification date produced a disordered list. (PPP-31792)

Windows

  • It is now possible to connect a remote Microsoft SQL Server 2017 database server installed on Linux for hosing databases.
  • MySQL Server 5.7 was updated to version 5.7.19.
  • MySQL Server 5.6 was updated to version 5.6.36.
  • Plesk SQL Server 5.7 was updated to version to 5.7.19.
  • MySQL Connector/ODBC was updated to version 5.3.7.
  • Plesk administrator’s PHP version was switched to 64-bit resulting in improved performance of backing up to cloud storages.
  • PHP 4 is no longer shipped with Plesk.
  • The libcurl library 7.47.1 was updated to version 7.53.0.
  • Under certain circumstances, the plesksrv service crashed with an unhanded exception 0xE06D7363 resulting in Plesk becoming inaccessible. (PPP-32701)
  • Updating the DrWeb Antivirus database did not result in the “last update date” of Plesk Premium Antivirus displayed in “Tools & Settings” > “Server Components” being updated. (PPP-31197)
  • Under certain circumstances, the C:\Program Files (x86)\Plesk\admin\repository\registry.xml file became empty, which resulted in Plesk becoming inaccessible. (PPP-32634)

Plesk Onyx 17.5.3 Update 27

Third-Party Component Updates

  • PHP 7.1 was updated to version 7.1.11.
  • PHP 7.0 was updated to version 7.0.25.
  • PHP 5.6 was updated to version 5.6.32.

According to php.net, PHP 7.0.25 and PHP 5.6.32 are security releases. We encourage all Plesk users to upgrade PHP to the latest version.

Plesk Onyx 17.0.17 Update 38

  • PHP 7.1 was updated to version 7.1.11.
  • PHP 7.0 was updated to version 7.0.25.
  • PHP 5.6 was updated to version 5.6.32.

According to php.net, PHP 7.0.25 and PHP 5.6.32 are security releases. We encourage all Plesk users to upgrade PHP to the latest version.

24 October 2017

Plesk Onyx 17.5.3 Update 26

Linux

  • Phusion Passenger was updated to version 5.1.11, which includes a fix for a major security issue. We thank our colleagues from cPanel for discovering the vulnerability.

    We highly recommend you to update Plesk.

Plesk Onyx 17.0.17 Update 37

Linux

  • Phusion Passenger was updated to version 5.1.11, which includes a fix for a major security issue. We thank our colleagues from cPanel for discovering the vulnerability.

    We highly recommend you to update Plesk.

17 October 2017

Extension Updates

Let’s Encrypt 2.4.0

  • The customers are now notified by email about automatic certificate renewal, both successful and failed. This behaviour can be configured in Tools & Settings – Notifications.
  • The certificate used for securing mail service will now be renewed and applied automatically. Several issues with renewing certificates were fixed.
  • In error reports, technical details are now grouped together in a collapsed text block.
  • When creating a subscription or domain with an internationalized domain name, automatic installation of a Let’s Encrypt certificate failed. (EXTLETSENC-329)
  • The certificate used for securing Plesk Panel was not shown in the certificate repository. (EXTLETSENC-187)
  • If Let’s Encrypt Authority rejects the request with “Policy forbids issuing for name”, the error message now provides relevant information and a reference link. (EXTLETSENC-202)
Linux
  • When issuing a certificate for a webmail addon domain, if an error occurred, the error message did not provide a relevant explanation. (EXTLETSENC-321)
  • Under certain circumstances, the certificate for Plesk Panel was not renewed upon updating the Let’s Encrypt extension from versions earlier than 2.0. (EXTLETSENC-322)
Windows
  • Domain certificates used for securing Plesk Panel are now actually renewed instead of removing old certificate and issuing a new one. (Only for Plesk 17.8 and later.)
  • Symbolic links to certificates were created with extra \ symbols, which prevented opening them with some applications, for example with notepad.exe. (EXTLETSENC-315)

16 October 2017

Plesk Onyx 17.5.3 Update 25

  • Security improvements.
  • Sending an XML API request with a non-existent secret key resulted in response with message ‘invalid protocol version’. Now a relevant error message is returned. (PPPM-7176)

Linux

  • Using the mchk utility on a mailbox with non-empty Trash resulted in the ‘Email Addresses’ tab on the domain page showing a miscalculated size of this mailbox. (PPPM-6617)
  • Running plesk bin init_conf --init on a Plesk instance with a preset administrator password resulted in resetting this password. (PPP-31393)

Plesk Onyx 17.0.17 Update 36

  • Security improvements.
  • Sending an XML API request with a non-existent secret key resulted in response with message ‘invalid protocol version’. Now a relevant error message is returned. (PPPM-7175)

12 October 2017

Extension Updates

WordPress Toolkit 2.3.1

  • Addendio service is now used by default for installing plugins and themes. Enjoy flexible filtering and additional plugin / theme catalogs to choose from.

    Note: if you have Addendio Plesk Extension installed, please uninstall it to avoid conflicts.

  • When users perform custom WordPress installation, WordPress Toolkit now asks users if they want help with installing plugins.
  • After the discussion with WordPress Security team, the ‘Version information’ security check was removed because it wasn’t useful and generated issues in certain cases. (EXTWPTOOLK-852)
  • After synchronizing instances, the source instance page had information about the target instance. (EXTWPTOOLK-922)

9 October 2017

Plesk Mobile 1.1.0 for Android

  • User interface was adapted for tablets.
  • Server and domain widgets can now be added to the home screen.

Plesk Mobile is available at the Apple App Store and Google Play.

5 October 2017

Extension Updates

Ruby 1.3.4

  • Ruby 2.4 was updated to version 2.4.2.
  • Ruby 2.3 was updated to version 2.3.5.
  • Ruby 2.2 was updated to version 2.2.8.

2 October 2017

Plesk Onyx 17.8 Preview 6

  • The Amazon AWS Migration Tutorial extension was published.
  • Plesk users can now store their backups remotely in Google Drive.
  • For certain extensions, the installed license can now be upgraded from Extensions Catalog.
  • Plesk administrator can now find specific extensions using the Plesk global search found in the top left corner.
  • Plesk administrator can now customize the “My Extensions” screen by rearranging the extensions.
  • Plesk Extensions will now be running on PHP 7.1. We recommend extension vendors to review their code for PHP 7.1 compliance.
  • Most users should observe significant resource consumption decrease along with performance improvements.
  • XML API requests using the session operator with the get operation retrieved expired CP sessions in addition to the currently open CP sessions. (PPP-31651)
  • The isImpersonated() method could not identify that an administrator or a reseller was logged in the Customer Panel as one of their customers. (PPP-32589)
  • Under certain circumstances, it was possible to select more than one item from the left menu panel in Power User view. (PPP-31871)
  • A mistyped time zone name was displayed in Tools & Settings > System Time. (PPP-31324)
  • Code Editor converted line endings to Windows-style with CRLF line terminators. (PPP-32628)

Linux

  • CentOS 7.4, Red Hat Enterprise Linux 7.4 and Debian 9 are now supported.
  • Plesk pages now support gzip encoding.
  • The plesk repair utility with the installation aspect now detects and fixes incorrect permissions and ownership of files in RPM and DEB packages.
  • The plesk repair utility with the fs aspect now detects and fixes incorrect permissions and ownership of files inside httpdocs folders.
  • Under certain circumstances, DMARC service encountered segmentation fault errors. (PPP-32405)
  • On CloudLinux, it was impossible to click the ‘Run Now’ button while adding a cron-style scheduled task for the root user. (PPP-31798)
  • Wildcard subdomains logs were not rotated. (PPP-31787)
  • A customer could potentially gain access to the data owned by the psaadm group. (PPP-32586)
  • Users could not set a four-digit CPU limit in Cgroups Manager. (PPP-32603)
  • Multiple simultaneous attempts to renew a Let’s Encrypt SSL/TLS certificate via different Plesk sessions could result in Apache stopping and failing to start. (PPP-31345)

Windows

  • Users can now log in to Plesk servers installed on Active Directory Domain Controller via FTP using their short names.
  • ASP.NET Core 2.0 is now supported.
  • ASP.NET Core 1.1 was updated to version 1.1.2.
  • ASP.NET Core 1.0 was updated to version 1.0.5.
  • The plesk version CLI command now shows the revision number of the latest installed microupdate.
  • Plesk administrator no longer can add IP addresses to or remove them from a network interface with DHCP enabled.
  • MSSQL 2008 server is no longer shipped with Plesk.
  • Plesk Log Browser sometimes displayed information from old, rotated IIS logs if log rotation was enabled on the server. (PPP-31004)
  • Users could not stop or recycle IIS application pools in Internet Explorer 11. (PPP-31537)
  • Microsoft SQL Server database dumps sometimes failed to be restored. (PPP-31565)
  • Under specific circumstances, invalid entries could be added to domains’ list of servers allowed to request DNS zone transfer in the DNS Manager. (PPP-31212)
  • Users could not delete TXT DNS records containing capital letters. (PPP-32671)
  • Attempts to repair the mail server that is not installed via the plesk repair utility resulted in a confusing error message. (PPP-31425)
  • Users could not import Microsoft SQL Server databases if the local administrator user was renamed. (PPP-31545)
  • Using the plesk repair utility failed to set the correct identity for IIS application pools. (PPP-31280)

Plesk Onyx 17.5.3 Update 24

  • Security improvements.
  • Restricting administrative access with ‘IP Access Restriction’ resulted in access being restricted for customers and resellers as well. (PPPM-6498)

Linux

  • On CentOS 7 servers, SELinux module restricted Plesk Update Manager from running rpm package scripts, which resulted in failure to update certain packages. (PPPM-6338)
  • On CloudLinux servers with enabled cagefs, the cron job for renewing Let’s Encrypt certificates failed with message ‘this program can not be run as root’. (PPPM-7018, PPP-31798)
  • Plesk used a Postfix-specific version of sendmail-wrapper, which resulted in cron tasks failing due to non-empty output of plesk sendmail command. (PPPM-7138, PPPM-7148)
  • On CentOS 7 servers, sendmail-wrapper reported errors when resolving mail aliases. (PPPM-7139)

Windows

  • Creating server backup failed, if the server had a domain with a Let’s Encrypt certificate. (PPPM-6126)

Third-Party Component Updates

  • PHP 7.0 was updated to version 7.0.24.
  • PHP 7.1 was updated to version 7.1.10.

Plesk Onyx 17.0.17 Update 35

  • CentOS 7.4 and Red Hat Enterprise Linux 7.4 are now supported.
  • Security improvements.
  • Restricting administrative access with ‘IP Access Restriction’ resulted in access being restricted for customers and resellers as well. (PPPM-6498)

Linux

  • On CentOS 7 servers, SELinux module restricted Plesk Update Manager from running rpm package scripts, which resulted in failure to update certain packages. (PPPM-6338)

Third-Party Component Updates

  • PHP 7.0 was updated to version 7.0.24.
  • PHP 7.1 was updated to version 7.1.10.

28 September 2017

Extension Updates

Security Advisor 1.5.0

  • The list of domains in the Security Advisor can now be filtered.
  • The subscription screen now has a Security Advisor button, which opens Security Advisor with a filtered list of domains for the corresponding subscription.
  • The Home screen now has a Security Advisor button, which opens Security Advisor with a list of all available domains.

DataGrid → Opsani

  • The DataGrid extension was renamed to Opsani, because the product name has changed.

Virtuozzo ReadyKernel

  • The ReadyKernel extension will not be suggested to install, because Virtuozzo has announced that it stops supporting ReadyKernel for RedHat Enterprise Linux, CentOS and Ubuntu.

Ruby 1.3.3

  • The extension is now available for Debian 9.
  • The extension’s description on the catalog was revised and updated.

25 September 2017

Plesk Onyx 17.5.3 Update 23

  • CentOS 7.4 and Red Hat Enterprise Linux 7.4 are now supported.
  • Under certain circumstances, subscription backups could not be restored on Web Admin Edition. (PPPM-6865)

Linux

  • If the mailbox size was set to unlimited, running plesk repair mail for a domain resulted in overwriting size settings for particular mailboxes under that domain. (PPPM-6140)
  • A warning message about changing hosting type to Forwarding was incorrectly localized, which resulted in variable name appearing in the message text. (PPPM-7050)
  • Sending an email to multiple recipients via Postfix server with SPF enabled resulted in multiple “Received-SPF…” lines instead of one line. (PPPM-3456)
  • Under certain circumstances, Postfix failed to resolve short system email aliases, such as “root” or “postmaster”, which resulted in emails being rejected with message “Unable to get sender domain by sender mailname”. (PPPM-6939, PPP-27696)
  • Under certain circumstances, DMARC service encountered segmentation fault errors. (PPPM-6847)

20 September 2017

Extension Updates

Plesk Migrator 2.11.4

  • Plesk Migrator now supports importing websites with Joomla, Drupal, and Prestashop installed (with certain limitations, to learn more, read Migrating Applications).
  • Users can now view the migration log in real time and search the log for key phrases in the Plesk Migrator interface.
  • The reliability of migrations from servers with non-English locale has been improved.
  • Re-syncing a subscription that was reassigned to a different owner during migration flooded the migration log with PHP notices, and could corrupt the Plesk Migrator interface if the display_errors PHP option was enabled. (PMT-3887)
  • Migration from Plesk failed if one or more customer passwords on the source server decrypted to ‘none’. (PMT-3876)
  • When migrating a subscription with Magento installed, the Magento configuration file was not updated if the Magento database was renamed during migration. (PMT-3513)
  • When migrating a subscription with Prestashop, the Prestashop configuration file was not updated if the Prestashop database was renamed during migration. (PMT-3520)
  • When importing an application, the contents of all application files were lost if the specified domain name belonged to a domain already hosted on the target server. (PMT-3967)
  • Migration from Plesk failed if MariaDB 10.0.32 or later was installed on the source server. (PMT-3916)

Linux

  • When migrating from Ubuntu or Debian to CentOS or Red Hat Enterprise Linux (or vice versa), subscriptions with files owned by the web server that contained non-UTF-8 characters could be assigned to incorrect owners. (PMT-3860)
  • Migration could not be started if one or more secret keys in the Plesk database could not be decrypted correctly. (PMT-3298)
  • Plesk Migrator could not set the correct permissions for statistics and logs directories. (PMT-3934)

Windows

  • When migrating from Helm via the command line, the shallow-dump.xml file was created anew during each migration stage, which considerably prolonged the migration. (PMT-3921)
  • Migration from Helm failed if one or more packages had enabled features whose parent plan was deleted. (PMT-3912)
  • The post-migration report did not contain information about missing DNS records for domains whose names contained IDN characters. (PMT-3906)
  • Migration from Helm failed if one or more identical IP addresses were registered as both shared and dedicated on the source server. (PMT-3878)
  • Under specific circumstances, copying of mail content for individual mailboxes could fail. (PMT-3868)
  • Copying of mail content could fail when migrating MailEnable accounts with a large number of mails. (PMT-3866)
  • On servers with the Chinese locale, under specific circumstances, syncing Microsoft SQL Server databases could result in an error. (PMT-3832)
  • Migration from a server with Japanese locale could fail with a misleading error message when copying website content. (PMT-3705)
  • When importing an application to Plesk for Windows, the import could fail if the application had an exceedingly large number of files. (PMT-3975)

18 September 2017

Plesk Onyx 17.5.3 Update 22

  • Plesk Server Health Monitor received a series of improvements:
    • CPU total usage statistic now includes the number of CPU cores and maximum available usage.
    • Notification thresholds for CPU usage were corrected.
  • The extensions are now updated daily if automatic update is enabled on the server.
  • Security improvements.

Plesk Onyx 17.0.17 Update 34

  • Security improvements.

5 September 2017

Plesk Onyx 17.8 Preview 5

  • Contextual promos for Plesk extension are now shown in the Plesk interface.
  • Plesk users now can store their backups remotely in Amazon S3 buckets.
  • The “Extensions” > “My Extensions” screen in the Plesk UI has been redesigned.
  • Improved the first time setup experience for Plesk servers on Google Cloud.
  • Plesk users now can set the administrator password in the Cloud Launcher when creating a Plesk server on Google Cloud.
  • Made it easier for Plesk administrators to access their installed extensions.
  • Plesk now checks for extension updates every day instead of every week.
  • The Extensions Catalog search function has been improved.
  • When creating a Plesk server on Amazon Web Services, the login link is now listed in the installation log available in the AWS Management Console.
  • After upgrading to Plesk Onyx 17.8, the window offering to rate Plesk was shown every time a new Plesk page was opened. (PPP-31268)
  • Logging in to Plesk with no license installed resulted in an error. (PPP-31409)
  • Changing the subscription limits on a Plesk Multi Server master node failed to update the subscription limits on service nodes. (PPP-31221)
  • Users with the “Administrator” or the “WebMaster” user role could create new webspaces even if their access was limited to a single subscription. (PPP-30024)
  • Restricting administrative access in Plesk resulted in customers and resellers being unable to log in to Plesk via the Plesk Mobile application. (PPP-30222)
  • Trying to access phpMyAdmin in Plesk resulted in an error if the user’s session had timed out. (PPP-30845)
  • Under specific circumstances, the File Manager could be used to perform certain operations with files outside of the user’s webspace. (PPP-31240)
  • Backups could not be restored on Plesk Web Admin edition servers. (PPP-31168)

Linux

  • Plesk firewall is now managed by firewalld to ensure that all ports necessary for Plesk to operate are open.
  • Trying to browse files with extensions other that .php resulted in a “403 Forbidden” error if the “Proxy mode” option was disabled and both the “Restrict the ability to follow symbolic links” and the “Serve static files directly by nginx” options were enabled in “Apache & nginx settings”. (PPP-27118)
  • SPF handler could not add email headers for authorized SMTP sessions, which resulted DMARC verification failures. (PPP-31016)
  • During Plesk installation, the “TLSv1” protocol was specified in the ‘/etc/courier-imap/imapd-ssl’ file instead of “TLSv1+”. (PPP-29831)
  • Running the ‘plesk bin init_conf –init’ CLI command reset the Plesk administrator password. (PPP-31393)
  • Running the ‘plesk bin cloning -u prepare-public-image true’ CLI command did not reset the MySQL “admin” user’s password. (PPP-30057)
  • The disk space usage for mail accounts shown on the “Email Addresses” tab in Plesk was incorrect. (PPP-30528)
  • Trying to log in to Roundcube with an incorrect password resulted in an HTTP response code 500. (PPP-29087)
  • On Debian 8 servers, IPv6 addresses added via Plesk were not working correctly after server reboot. (PPP-29295)
  • On Debian 8 servers, IPv6 addresses added via Plesk were not added to the ‘/etc/network/interfaces’ file. (PPP-29298)
  • Backups made in Plesk did not include dumps of MySQL databases if Perl version 5.26 was installed on the server. (PPP-31259)

Windows

  • Changes made to a website’s PHP settings after changing the website’s document root directory to a child directory of /httpdocs failed to take effect. (PPP-30889)
  • Changing a domain’s ASP.NET settings in Plesk resulted in the “providerName” parameter being removed from the domain’s web.config file. (PPP-30496)
  • Creating server backups in Plesk resulted in an error if one or more domains on the server were secured with an SSL/TLS certificate from Let’s Encrypt. (PPP-29193)
  • During upgrade to Plesk Onyx 17.8, if an external drive was mounted to the the %plesk_vhosts% directory, the drive was unmounted and an empty directory was created instead. (PPP-30801)

Plesk Onyx 17.5.3 Update 21

  • Clicking the “Backup Manager” breadcrumb on the “Websites&Domains” > “Backup Manager” > “Back Up” screen took the user to the “My Account” > “Backup Manager” screen if Plesk was behind an UI proxy. (PPPM-6577)

Linux

  • Updating the administrator’s default SSL/TLS certificate via CLI corrupted the web server configuration. (PPPM-6136)
  • Users could not restore from full backups stored in the FTP repository if the ‘/usr/local/psa/PMM/tmp’ directory was missing. (PPPM-6591)
  • The ‘ifmng’ CLI utility was unable to correctly parse IPv6 addresses without a netmask. (PPPM-6373)

Windows

  • SmarterMail 16 is now supported.
  • Certain operations with virtual hosts could not be performed in Plesk if an external drive was mounted to the the %plesk_vhosts% directory. (PPPM-6615)

Third-Party Component Updates

  • PHP 7.1 was updated to version 7.1.9.
  • PHP 7.0 was updated to version 7.0.23.

Plesk Onyx 17.0.17 Update 33

Third-Party Component Updates

  • PHP 7.1 was updated to version 7.1.9.
  • PHP 7.0 was updated to version 7.0.23.

31 August 2017

Extension Updates

Let’s Encrypt 2.3.0

  • When creating a subscription, add-on domain, or subdomain, it can be immediately secured with a Let’s Encrypt certificate. The corresponding checkbox on the subscription or domain creation page is not selected by default. To make it selected by default, add the following setting in the panel.ini:

    [ext-letsencrypt]
    secure-new-domain = true
    
  • The Let’s Encrypt extension now explains common errors that can happen when issuing a certificate and gives instructions on resolving them.
  • When using Let’s Encrypt CLI for issuing a certificate, the alternative domain names, passed as command parameters, were not included in the cerfificate. (EXTLETSENC-104)
  • An error message was shown when the extension could not clean up certain temporary files after issuing a certificate. Now a warning message is shown instead. (EXTLETSENC-106)
  • Under certain circumstances, on Plesk 12.5 servers, issuing a certificate on a subscription with incorrect DNS configuration resulted in a ‘PHP fatal error’. (EXTLETSENC-256)
  • Under certain circumstances, if the web server restarted during the process of issuing a certificate, it could not access the certificate file, which resulted in failure to restart. (EXTLETSENC-213)
Linux
  • Under certain circumstances, on Plesk 12.5 servers, a certificate renewal task failed with ‘DEBUGGER DETECTED’ message. (EXTLETSENC-255)
Windows
  • The symbolic links to issued certificates were created with Unix-style path separator, which resulted in them being unreadable. (EXTLETSENC-235)

28 August 2017

Plesk Onyx 17.5.3 Update 20

  • When regenerating webserver configuration, Plesk now detects domains mapped to unavailable IP addresses and proposes to fix each domain by either remapping it to an available IP or excluding it from the conifiguration. This ensures that the regenerated configuration is valid and the webserver succeeds to start.

  • Removing all licenses from a Plesk instance resulted in logging in to the Plesk Panel via browser failing with a “PHP fatal error”. (PPP-30145)

24 August 2017

Extension Updates

WordPress Toolkit 2.3.0

  • A restoration point can now be created for a WordPress instance before running operations that have a risk of damaging the instance, such as upgrading it or syncing data. After such operation the instance can be rolled back to the restoration point.
  • A new security check ‘Disable pingbacks’ was added. It prevents attackers from exploiting the WordPress Pingback API to send spam and launch DDoS attacks.

  • A link to the list of WordPress instances was added to the left navigation pane in Power User view and Customer panel.
  • A confirmation dialog is now shown before updating multiple WordPress instances.
  • A confirmation dialog is now shown before installing a WordPress instance to a database which is already used by another instance.
  • A confirmation dialog is now shown if WordPress installation can overwrite certain files, created by some other CMS.
  • Now the WordPress Toolkit does not allow synchronizing databases between WordPress instances that share a single database.
  • The message about synchronizing an instance with an older WordPress version to an instance with a newer version was corrected. (EXTWPTOOLK-736)
  • The string placeholder was used instead of the domain name on the clone page when German language was used in the user interface. (EXTWPTOOLK-771)
  • WordPress Toolkit could not work with instances where the is_admin function was used in wp-config.php. (EXTWPTOOLK-722)
  • Changing the Plesk encryption key after a failed attempt to clone a WordPress instance could result in all further attempts failing. (EXTWPTOOLK-657)
  • When cloning a WordPress instance, an error on the database migration step, could result in file transfer step marked as failed. (EXTWPTOOLK-701)
  • When cloning an instance, the WordPress Toolkit searched for possible locations of wp-config.php in a wrong order, which could result in a failure to clone the instance. (EXTWPTOOLK-704)
  • A customer having no access to the WordPress toolkit could indeed have an ‘Install Wordpress’ button, which actually did not perform any action. (EXTWPTOOLK-721)
  • The “Administrator’s username” security check was displayed in a wrong section of the Secure WordPress dialog. (EXTWPTOOLK-695)
Windows
  • Cloning or synchronizing WordPress instances could fail due to unquoted escape sequences in file paths. (EXTWPTOOLK-749)

21 August 2017

Plesk Onyx 17.5.3 Update 19

  • The Fail2ban white list is now automatically updated with Plesk server IPs when they are created, updated or removed.

    Note: To add IPs created before this Plesk update to the Fail2ban white list, open the IP Addresses page in Tools & Settings and click the ‘Reread IP’ button.

  • A DNS SRV record with empty target can now be added.
  • Under certain circumstances, the ‘Share your opinion’ form was shown on each page and could not be postponed. (PPPM-6891)
  • An FTP bakup storage having incorrect or missing settings was not shown on the backup screen, and a backup attempt resulted in an error. (PPPM-6021)

Plesk Onyx 17.0.17 Update 32

  • An FTP bakup storage having incorrect or missing settings was not shown on the backup screen, and a backup attempt resulted in an error. (PPPM-6870)

Linux

  • The libdbd-mysql-perl package could be removed from the Plesk server, which disrupted the functioning of subscription backups. (PPPM-6798)
  • Under specific circumstances, uninstalling Postfix mailserver resulted in removing basic Plesk packages. (PPPM-6091)

14 August 2017

Plesk Onyx 17.5.3 Update 18

  • The domain alias for a subscription, assigned to an external IP, was displayed as assigned to an internal IP. (PPPM-6322)

Linux

  • The libdbd-mysql-perl package could be removed from the Plesk server, which disrupted the functioning of subscription backups. (PPPM-6764)
  • SPF handler could not add email headers for an authorized SMTP session, which resulted in failure to pass DMARC verification. (PPPM-6824)
  • Under specific circumstances, uninstalling Postfix mailserver resulted in removing basic Plesk packages. (PPPM-6091)
  • Scheduled tasks were added according to the default time instead of server time. (PPPM-6381)
  • Mail from specific senders, including amazon.de and husqvarnagroup.com, could not pass DMARC verification. (PPPM-6847)

7 August 2017

Plesk Onyx 17.8 Preview 4

  • Plesk Onyx 17.5 images are bundled with Google.
  • Plesk extensions promos can now be set and shown as a contextual advertisement on certain Plesk pages.
  • CAA DNS records are now supported in Plesk.
  • Plesk backups can now be stored in cloud storages (Amazon S3) via Plesk GUI and CLI.
  • After having purchased an extension licence in Plesk Online Store, user is redirected back to the Plesk server and Plesk automatically installs the new extension licence and upgrades existing extensions’ licences if necessary.
  • Extensions upselling is now available.
  • The web server failed to start if an IP address registered in Plesk was absent in the system.
  • Users could not change a domain’s hosting type to “forwarding’ via XML API. (PPP-30466)
  • Plesk returned empty responses to XML API requests if the “Google Authenticator” extension was installed on the Plesk server. (PPP-30527)
  • The inncorrect DNS record was added for the website preview if the server was behind NAT. (PPP-29408)
  • It was impossible to add the 127.0.0.0/8 subnet mask to the mail server whitelist via CLI. (PPP-29607)
  • User with the denied permission “Create and manage sites” could not add a website but still had access to creating domains. (PPP-29718)
  • User with the access only to a particular webspace was able to see the list of all other webspaces. (PPP-30023)

Linux

  • LimitNOFILE can now be managed for PHP-FPM.
  • PHP opcache_get_status is now disabled by default.
  • Rkhunter was updated to version 1.4.4.
  • Under certain curcumstances, websites could not be published in Web Presence Builder. (PPPM-6776)
  • Users with encrypted mailbox passwords could not log in to Roundcube. (PPP-30208)
  • The maximum number of connections to the Plesk mail server configured in “Tools & Settings” > “Mail Server Settings” did not affect the maximum number of IMAP connections. (PPP-30395)
  • When configuring the settings of PHP handlers in “Tools & Settings” > “PHP Settings”, PHP-FPM handlers were not listed in the help message. (PPP-30640)
  • Users could not send mail via Horde after the plesk sbin pci_compliance_resolver --enable utility was run on the Plesk server. (PPP-30816)
  • Web Presence Builder websites could not be published if the information about installed packages was missing from the Plesk database. (PPP-30824)
  • Trying to back up a subscription resulted in a confusing error message if the libdbd-mysql-perl package was missing from the Plesk server. (PPP-30850)
  • After the plesk sbin pci_compliance_resolver --enable utility was run in Plesk 12.0 and Plesk 12.0 was upgraded to Plesk Onyx, sw-cp-server failed to start due to duplicate ssl_cipher records. (PPP-28486)
  • The mchk utility resets back to open relay settings that had been closed. (PPP-28966)

Windows

  • IIS Dynamic Content Compression is now supported in Plesk.
  • SNI support is now activated by default.
  • POCO Libraries were updated to version 1.7.8p3.
  • Tomcat was updated to version 7.0.79.
  • AWStats was updated to version 7.6.
  • Securing the mail server with an SSL/TLS certificate in Plesk failed to add the certificate in MailEnable if MailEnable version 9.60 or later was installed on the Plesk server. (PPP-30517)
  • Users could not perform certain operation with subscriptions (such as renaming) if Plesk was installed on a mounted .vhd file. (PPP-30525)
  • When configuring backup settings for remote Linux-based Microsoft SQL Server 2017 database servers, users could not set a Linux-style path for the temporary files directory. (PPP-31010)
  • Some Plesk services installation paths contained spaces and were unquoted. (PPP-28340)
  • The contact name was not displayed in scheduled tasks notifications. (PPP-29261)
  • Email notifications in scheduled tasks malfunctioned due to equal sender and receiver addresses in the header. (PPP-29550)
  • Copying of databases via Plesk failed if the database size exceeded 3.5 GB or the database contained big blobs. (PPP-29570)
  • Internationalized domain names could not be created directly. (PPP-29882)
  • It was impossible to create a domain alias for the domain using the Punycode encoding. (PPP-29923)

Third-Party Component Updates

Linux
  • Roundcube was updated to version 1.2.5.
  • PHP 7.0 was updated to version 7.0.22.
  • PHP 7.1 was updated to version 7.1.8.
Windows
  • PHP 7.0 was updated to version 7.0.22.

Plesk Onyx 17.5.3 Update 17

  • Download URLs for installing Atomicorp packages have been updated.
  • Security improvements.
  • The DNS settings page for a DNS zone with thousands of records took 5-10 minutes to load. (PPPM-6751)
  • After closing the ‘Change View’ menu, the link for managing views did not appear in the ‘Tools & Settings’. (PPPM-6749)

Linux

  • When renaming a domain alias, the DNS zone for the previous alias name was not removed. (PPPM-6748)
  • The server_pref utility could not set SSL protocols and cyphers for FTP service. (PPPM-6572)

Third-Party Component Updates

  • PHP 7.0 was updated to version 7.0.22.
  • PHP 7.1 was updated to version 7.1.8.
Windows
  • MySQL Server 5.5 was updated to version 5.5.55.
  • MySQL Server 5.6 was updated to version 5.6.36.

Plesk Onyx 17.0.17 Update 31

  • Download URLs for installing Atomicorp packages have been updated.
  • Security improvements.

Third-Party Component Updates

  • PHP 7.0 was updated to version 7.0.22.
  • PHP 7.1 was updated to version 7.1.8.

3 August 2017

Plesk Manager & Plesk Monitor

  • Plesk Manager and Plesk Monitor, both 32-bit apps, have been discontinued. To continue managing your servers, websites and customers on the go, install the brand new 64-bit Plesk Mobile App. Plesk Mobile is available now at the Apple App Store and Google Play.

31 July 2017

Plesk Onyx 17.5.3 Update 16

  • Security enhancements.
  • Database dumps were not downloaded automatically even if the ‘Automatically download dump after creation’ checkbox was selected when exporting the dump. (PPPM-6341)

Linux

  • Web Presence Builder websites could not be published if the information about installed packages was missing from the Plesk database. (PPPM-6776)
  • Updating the default SSL/TLS certificate in the Plesk administrator’s repository via the CLI resulted in an error. (PPPM-6775)

Windows

  • Trying to customize a subscription or to open the ‘Websites & Domains’ > ‘PHP Settings’ page resulted in an error if no PHP handlers were configured in Plesk. (PPPM-6127)

Plesk Onyx 17.0.17 Update 30

  • Security enhancements.
  • Under specific circumstances, changing mail server settings resulted in an error if the Plesk interface language was set to Italian. (PPPM-5761)

Linux

  • Web Presence Builder websites could not be published if the information about installed packages was missing from the Plesk database. (PPPM-6777)
  • Updating the default SSL/TLS certificate in the Plesk administrator’s repository via the CLI resulted in an error. (PPPM-6137)

24 July 2017

Plesk Onyx 17.5.3 Update 15

Linux

  • Confirming a finished update of Plesk components resulted in Plesk Autoinstaller becoming unresponsive. (PPPM-6723)

Third-Party Component Updates

  • RkHunter was updated to version 1.4.4.

20 July 2017

Extension Updates

Plesk Migrator 2.10.10

  • A running site importing can now be stopped.
  • When migrating from Plesk versions 11.0 to 12.5, if a certain password can not be decrypted, migration does not stop, but a new random password is generated instead.
  • When importing directories, the path on the target server is shown on the import screen.
  • Migrating to Plesk Multi Server configured to use a non-standard SSH port resulted in failing to copy content with an ‘Unable to connect’ error. (PMT-3816)
  • After consecutively running Switch DNS and Revert DNS on a migrated subscription, the subscription’s checkbox on the advanced mode screen was still selected. (PMT-3835)
  • If the target server’s Plesk license did not include reseller accounts, migrating accounts with reseller privileges resulted in errors. Now Plesk Migrator handles such accounts in the following way:
    • all customer accounts, belonging to the reseller, become regular customer accounts;
    • all subscriptions, belonging to the reseller, are assigned to the administrator account;
    • the reseller account itself is not migrated. (PMT-3795)
  • The websites’ files with names, starting with a dot, were not imported. (PMT-3817)
  • A customized subscription expiration date was not migrated from Plesk 17.0 or later. (PMT-3843)
  • Report about failure to transfer a file by FTP during site importing contained unnecessary information from program logs. Now only a short report is shown with a list of such files. (PMT-3713)
  • When migrating from Plesk 17.0 or later, encrypted passwords of additional FTP accounts were replaced with new random passwords. Now such passwords are migrated without changing. (PMT-3689)
  • Java applications could not be migrated between Plesk servers. (PMT-3779)
  • The results of post-migration checks were always marked as ‘Errors’, even when all checks succeeded. (PMT-3820)
  • Plesk Migrator failed to find the document root of an IDN subscription, which resulted in website import failing with an error. (PMT-3809)
Linux
  • When migrating to Plesk Multi Server, skipping pre-migration checks for a subscription resulted in failure to migrate such subscription. (PMT-3822)
  • When migrating from a server with Horde webmail to a server with different webmail, Plesk Migrator attempted to restore the mail address book, which resulted in an error. Now Plesk Migrator detects such situations and does not try to restore the address book. (PMT-3806)
  • When migrating from DirectAdmin, some subscription limits could be migrated incorrectly. (PMT-3794)
  • If the source server was configured to produce any output in a non-interactive shell (such as an SSH welcome message), migration failed with an error. Now Plesk Migrator detects such configurations and shows a comprehensive message, explaining how to fix the issue. (PMT-3823)
  • If an attempt to perform DNS Switch with UI failed due to some problem, the following attempts resulted in errors even if the problem was resolved. (PMT-3845)
  • When migrating websites from a Confixx server, the SSL certificates were transferred to the subscription’s certificate pool and were not available for the subscription’s domains. As a result, after any webserver reconfigration the websites became unable to use their certificates and had to use the default Plesk certificate. (PMT-3818)
Windows
  • Sample configurations for migrating from and to Plesk servers with remote SmarterMail were added.
  • If the source system had services with names or descriptions, containing non-ASCII characters, the whole server migration failed with message ‘Failed to remove missing Python and Perl scripting options from backup dump’. (PMT-3704)
  • Under certain circumstances, dumping MySQL databases when migrating IDN subscriptions failed with ‘Unicode Encode Error’. (PMT-3825)
  • Restoring MS SQL databases on IDN subscriptions failed. (PMT-3840)
  • Synchronizing or repeated migration of subscription’s business objects (like databases, email accounts or domains) to a server with remote SmarterMail failed. (PMT-3819)
  • Subscriptions migration from Helm 3 servers failed, if the subscriptions were using web forwarding and had mailboxes and/or databases. (PMT-3859)
  • Migration from Windows 2003 x64 servers with non-English locale failed while copying files with message ‘Failed to copy web files for subscription’. (PMT-3027)
  • Migration GUI missed a link for downloading the RPC Agent installation package. (PMT-3829)
  • If a subscription on Helm 3 server had a mail service enabled, but no mail IP available, migration of the subscription failed. (PMT-3856)
  • When migrating from Helm 3, subscriptions of customers with login name longer than 15 characters were skipped without notification. (PMT-3849)

Let’s Encrypt 2.2.2

  • To prevent Let’s Encrypt extension from automatically securing Plesk Panel on installation, add the following setting in panel.ini before installing or updating the extension:

    [ext-letsencrypt]
    disable-panel-auto-securing = true
    
  • Setting the verify option to true in panel.ini config section for Let’s Encrypt extension resulted in inability to connect to the Let’s Encrypt CA servers. (EXTLETSENC-223)
  • The command line interface did not allow to issue certificates for domains with www prefix. (EXTLETSENC-226)
  • In certain cases, when installing or upgrading the extension, a valid certificate used for securing Plesk Panel was detected as insecure and replaced with Let’s Encrypt certificate. Now the extension automatically replaces only self-signed certificates. (EXTLETSENC-222)

WordPress Toolkit 2.2.1

  • Some parts of the security check screen didn’t show proper text in the Special Edition of the WordPress Toolkit if non-English locale was used. (EXTWPTOOLK-699)
  • The buttons on the maintenance mode setup screen had no labels and performed no actions if non-English locale was used. (EXTWPTOOLK-700)

19 July 2017

Extension Updates

WordPress Toolkit 2.2.0

  • The Special Edition of WordPress Toolkit is now available for all users of Plesk Web Admin edition. This version offers the basic features of WordPress Toolkit for free.
  • Improved handling and reporting of WordPress upgrade errors.
  • The built-in help for command-line utility has been improved and updated.
  • The dialog for removing a broken instance had no text. (EXTWPTOOLK-671)
  • After detaching an instance, WordPress Toolkit did not properly set the instance’s autoupdate settings. (EXTWPTOOLK-653)
  • Spaces were missing in the text on the cloning page for some languages. (EXTWPTOOLK-660)
  • When user performed a custom WordPress installation and specified ‘admin’ as a WordPress administrator username, this username was replaced on the Securing Instance step of the installation. Now the ‘admin’ username is not replaced if explicitly specified, and the instance is marked as insecure instead. (EXTWPTOOLK-507)
  • During the upgrade, the default WordPress maintenance page was used instead of the maintenance page configured in WordPress Toolkit. (EXTWPTOOLK-644)
  • Manually removing a WordPress database without using Plesk could result in inability to install or clone WordPress instances. (EXTWPTOOLK-471)
  • WordPress Toolkit could not work with an instance that had any code requiring ‘wp-settings.php’ in ‘wp-config.php’. Now WordPress Toolkit ignores such code when working with the instance and provides improved error reporting for ‘wp-config.php’ issues. (EXTWPTOOLK-638)
  • If a theme or a plugin failed to update, no error message was shown. Now WordPress Toolkit shows a comprehensive error message in such case. (EXTWPTOOLK-489)
  • Some plugins dependent on other plugins (such as WooCommerce Germanized plugin) could not be activated via the WordPress Toolkit. (EXTWPTOOLK-621)
  • Repeating previously failed clone procedure for a WordPress instance failed again if the database user was linked to another database due to database user with the same name already existing. (EXTWPTOOLK-658)
  • Removing the database of a cloned website resulted in inability to clone it again to the same domain and with the same database name. (EXTWPTOOLK-669)
  • If user was cloning a subdomain-based WordPress multisite when no valid domains were available, WordPress Toolkit displayed an ugly-looking error without even opening the Clone screen. To avoid hurting the aesthetic sensibilites of users, the error is now displayed properly on the Clone screen and is looking quite fabulous. (EXTWPTOOLK-639)
  • If cloning of a WordPress installation was blocked by database import or export errors, the WordPress Toolkit reported that the installation was not configured, but did not explain the actual problem. Now it correctly detects and reports the problem that caused the error. (EXTWPTOOLK-636)
  • Themes with descriptions containing non-ASCII characters were breaking the functioning of theme search in WordPress Toolkit. (EXTWPTOOLK-579)
  • When synchronizing data between two WordPress instances, the maintenance mode page displayed on the target instance tried to use the resources located on the source instance. (EXTWPTOOLK-631)
  • Trying to enable maintenance mode on a WordPress instance of version earlier than 4.3 resulted in an error. (EXTWPTOOLK-686)

17 July 2017

Plesk Onyx 17.5.3 Update 14

  • Health Monitor is now available in Power User view as well as in Service Provider view. (PPPM-278, PPPM-2857)

  • Trying to configure FTP storage resulted in an error if the FTP server did not allow to resume uploads and downloads, or to upload the .ftpaccess file. (PPPM-6502)

  • Trying to configure FTP storage resulted in an error if the path to the directory for storing backup files contained one or more whitespace characters. (PPPM-6236)

Linux

  • Restoring a subscription from backup using the “Only configuration of the selected objects” option failed to restore Apache and nginx settings for the subscription. (PPPM-6530)

Third-Party Component Updates

Linux

  • Roundcube was updated to version 1.2.5.

12 July 2017

Extension Updates

Let’s Encrypt 2.2.1

  • The extension incorrectly handled errors when communicating with Plesk Panel, which disrupted the functioning of extension itself. Now it correctly handles such errors, shows an explaining message and continues working when possible. (EXTLETSENC-221)

11 July 2017

Extension Updates

Let’s Encrypt 2.2.0

  • This update contains changes, affecting both Let’s Encrypt and Security Advisor extensions. Please also update Security Advisor to version 1.4.1 or later.
  • Plesk Panel can now be secured with a Let’s Encrypt certificate. The corresponding setting is now available at the SSL/TLS Certificates page.
  • Upon installing or upgrading (either at Plesk installation or separately), the extension checks that a trusted certificate is used for Plesk Panel. If the extension detects a non-trusted (for example, self-signed) certificate, it automatically attempts to replace it with a trusted certificate from Let’s Encrypt CA. Thus, in most cases, a fresh installation of Plesk Panel is secured since the first login.
  • The extension now detects and renews Let’s Encrypt certificates, obtained with Security Advisor for securing Plesk Panel.
  • Renewing the Let’s Encrypt certificates is now done at a random time within the day when the certificate is due to renewal. This helps evenly spreading the load on Let’s Encrypt Certificate Authority and enables issuing more free certificates.
  • Cases, when IPv6 was disabled for a subscription but an external DNS resolved the domain name to an IPv6 address, were not detected. This resulted in failing attempts to create a certificate. Now Plesk correctly detects such cases and shows a message, explaining the problem. (EXTLETSENC-182)
  • The extension was not able to renew certificates, issued before updating the extension to version 2.0 for domain names with uppercase letters. (EXTLETSENC-211)
  • The subscription’s certificate README file was missing a link to the Certbot documentation. (EXTLETSENC-166)
  • On Windows servers, renewing certificate for webmail failed. (EXTLETSENC-164)
  • A failed certificate installation led to exhausting the Let’s Encrypt rate limits for a domain, which resulted in inability to renew the certificate. (EXTLETSENC-198)

Security Advisor 1.4.1

  • This update contains changes, affecting both Let’s Encrypt and Security Advisor extensions. Please also update Let’s Encrypt to version 2.2.0 or later.
  • Now Security Advisor delegates obtaining free certificates for securing Plesk Panel from Let’s Encrypt CA to the Plesk Let’s Encrypt extension, which excels in this task.

10 July 2017

Plesk Onyx 17.5.3 Update 13

Linux

  • Adding DNS TXT records longer than 255 characters resulted in inability to start the DNS service. (PPPM-3170)
  • On Ubuntu 14.04 x64 servers installed in a Virtuozzo container, the PHP FPM processes were not restarted after minor PHP updates, which could result in unexpected behaviour of PHP applications on the server. (PPPM-6296)
  • On CentOS 7 x64 servers, the Dovecot component, when already updated to the latest version, was incorrectly marked with an ‘updates available’ label. (PPPM-6605)

Third-Party Component Updates

  • PHP 7.0 was updated to version 7.0.21.
  • PHP 5.6 was updated to version 5.6.31.
  • PHP 7.1 was updated to version 7.1.7.

Plesk Onyx 17.0.17 Update 29

Linux

  • On Ubuntu 14.04 and Debian 7 servers installed in a Virtuozzo container, the PHP FPM processes were not restarted after minor PHP updates, which could result in unexpected behaviour of PHP applications on the server. (PPPM-6296)

Third-Party Component Updates

  • PHP 7.0 was updated to version 7.0.21.
  • PHP 5.6 was updated to version 5.6.31.
  • PHP 7.1 was updated to version 7.1.7.

3 July 2017

Plesk Onyx 17.5.3 Update 12

  • Plesk Onyx 17.5.3 Update 12 is a stable (late adopter) release.
  • Starting with this update, Perigon Control Suite is no longer supported.
  • The -forwarding true parameter of the plesk bin mail --create command was ignored, which resulted in creating a mailbox with disabled forwarding. (PPPM-6038)

Linux

  • If the PHP handler was changed to “FPM application served by nginx”, the setting was not displayed on the PHP Settings page. (PPPM-6171, PPPM-6532)
  • If nginx proxy mode was turned off for a subscription, the Apache-based options for PHP handler were indeed available on the PHP Settings and Hosting Setings pages. (PPPM-6550)
  • Trying to log in to Roundcube with an incorrect password resulted in an HTTP response code 500. (PPPM-6104)

Windows

  • Backup to an FTP storage failed if the field “Directory for backup files storage” was empty. (PPPM-6466)

29 June 2017

Extension Updates

WordPress Toolkit 2.1.2

  • Repeatedly scanning a subscription for WordPress instances resulted in autoupdate turned off for all found instances. (EXTWPTOOLK-652)

26 June 2017

Plesk Onyx 17.5.3 Update 11

  • Improved stability for Plesk license key renew operation.
  • Creating a subscription with specific web server settings with an API-RPC request resulted in error ‘Unable to update hosting preferences. The user example.tld already exists. Incorrect fields: “login”’. (PPPM-6547)

19 June 2017

Plesk Onyx 17.5.3 Update 10

  • CLI for managing ModSecurity was significantly enhanced and now supports most features, available in Plesk Panel, including:
    • Applying predefined firewall configurations,
    • Uploading custom rulesets,
    • Setting the active ruleset and update frequency,
    • Setting the web application firewall mode.
  • Additional HTTP headers can now be configured in Apache and nginx settings.
  • Plesk 17.5.3 locales were updated.
  • Pressing ‘Download Backup’ several times in a row caused Plesk to consume extra disk space. (PPPM-4941)

15 June 2017

Extension Updates

WordPress Toolkit 2.1.1

  • If the subscription was configured to use PHP 5.3 or earlier, WordPress Toolkit erroneously detected subscription’s WordPress instances as broken. (EXTWPTOOLK-632)

14 June 2017

Extension Updates

WordPress Toolkit 2.1.0

  • Users can now protect their WordPress websites with a password. Anyone browsing a password-protected website receives the “401 Unauthorized” response unless they provide the correct login and password.
  • Users can now manually put their WordPress websites into maintenance mode. Users are also able to edit the placeholder page that is displayed to those visiting a WordPress website under maintenance.
  • The “WordPress register” event can now be used with Plesk event handlers. The event triggers every time a WordPress website is registered in the WordPress Toolkit after performed scan for WordPress installations or after installation via the Application catalog.
  • The WordPress installation procedure was simplified and streamlined.
  • The procedure for the installation of WordPress plugins and themes on newly created WordPress websites was simplified and streamlined.
  • Under certain circumstances, the administrator’s webmail address was displayed incorrectly in WordPress Toolkit. (EXTWPTOOLK-490)
  • Importing a WordPress website resulted in an error if no hosting was configured for the parent domain. (EXTWPTOOLK-558)
  • In case of available major updates, administrators of WordPress websites with minor automatic updates enabled received daily notifications about installed updates even though these updates were not actually installed. Meanwhile, notifications about available updates were not delivered. (EXTWPTOOLK-561)
  • Cloning WordPress websites failed to preserve the source website’s automatic update settings. (EXTWPTOOLK-600)

13 June 2017

Plesk Onyx 17.8 Preview 2

  • Plesk Onyx 17.5 solution images for WordPress Server and Business Server are bundled with Amazon and Azure.
  • The Extensions Catalog landing page has received Featured Categories and several other updates.
  • Plesk EULA and copyright information were updated.
  • Starting with Plesk Onyx 17.8 Preview 2, Perigon Control Suite is no longer supported.
  • Installing Plesk with the ‘Plesk Migrator’ component resulted in creating duplicate entries in /etc/apt/sources.list. (PPP-28879)

Linux

  • In Cgroups Manager a notification threshold for resource usage can now be configured without setting a hard limit.
  • Additional HTTP headers can now be configured in Apache and nginx settings.
  • PHP-FPM pool settings can be configured on a domain level via Plesk GUI.
  • CloudLinux 7.3 is now supported.
  • The PHP-FPM setting max_children can now be customized.

Windows

  • MailEnable Standard Edition is now automatically upgraded on Plesk upgrade.
  • ISC BIND is now running under a low-privileged user.

Third-Party Component Updates

  • PHP 7.0 was updated to version 7.0.20.
  • PHP 7.1 was updated to version 7.1.6.
Linux
  • Roundcube was updated to version 1.2.4.
Windows
  • MySQL-Admin was updated to version 5.7.
  • MailEnable was updated to version 9.74.

Plesk Onyx 17.5.3 Update 9

  • Please note that Plesk Panel service will restart after updating.
  • Restoring or migrating a multi-line catch-all bounce message failed. (PPPM-6417)
  • A multiline mail bounce message could not be set via CLI. (PPPM-6416)
  • Removing additional domains or subdomains from Power User view failed with a ‘Permission denied’ message. (PPPM-6142)
  • If the name of a customer’s subscription was the same as the server’s hostname, the customer could not save changes in the domain hosting settings. (PPPM-6420)
  • Log Browser failed to properly parse certain ModSecurity logs. (PPPM-5872)

Linux

  • If the PHP handler was changed to “FPM application served by nginx”, the setting was not displayed on the PHP Settings page. (PPPM-6171)
  • Opening Plesk Panel by URL with port 8443 and no protocol specified resulted in returning an HTTP response code 400 instead of redirecting to HTTPS. (PPPM-6366)

Third-Party Component Updates

  • PHP 7.1 was updated to 7.1.6.
  • PHP 7.0 was updated to 7.0.20.

Plesk Onyx 17.0.17 Update 28

  • Security improvements.
  • Adding an FTP storage in Backup Manager failed with message ‘Curl error: (35) SSL connect error’. (PPPM-6165)
  • Having extra data in DUMP_D directory resulted in calculating disc usage of dumps with ppm-ras running too slow. (PPPM-6361)
  • When opening a backup restoration page, ppm-ras --get-dump-list was called twice, which was logged in pmmcli.log. (PPPM-6358)

Third-Party Component Updates

  • PHP 7.1 was updated to 7.1.6.
  • PHP 7.0 was updated to 7.0.20.

7 June 2017

Extension Updates

Plesk Migrator 2.9.2

  • An option to migrate a reseller with all accounts and subscriptions has been implemented.
  • Now when a subscription, owner or subscription plan is already migrated, it can be hidden from the ‘List of subscriptions’ tab.
  • The DirectAdmin migration agent now checks the data consistency on the source side. It correctly performs migration even when there are errors in the configuration of some domains. The overall fault tolerance of the agent has been improved.
  • The ‘List of subscriptions’ tab was added to the migration screen. It replaces the ‘Add subscriptions’ tab in simple mode, or the ‘Subscriptions list’ tab in advanced mode.
  • When migrating sites from cPanel, the Plesk Migrator detected a single WordPress instance as two separate instances. (PMT-3672)
  • MySQL events were not transferred during migration. (PMT-3677)
  • In certain circumstances it was impossible to import a website, if its webspace had files with names, containing non-ASCII characters. (PMT-3703)
Linux
  • When migrating from cPanel, there is an option to choose whether to migrate subdomains and domain aliases as addon domains, thus preserving the related email accounts.
  • Now, if the target database has earlier version and does not support some features of the source database, a comprehensive message is shown at the end of migration. (PMT-3241)
  • MySQL databases could not be migrated if a database’s admin password did not match the password stored in the PSA database. (PMT-3778)
  • Migration of mail content from cPanel failed, if the home directory on source was different from /var/home/ (PMT-3212)
  • Several domain aliases, created by cPanel for internal purposes, were migrated as domain aliases in Plesk. Now Plesk Migrator recognizes and ignores such technical aliases. (PMT-3506)
  • Plesk Migrator did not set a password for the source server’s user that it creates for copying content. Some servers’ configurations forbid SSH authorization of such users, thus making copying unavailable. (PMT-3558)
  • Additional Apache and nginx directives of subscriptions were not transferred. (PMT-3072)

5 June 2017

Plesk Onyx 17.5.3 Update 8

  • Adding an FTP storage in Backup Manager failed with message ‘Curl error: (35) SSL connect error’. (PPPM-6165)
  • Having extra data in DUMP_D directory resulted in calculating disc usage of dumps with ppm-ras running too slow. (PPPM-6361)
  • When opening a backup restoration page, ppm-ras --get-dump-list was called twice, which was logged in pmmcli.log. (PPPM-6538)
  • Under certain circumstances, trying to change the PHP settings or version resulted in an error. (PPPM-6030)

Windows

  • Creating more than two domain aliases resulted in records being removed from the parent DNS zone. (PPPM-6148)

29 May 2017

Plesk Onyx 17.5.3 Update 7

  • Redirects from HTTP to HTTPS on domain aliases have been improved to make a single SEO-safe redirect with HTTP response code 301.
  • A detailed message explaining the changes and consequences is now shown when changing the hosting type. This message contains a complete list of folders that are going to be removed.
  • Security improvements.
  • Starting multiple backup processes within a minute of each other caused one of them to fail. (PPPM-5728, PPP-27889)

Linux

  • Under specific circumstances, a request for static files on a WordPress site returned the HTTP response code 404. (PPPM-6309)

Windows

  • Plesk now properly detects the platform when hosted on Google Cloud.
  • Enabling mail service for a domain via an XML API request resulted in webmail becoming unavailable for that domain. (PPPM-6263)

Plesk Onyx 17.0.17 Update 27

  • Security improvements.
  • Changing the PHP handler or version for a domain caused the same change for a subdomain. (PPPM-4617)

Linux

  • Under specific circumstances, a request for static files on a WordPress site returned the HTTP response code 404. (PPPM-6310)
  • On Ubuntu 16.04 servers, changing the PHP handler for a domain with multiple subdomains could result in an error if all of them were configured to use the “FPM application served by Apache” handler and the same version of PHP. (PPPM-5142)

Windows

  • Enabling mail service for a domain via an XML API request resulted in webmail becoming unavailable for that domain. (PPPM-5715)

Extension Updates

Virtuozzo ReadyKernel 1.1.0

  • Ubuntu 14.04 and Ubuntu 16.04 are now supported.

24 May 2017

Extension Updates

Plesk Migrator 2.8.7

  • When importing sites, databases, or directories, the actual status of each item is displayed. If import of an item failed or generated a warning, a detailed list of issues is available.

  • Removing an additional domain that was previously imported from another server resulted in an error in Plesk panel. (PMT-3701)

  • In case of a database name or database user name conflict during site import, if there were additional spaces between the names and values of corresponding variables in the wp-config.php file, the WordPress application did not work after import. (PMT-3673)

  • Passwords for accounts with names, containing Unicode characters outside of ASCII range, could not be decrypted after migration. (PMT-3667)

  • If the source FTP server did not support TLS, this negatively affected the performance during import. (PMT-3643)

  • When migrating from Plesk Onyx, an error in decrypting a password for an account could result in resetting passwords for all accounts. (PMT-3604, PMT-3605)

  • Extension data on the target server could be overwritten by data from the source server. Now by default the server-wide extension settings are not migrated. (PMT-3586)

  • Overuse policy for reseller accounts was not migrated and instead was reset to ‘Overuse of disk space and traffic is allowed’. (PMT-3469)

  • Database import failed if the PHP process had no write permission on the source server. (PMT-3682)

Linux
  • Copying a MySQL database from Plesk Onyx on a Linux server failed if the database server password was stored in plain text format. (PMT-3759)

  • Protected directories on subdomains were not migrated from DirectAdmin. (PMT-3764)

  • When using PureFTD on the source server, the site import performance was lower than expected. (PMT-3679)

  • Under certain circumstances, migration from a Plesk for Linux server could fail with an error message “Cause: ‘int’ object has no attribute ‘isdigit’”. (PMT-3621)

  • SSL Certificate Authority certificates were not migrated from DirectAdmin. (PMT-3613)

  • When migrating mail messages to Plesk for Linux via IMAP, if a mailbox name contained an uppercase character, the messages in it were not migrated. (PMT-3607)

  • When migrating from DirectAdmin, a cron task with a certain syntax could not be parsed. (PMT-3544)

  • When migrating from DirectAdmin, if a mailbox had an automatic reply set up, but the corresponding template file did not exist, the migration could not be performed. (PMT-3542)

Windows
  • When migrating from or to a Plesk server with a remote SmarterMail server: the type ‘A’ DNS records for mail (mail.*) were migrated incorrectly. (PMT-3725)

  • When migrating from Plesk with a remote SmarterMail server to Plesk with a local SmarterMail server, or vice versa, the webmail settings for hosting plans and subscriptions were not converted as intended. (PMT-3723)

19 May 2017

Extension Updates

Plesk Multi Server 1.2.0

  • A Plesk server having active subscriptions can now be added to a Plesk Multi Server infrastructure as a new service node.

  • A Plesk server having active subscriptions and being a service node in a Plesk Multi Server infrastructure can now be removed from it and turned into a separate Plesk server.

  • A service node could not be added if mail service was not installed on the management node. (EXTPMS-1333)

  • A service node could not be added if DNS server was not installed on the management node. (EXTPMS-1334)

  • Under certain circumstances, an error occurred on the Plesk Multi Server Settings page, making it unavailable. (EXTPMS-1315)

  • A task ‘Sync DNS records with DNS template’, running for a long time, could fail by timeout, returning HTTP response code 504. (EXTPMS-1162)

  • Earlier, the back synchronization process created a separate task to fetch statistics for each subscription, which caused an additional load on the server and slowed the process. (EXTPMS-1343)

    Now, by default, statistics for all subscriptions are fetched in a single task, which is run once a day. This behaviour can be configured in panel.ini:

    [ext-plesk-multi-server]
    statistics.period = 'backsync'
    

18 May 2017

Extension Updates

Let’s Encrypt 2.1.0

  • It is possible to include webmail to a certificate request and secure both the domain and webmail with this certificate.
  • Let’s Encrypt custom settings can be configured via the panel.ini file.
  • After a certificate for a subdomain had been issued, it was impossible to renew the certificate for the parent domain. (EXTLETSENC-105)

16 May 2017

Plesk Onyx 17.8 Preview 1

  • The Extension Catalog had received a new landing page with a series of improvements.

  • CLI for managing ModSecurity was significantly enhanced and now supports most features, available in Plesk Panel, including:
    • Selecting predefined and uploading custom rulesets,
    • Setting the active ruleset and update frequency,
    • Setting the web application firewall mode.
  • A detailed message, explaining the changes and consequences, is now shown when changing the hosting type. This message contains a complete list of folders that are going to be removed.

  • Redirects from HTTP to HTTPS on domain aliases have been improved to make a single SEO-safe redirect with HTTP response code 301.

    For example, if alias.tld is set as an alias for example.tld, and example.tld is secured with an SSL certificate, there is now a single redirect from http://alias.tld to https://example.tld.

  • Security improvements.

  • When trying to connect to an FTP storage, a ‘Curl error: (35) SSL connect error’ occurred. (PPP-29266)

  • In Power User view, attempts to remove a domain failed with a ‘Permission denied’ error. (PPP-29247)

  • Attempts to activate a terminated additional license led to Plesk removing the main license. (PPP-28991)

  • Additional users could not log in to Plesk because of a DNSSEC error. (PPP-28949)

  • A multiline mail bounce message could not be set via CLI. (PPP-28768)

  • If an FTP server for backing up had previously been configured incorrectly and using the server storage was forbidden, attempts to back up failed with an uninformative message. Now, Plesk shows a message explaining the requirement to configure an FTP storage. (PPP-28710)

  • Making API calls to Plesk resulted in an error if the <packet> tag was missing. (PPP-28705)

  • Customer could not change domain hosting settings for their domain if the subscription name was identical to the server’s hostname. (PPP-28667)

  • When a customer used the file-sharing option for public files and clicked ‘Link to This Folder’, the generated public URL for read-only visitors did not have the ‘www’ prefix. (PPP-28641)

  • Backup rotation from an FTP storage could consume extra disk space if the FTP server did not support the REST command. (PPP-28335)

  • Certain log messages from ModSecurity disrupted the functioning of the Log Browser page. (PPP-28282)

  • Starting multiple backup processes within a minute of each other caused one of them to fail. (PPP-27889, PPP-27484)

  • Pressing ‘Download Backup’ several times in a row caused Plesk to consume extra disk space. (PPP-27636)

  • The handler for the “Disk space limit for reseller account reached” event did not pass event parameters to commands. (PPP-27438)

  • Backup creation failed if the time of backup creation and upload exceeded the ‘FTP SessionTimeout’ value and the FTP repository did not support APPE/REST commands. (PPP-27354)

  • The “Maximum number of scheduled backup files to store” setting on the backup settings page was also applied to the external backup storages. (PPP-27351)

Linux

  • If the mailbox size for a subscription was set to unlimited, executing plesk repair mail <subscription> incorrectly changed the values in maildirsize file for each mail account under the subscription. (PPP-29237)

  • Browsing the access_log file in Plesk resulted in an error. (PPP-29214)

  • Upgrading the plesk-roundcube package resulted in overwriting PHP settings for Roundcube. (PPP-29088)

  • Trying to log in to Roundcube with an incorrect password resulted in an HTTP response code 500. (PPP-29087)

  • FastCGI PHP handler in the Service Plan was displayed in GUI as FPM by Apache. (PPP-29064)

  • When sending emails to a mail list, the Mailman generated a wrong DKIM signature. (PPP-28836)

  • If a backed up subscription contained more than 8GB of content files, it could not be restored from backup. (PPP-28793)

  • If the Skins & Color extension was installed in Plesk, creating a full server backup finished with a warning. (PPP-28765)

  • On Debian 8 servers, users could not log in to Horde if the ‘psa-kronolith’ component was installed. (PPP-28744)

  • The plesk repair fs command failed to check permissions on /var/lib/psa/dumps. (PPP-28599)

  • If a customer’s name contained Unicode characters outside of ASCII range, backing up such customer’s subscription had succeeded, but an error message was displayed. (PPP-28587)

  • If the name of a database included a dot, running the statistics utility resulted in a warning. (PPP-28531)

  • The mchk utility reset the ‘Certificate for securing mail’ setting to the default value. (PPP-28433)

  • Running the Watchdog Security Scan completed with a message ‘Checking file i18n versions [Update failed]’. (PPP-28221)

  • Under certain circumstances, updating Plesk from version 12.0 to Onyx resulted in an error message “ERROR 1049 (42000): Unknown database '-Br'”. (PPP-28194)

  • On Debian 8 x64 with tar v. 1.27.1 installed, if the web content directory contained a subdirectory or a file with a leading space in the name, the backup process got stuck, consuming 100% of CPU. (PPP-28176)

  • Sendmail failed to send email to the root account. (PPP-27696)

  • The plesk repair utility did not detect broken symlinks to Apache configuration files. Now, such broken symlinks are repaired correctly. (PPP-27477)

  • On Ubuntu 16.04 servers, Watchdog incorrectly reported the PHP-FPM service as being stopped. (PPP-27085)

  • Kaspersky AntiVirus could not correctly detect its PID. (PPP-27002)

  • On CloudLinux 7 servers, APS applications could not be installed on subscriptions for which CageFS was enabled. (PPP-25214)

  • On Debian 8 servers, restoring a subscription from a backup made on another Plesk server with a different mail server installed resulted in all mail for that subscription being permanently softbounced with a 4xx code. (PPP-22957)

Windows

  • MySQL 5.7 is now supported.

  • A customer had to manually change the publishing settings to enable web deploy from Visual Studio for ASP.NET Core applications. (PPP-29284)

  • If SmarterMail Pro was installed, the Outgoing Mail Control feature worked incorrectly. (PPP-29254)

  • If Plesk data directory and Plesk installation directory were different, upgrading from Plesk 17.0 to a later version failed with an ‘Access is denied’ message. (PPP-29170)

  • If the PHP temporary folder was not accessible, certain operations caused a php-cgi.exe error. (PPP-29081)

  • If the PHP temporary folder was not located on the drive on which Plesk was installed, the Let’s Encrypt extension could not renew certificates. (PPP-29077)

  • Enabling mail service with an API call resulted in webmail binding in IIS being removed. (PPP-28901)

  • Under certain circumstances, the functionality of Plesk utilities linked with C++/CLI assemblies was disrupted. (PPP-28747)

  • On servers under high load, server health statistics sometimes became unavailable. (PPP-28647)

  • On Windows servers, a system task could be scheduled multiple times, resulting in unreported errors. Now, the scheduler properly detects and rejects duplicate tasks. (PPP-28370)

Third-Party Component Updates

  • PHP 7.1 was updated to version 7.1.5.
  • PHP 7.0 was updated to version 7.0.19.

Windows

  • ASP.NET Core 1.1 was updated to version 1.1.1.
  • ASP.NET Core 1.0 was updated to version 1.0.4.

15 May 2017

Plesk Onyx 17.5.3 Update 6

Windows

  • If Plesk data directory and Plesk installation directory were different, upgrading from Plesk 17.0 to a later version failed with an “Access is denied” message. (PPPM-6138)
  • Under certain circumstances, the functionality of Plesk utilities linked with C++/CLI assemblies was disrupted. (PPPM-6025)

Third-Party Component Updates

  • PHP 7.1 was updated to version 7.1.5.
  • PHP 7.0 was updated to version 7.0.19.
Windows
  • .NET Core 1.1 was updated to version 1.1.1.
  • .NET Core 1.0 was updated to version 1.0.4.

Plesk Onyx 17.0.17 Update 26

Third-Party Component Updates

  • PHP 7.1 was updated to version 7.1.5.
  • PHP 7.0 was updated to version 7.0.19.

8 May 2017

Plesk Onyx 17.5.3 Update 5

  • Domain management operations sometimes failed with the “Exception: Access is denied for domain <ID>” error. (PPPM-6194)

Plesk Onyx 17.0.17 Update 25

  • Domain management operations sometimes failed with the “Exception: Access is denied for domain <ID>” error. (PPPM-6194)

4 May 2017

Extension Updates

WordPress Toolkit 2.0.4

  • The WP-CLI utility was updated to version 1.1.
  • Commands “list” and “info” were added to the WP-CLI utility. WordPress instances can be identified by the combination of “path” and “main-domain-id” (via WP-CLI as well).
  • Titles of WordPress toolkit pages now display WordPress instance URL along with its name.
  • If there were a large number of WordPress instances, during cloning, it took WordPress toolkit a lot of time to generate the list of available domains and subdomains. (EXTWPTOOLK-505)
  • There was no warning message that the destination WordPress instance will be replaced by the source one during synchronization. (EXTWPTOOLK-493)
  • During synchronization, database tables prefixes were changed even if users selected to synchronize only files. (EXTWPTOOLK-457)
  • Error messages were displayed in the panel log after the first WordPress instance installation. (EXTWPTOOLK-454)
  • If autoupdate settings were turned on in WordPress toolkit, and later they were changed manually in the configuration file, WordPress toolkit autoupdate settings were not changed accordingly. (EXTWPTOOLK-452)
  • During new APS WordPress installations, the instances were marked as not secure because database tables prefixes were also marked as not secure. (EXTWPTOOLK-395)
  • If during WordPress installation the page was refreshed, WordPress installation started again. (EXTWPTOOLK-365)
  • If during WordPress installation wordpress.org was not accessible from the Plesk server and the necessary data was not stored in WordPress toolkit cache, Plesk displayed an error message that was not explicit. (EXTWPTOOLK-361)
  • WordPress Toolkit was able to generate invalid database table prefixes starting with numbers in exponential notation (for example, 0E70IaqpI). (EXTWPTOOLK-111)
  • Context help from all WordPress toolkit screen states did not redirect users to the WordPress related pages in Documentation and Help Portal. (EXTWPTOOLK-6)
Linux
  • If WordPress Toolkit scanned for new WordPress instances and at least one of new instances was corrupt, scanning was performed with errors and not all new instances were found. (EXTWPTOOLK-477)

27 April 2017

Extension Updates

Plesk Migrator 2.7.9

  • Site migration was blocked if the source web server rejected requests without the User-Agent header. (PMT-3698)
Windows
  • Subscriptions migration failed and the subscriptions were marked as migrated with errors during migration from Plesk 8.6, 9.5, 10.4 for Windows. (PMT-3702)

26 April 2017

Plesk Onyx 17.5.3 Update 4

  • Incremental backups of IDN domains could not be created. (PPP-28673)
  • Subcscription-level users could not login to Plesk because of DNSSEC error. (PPP-29072)
  • When a customer used the file-sharing option for public files and clicked ‘Link to This Folder’, the generated public URL for read-only visitors did not have the ‘www’ prefix. (PPP-28753)
  • Backup creation failed if the time of backup creation and upload exceedeed FTP SessionTimeout and the FTP repository did not support APPE/REST commands. (PPP-28922)
  • Wildcard subdomains could not be renamed in UI. (PPP-29073)
  • Extesions catalog could not be loaded in UI in case of slow network connection. (PPP-29074)

Linux

  • Plesk 17.5 locales were updated. (PPP-28821)
  • FastCGI PHP handler in the Service Plan was displayed in GUI as FPM by Apache. (PPP-29075)
  • A subscription could not be restored from backup archives on an FTP repository if the backup contained one or more files larger than 8 GB. (PPPM-6039)
  • Server backup was completed with a warning if Skins & Color extension had been installed. (PPPM-6034)

Windows

  • Plesk 17.5 locales were updated. (PPP-28813)
  • Backup restoration from the FTP repository failed if the backup contained one or more files larger than 4 GB. (PPP-28881)
  • In some cases, micro-updates installation failed during installation of the base locale package. (PPP-28736)
  • Under specific circumstances, web statistics was not calculated for one domain either by Daily Maintenance Script or manually. (PPP-28679)
  • Under specific circumstances, incremental multi-volume backup failed because of the plesk_agent_manager.exe buffer overflow. (PPP-28921)

24 April 2017

Plesk Onyx 17.0.17 Update 24

  • Security enhancements.
  • A backup rotation from an FTP storage was not working if an FTP server did not support REST commands. (PPPM-5902)

Linux

  • A subscription could not be restored from backup archives on an FTP server if there were any content files larger than 8GB. (PPPM-6039)

Windows

  • Data could not be restored from backup archives on an FTP server if there were any content files larger than 4GB. (PPPM-6052)
  • In Plesk 17.0 micro-updates installation failed if all previous micro-updates had been installed before. (PPPM-6012)

Third-Party Component Updates

  • Roundcube was updated to version 1.2.4. (PPPM-5950)

20 April 2017

Extension Updates

Plesk Migrator 2.7

  • When migrating to a Plesk server using a non-English locale, a confusing error message was displayed if the name of one or more files or directories on the source server contained national characters. (PMT-3294)
  • The lack of notifications or a progress bar during post-migration checks could confuse the user. (PMT-3309)
  • Migration could fail if multiple perl versions were installed on the source server and the PATH environment variable pointed to a custom perl version. (PMT-3376)
  • Web content was not copied if SSH access to the source server was limited to specific users and the users ‘plesk-migrator*’ were not allowed access. (PMT-3385)
  • PostgreSQL databases could not be migrated if PostgreSQL server version 9.5 or later was installed on the source server. (PMT-3391)
  • Under specific circumstances, the “Failed to remove temporary user” error was displayed during migration even if the temporary user was removed. (PMT-3399)
  • Entries in the subscription log were not sorted by date. (PMT-3525)
  • Microsoft SQL Server databases could not be migrated if the Microsoft SQL Server instance on the source server was configured to use a nonstandard port. (PMT-3547)
  • The header on the migration screen was corrupted if the Plesk interface language was set to Italian. (PMT-3548)
  • When migrating from DirectAdmin, quota for mailboxes was set to 100 MB even if it was set to unlimited on the source server. (PMT-3550)
  • Trying to re-sync business objects after deleting a mail account on the source server produced a confusing error message. (PMT-3552)
  • During site migration, WordPress sites using a remote database were not re-configured to use the database migrated to the destination server’s MySQL server. (PMT-3562)
  • Removing the session folder created after initiating a site migration resulted in empty session folder and configuration file getting created. (PMT-3579)
  • If during migration names of some databases and database users were changed, after upgrading Plesk Migrator to the latest version and restarting the migration, the name changes were not preserved. (PMT-3582)
  • When migrating from DirectAdmin, if a mailbox and a forwarder with the same name were present on the source server, only the forwarder was migrated. (PMT-3585)
  • When migrating from Plesk Onyx, extension files stored in the “/usr/local/psa/var/modules/” directory were assigned incorrect ownership. (PMT-3587)
  • Migration from DirectAdmin failed if a DNS zone contained a white space character as a separator. (PMT-3600)
  • When migrating from Plesk, the “Restrict the ability to follow symbolic links” hosting plan setting was disabled on destination server even if it was enabled on the source. (PMT-3602)
  • Migration from DirectAdmin failed if a protected directory created in DirectAdmin was not physically present on the file system. (PMT-3618)
  • Migration from DirectAdmin failed if one or more mail users on the source server did not have a home directory configured. (PMT-3645)
  • Migration to Plesk Onyx could fail if one or more customers on the source server had unicode characters in their name. (PMT-3646)

17 April 2017

Plesk Onyx 17.5.3 Update 3

Third-Party Updates

  • PHP 7.1 was updated to version 7.1.4.
  • PHP 7.0 was updated to version 7.0.18.

Plesk Onyx 17.0.17 Update 23

Third-Party Updates

  • PHP 7.1 was updated to version 7.1.4.
  • PHP 7.0 was updated to version 7.0.18.

13 April 2017

Extension Updates

Git 1.1.0

  • When checking out a repository, users could only select existing directories for the deploy path. (EXTGIT-34)
  • Users could not create subdomains for addon domains with hosting type set to “Forwarding”. (EXTGIT-38)
  • Under specific circumstances, if more than one repository was checked out for a single domain, trying to remove a repository resulted in a different repository being removed instead. (EXTGIT-39)
  • Git repositories could not be created if deployment mode was set to “No Deployment”. (EXTGIT-40)
  • After changing the deployment mode of an existing repository from “No Deployment” to “Automatic Deployment”, an absolute deploy path was displayed instead of one relative to the subscription’s root. (EXTGIT-41)
  • Users could not authenticate with local Git repositories belonging to subdomains after the subscription’s system user password was changed. (EXTGIT-45)

Let’s Encrypt 2.0.3

  • The extension now logs its communication with the Let’s Encrypt servers in the panel.log. This enables better troubleshooting when there are some issues with requesting a certificate.

WordPress Toolkit 2.0.3

  • A WordPress site could not be cloned if wp-config.php file had non UTF-8 encoding. (EXTWPTOOLK-492)
  • A WordPress site was cloned incorrectly (some URLs of the cloned site referred to the source) if values of siteurl and home were not the same. (EXTWPTOOLK-488)

8 April 2017

Plesk Onyx 17.0.17 Update 22

Linux

  • After the latest Kaspersky virus database update, mail was no longer being scanned for viruses, and mail notifications were sent for every unprocessed email. (PPPM-6041)

6 April 2017

Extension Updates

Let’s Encrypt 2.0.2

  • Before requesting a certificate for multiple domain names, the extension verifies the ownership of each domain name included in the request. If a domain name passes the verification but its “www” counterpart fails it, the latter is excluded from the certificate signing request. After verification is finished, a warning message listing the excluded domain names is displayed.
  • For each secured domain, the extension creates a symbolic link to the certificate. When the extension renews the certificate, it updates the link, so that the link always points to the latest certificate.
  • On Windows 2012 and Windows 2016 servers, renewed certificates were not added to IIS.

5 April 2017

Plesk Onyx 17.5.3 Update 2

  • Several security issues were fixed. (PPP-27022)
  • If the FTP server did not support the REST command, backup rotation from an FTP storage could consume extra disk space. (PPP-28593)
  • When attempting to export a MS SQL database, Plesk provided a wrong download link. (PPP-28485)
  • If the extension catalog was inaccessible due to network connectivity, it was not possible to access the list of already installed extensions. (PPP-28510)

Linux

  • If DMARC reports were disabled, Plesk still executed the daily report task, which reported an error if the DMARC check history was empty. (PPP-28428)

Windows

  • Under specific circumstances, parallel execution of websrvmng.exe сaused an error “Cannot commit configuration changes because the file has changed on disk”. (PPP-28478)

Third-Party Component Updates

  • Roundcube was updated to version 1.2.4, including a fix for a vulnerability to an XSS attack.

Extension Updates

Cgroups Manager

  • The Cgroups Manager did not allow to set the CPU limit value above 100%. (PPP-28283)

31 March 2017

Extension Updates

WordPress Toolkit 2.0.2

  • A WordPress site installed on a subdomain can now be cloned to a new subdomain of the same domain.
  • A WordPress site could not be displayed in browser without manual configuration after cloning to a domain with “Preferred domain” set to a WWW-prefixed URL. (EXTWPTOOLK-474)
  • A WordPress site could not be displayed in browser without manual configuration if it was installed on a domain with “Preferred domain” set to a WWW-prefixed URL. (EXTWPTOOLK-472)
  • Automatic login to WordPress failed if “Preferred domain” in the domain’s hosting settings was set to another URL than the URL of the WordPress instance (for example to a WWW-prefixed URL while the instance had an URL without WWW prefix). (EXTWPTOOLK-470)
  • WordPress sites could not be synchronized if proc_open was disabled in PHP settings of the source or destination domain. (EXTWPTOOLK-466)
  • A WordPress site could not be cloned if proc_open was disabled in PHP settings of the source or destination domain. (EXTWPTOOLK-456)

29 March 2017

Extension Updates

Plesk Migrator 2.6.11

  • Migration of folders from a web site failed if an FTP server on the source server returned relative paths in the list of the folders. (MT-3563)
  • The list of folders for migration could not be obtained by Plesk Migrator if “.” or “..” were present in the folders list returned by the FTP server. (PMT-3569)
  • Migration of a web site content failed if the FTP connection was unexpectedly closed on copying the content. (PMT-3567)
  • Migration of a web site content failed after upgrading Plesk Migrator from version 2.1 or earlier to a later version. (PMT-3568)
  • The database of an imported WordPress site could not be migrated if the time of files migration exceeded the IDLE timeout of the source FTP server. (PMT-3575)
  • A WordPress site could not be migrated if redirection was enabled on the source domain. (PMT-3571)
  • Website migration could be blocked if the session folder was deleted after the migration. (PMT-3576)
  • Website migration failed with an uninformative error message if the document root could not be detected automatically. (PMT-3574)
  • The migration progress dialog got stuck if an error occurred while retrieving data from the source server. (PMT-3573)

28 March 2017

Extension Updates

Let’s Encrypt 2.0.1

  • Let’s Encrypt certificates could not be issued if no list of trusted root CAs could be found on the server. (EXTLETSENC-82)

27 March 2017

Plesk Onyx 17.0.17 Update 21

  • Security improvements.
  • Uploading a backup to an FTP storage failed if APPE and REST commands were disabled on the FTP server and the uploading time exceeded the timeout session value. (PPPM-5919)
  • If uploading a backup to an FTP storage failed, the error message contained no details about the last response from the FTP server. (PPPM-5920)
  • Backups could not be updated to an FTP server via FTPS. (PPPM-5957)

Linux

  • nginx was updated to version 1.11.10. (PPPM-5963)
  • In some cases Plesk upgrade to version 17.0.17 from an earlier version failed and a confusing error message appeared. (PPPM-5897)

Windows

  • Extensions could not be installed via the extension.exe CLI utility. (PPPM-5904)

Extension Updates

WordPress Toolkit 2.0.1

  • A WordPress instance installed via the Application Catalog had a database prefix marked as non-secure. (EXTWPTOOLK-463)
  • Automatic login to WordPress failed if the instance was installed using non-secure HTTP and the “Permanent SEO-safe 301 redirect from HTTP to HTTPS” option was enabled in the hosting settings of the domain. (EXTWPTOOLK-462)
  • If an URL of a cloned WordPress instance ended with a slash after registering the instance in WordPress Toolkit, this URL did not change to a new one after cloning. (EXTWPTOOLK-461)
  • A page for managing a WordPress instance could not be opened in WordPress Toolkit if the instance used an external MySQL server database not registered in Plesk. (EXTWPTOOLK-460)
  • Slashes were present at the end of the URL of a WordPress instance installed via the Applications Catalog. (EXTWPTOOLK-458)
  • WordPress could not be installed if proc_open was disabled in a domain’s PHP settings. (EXTWPTOOLK-455)

Let’s Encrypt 2.0.0

  • Domain aliases support was added.
  • IDN domains support was added.
  • Granular and reliable renew process: the extension now performs daily check for certificates which are about to expire and renews them not earlier than 30 days before their expiration.
  • Replaced Python-based certbot with PHP-based client.
  • Fixed installation issues with python dependencies when 3rd-parties upgrade broke compatibility.
  • Fixed python-related issues (virtualenv and so on) on Windows.

23 March 2017

Plesk Onyx 17.5.3

  • Extension Catalog improvements:
    • Browse extensions in style with a redesigned Extensions Catalog interface.
    • User-friendly and intuitive, it helps you get things done faster.
    • Use categories to filter available extensions and find the ones you need.
    • Check out new and featured extensions to discover what is popular with other Plesk users right now.
    • Request the creation of an extension if you could not find one to suit your needs.
    • Rate your favorite extensions!
  • Incoming mail verification using SPF and DMARC.
  • Installation prefixes of web applications were not passed to event handlers. (PPPM-5303)
  • The “Upgrade 3rd party components” option in “Tools & Settings” > “System Updates” was not being enabled during upgrade to Plesk Onyx. (PPP-27030)
  • Retrieving information about resellers via an XML API call using the &ltreseller&gt operator failed if one or more mailboxes owned by a reseller had disk quota greater than 4 GB configured. (PPP-27207)
  • Attempting to restore a corrupted Plesk backup stored on an FTP repository or to create an incremental backup based on it rapidly consumed all available disk space on the server. (PPPM-5407)
  • Plesk failed to remove temporary extension files created during backup from the “DUMP_TMP_D” folder. (PPPM-5405)
  • Extensions were not included in Plesk backups if there were one or more symlinks in the folder containing the extension’s files. (PPPM-5480)
  • The “last updated” date on the Plesk Home page was displayed incorrectly in French locale. (PPPM-5496)
  • The wording of the “Maximum number of scheduled backup files to store” setting in “Tools & Settings” > “Backup Manager” was misleading. (PPP-27349)
  • Plesk did not ensure that FTP repositories used for storing backups supported APPE/REST commands, which could result in issues during backup to FTP. (PPP-27355)
  • File Manager could hang when trying to display the content of a directory containing a big amount of files. (PPPM-3718)
  • If a new product configuration was enabled for a license having been installed in Plesk, this configuration was not updated when retrieving the license key in Plesk. (PPP-26361)
  • File Manager could not be opened for a domain if the domain directory contained a file or a folder with non-UTF-8 characters in the name. (PPPM-5040)
  • In some cases, the “Call to a member function getDomain() on null” error message was displayed in the Plesk user interface. (PPPM-5095)
  • In some cases, the “Call to a member function getValue() on null” error message was displayed in the Plesk user interface. (PPP-26552)
  • It was impossible to create a database user with the dot character in the name. (PPP-26627)
  • It was impossible to add a DNS record of the “TXT” type longer than 255 characters. Now, this limitation is increased to 512 characters. (PPPM-4778)
  • PHP handler of a subscription’s subdomain changed after changing PHP handler of the subscription. (PPPM-5142)
  • During operations with domain aliases, the event handler did not reflect the “OLD_DOMAIN_NAME” and “NEW_DOMAIN_NAME” variables in the logs. (PPP-26699)
  • Tasks from rotated scheduled backups were displayed in Plesk Backup Manager. This could look confusing for users. (PPPM-5838)
  • After successful Plesk update, the notifications about the previous failed updates were still shown in the Plesk user interface. (PPP-26931)
  • Changing the PHP handler or version for a domain caused the same change for a subdomain. (PPPM-4617, PPPM-5547)
  • In German locale, the email template for notification about overusing resources had a typo. (PPPM-5706)
  • Plesk administrator could not change any settings on the “Tools & Setting” > “Mail Server Settings” screen in Italian locale. (PPPM-5761)
  • Retrieving the list of available PHP handlers in use via an XML API call using the &ltphp-handler&gt operator took a long time if a large number of domains were hosted on the server. (PPPM-5621)
  • Backups could not be uploaded to an FTP repository via the FTPS protocol. (PPPM-5922)

Linux

  • Fail2ban was updated to version 0.9.6.
  • Dovecot was updated to version 2.2.27.
  • Roundcube was updated to version 1.2.3.
  • Horde was updated to version 5.2.13.
  • ProFTPD was updated to version to 1.3.5d.
  • nginx was updated to version 1.11.10.
  • On Ubuntu 16.04 servers using Dovecot, mail could not be delivered if apparmor was enabled on the server. (PPP-26959)
  • On CentOS 6 servers, running the plesk sbin mchk utility resulted in Postfix being removed from the list of services to be run on server startup. (PPP-27031)
  • Plesk administrator could not view or edit service plan settings if all fastcgi and PHP-FPM handlers were disabled on the server. (PPPM-5332)
  • Changing the PHP handler for a domain with multiple subdomains could result in an error if all of them were configured to use the “FPM application served by Apache” handler and the same version of PHP. (PPPM-5142)
  • Creating full server backups via the “Dropbox backup” extension sometimes resulted in backups consuming more disk space than expected. (PPPM-5475)
  • Updating the IP address of a subscription without hosting using the plesk bin subscription utility failed to update the subscription’s “*_webmail.conf” file. (PPPM-5464)
  • On Ubuntu 14.04 and Ubuntu 16.04 servers, AWStats web statistics could not be displayed. (PPP-27322)
  • On CentOS 7 servers, Apache failed to start if the “proxy.plesk” or the “proxy_fcgi.plesk” modules were enabled in Plesk. (PPPM-5490)
  • PostgreSQL databases could not be backed up if PostgreSQL version 9.5 or later was installed on the server. (PPP-27343)
  • Fail2ban hung when trying to monitor log files after restarting a server with many websites. (PPPM-4692, PPPM-5494)
  • On Plesk with Apache 2.4, a domain configuration could not be updated because Apache failed to restart. (PPPM-3904)
  • In some cases, a subscription could not be created via the Plesk user interface and a confusing error message appeared. (PPPM-4524)
  • It was impossible to upgrade Plesk from version 12.5 to Onyx if Plesk used MySQL server 5.7 with the strict mode enabled. (PPP-26650)
  • Logs were not rotated on an additional domain even if log rotation was enabled on the service plan of the additional domain’s subscription. (PPPM-5213)
  • The PHP memory limit could not be changed via an XML API request. (PPP-26819)
  • On Ubuntu 14.04 x64 servers, Apache failed to restart after the upgrade to Plesk Onyx. (PPPM-5510)
  • On CentOS 7.3 x64 servers, a customer could not set up a permanent 301 redirect from HTTP to HTTPS for their subscription. (PPPM-5813, PPPM-5434)
  • If the Outgoing Mail Control was enabled server-wide, it was not possible to forward messages from one local mailbox to another with the auto-reply option. (PPPM-5658)
  • Using permanent redirects both from HTTP to HTTPS and from domain.tls to www.domain.tld version caused a redirect chain. It was improved to redirect, for example, http://domain.tld to https://www.domain.tld. (PPP-27750)
  • Plesk Firewall could take too long to add a rule, probably causing a “Gateway timeout” error in Plesk GUI. (PPPM-5699)
  • If the website preview was switched from “Default Quick Preview” to “Quick Preview on an external domain name”, the server IP was removed from trusted_ips.inc. (PPPM-4051)
  • On CentOS 6 x64, changing the PHP version caused a change of PHP handler to FastCGI by Apache. (PPPM-5618)
  • Mistyping a Plesk URL in such a way that it ended with the word ‘login’ closed the current session and redirected the user to the Plesk login page. (PPPM-5736)
  • Plesk administrator could configure Apache and nginx in such a way that PHP files were not being handled even though PHP was enabled. (PPPM-5742)
  • Under specific circumstances, removing a subdomain in Plesk resulted in the PHP-FPM service starting to malfunction. (PPPM-4583)
  • Plesk administrator could not disable the “opcache” PHP extension. (PPPM-5769)
  • Apache sometimes failed to restart gracefully because a hardcoded timeout value was too small. (PPP-28181)
  • On Ubuntu 16.04 servers, the “php7” Apache module could not be enabled. (PPPM-5864)
  • Plesk failed to correctly respond to subscriptions exceeding the hard disk quota configured. (PPPM-5898)

Windows

  • MySQL was updated to version 5.6.35.
  • Upgrade to Plesk Onyx could fail if there were any *.xml_bak files in the %plesk_dir%\etc\disksecurity folder. (PPPM-5308)
  • Plesk backups could fail with the “Input string was not in a correct format” error if the data in the Plesk database were inconsistent. (PPPM-5341)
  • Health Monitor failed to display CPU and memory usage of “php-cgi” and “w3wp” processes. (PPPM-5424)
  • SmarterMail administrator password could no longer be changed in Plesk after changing it via the SmarterMail web interface. (PPPM-5467)
  • On Windows 2008 R2 servers, creating a domain with the “Prohibit the ability to override handlers via web.config” setting enabled in “Tools & Settings” > “Security Policy” could result in the website being inoperable. In such cases, disabling this option and reconfiguring the website via the plesk bin repair utility failed to restore the website to operation. (PPP-27345)
  • After upgrading to Plesk Onyx, websites could become inoperable if the “Prohibit the ability to override handlers via web.config” setting was enabled in “Tools & Settings” > “Security Policy”. (PPP-27346)
  • Certain functions of Plesk Reconfigurator were unavailable to users whose user account on the server was not named “administrator”, even if it was a member of the “Administrators” group. (PPP-27348)
  • After upgrading to Plesk Onyx, websites could become inoperable if custom permissions for the inetpub\vhosts folder were configured in the %plesk_dir%\etc\disksecurity\custom.xml file. (PPPM-5501)
  • Web Presence Builder displayed a confusing error message on the Documents tab. (PPPM-5235)
  • On Windows 2012 R2 servers, set as an IIS node, Dynamic Website Activation could disrupt the functioning of Plesk and all websites on the server. (PPP-27503)
  • A customer could not create a mail account for SmarterMail. (PPPM-5560)
  • Installing a Horde mail client did not require that the MySQL server was running, resulting in errors. (PPPM-5562)
  • Kaspersky Anti-Virus did not check mail messages to mailboxes that were created after setting it up as a default anti-virus. (PPPM-5619)
  • When Node.js was installed in a non-standard path, NPM install failed due to a missing permission. (PPPM-5651)
  • The service of SimpleDNS Plus v. 6.0.118.0 was erroneously detected as “Not Activated”. (PPPM-5678)
  • It was not possible to create a database with a name starting with an underscore. (PPP-27878)
  • Domain creation sometimes failed if one or more large files (700 MB or more) were present in the virtual host template. (PPPM-5773)
  • Plesk could not manage Microsoft SQL Server instances that were hardened in accordance with the PCI compliance guidelines. (PPPM-5802)
  • Plesk daily maintenance script failed to calculate website statistics. (PPPM-5827)
  • Running the plesk repair ftp utility produced confusing error messages if the path to an FTP user’s directory contained “/” characters instead of “". (PPPM-5839)
  • DKIM settings could not be managed if SmarterMail 14.x or earlier was installed on the server. (PPPM-5812)

Extension Updates

WordPress Toolkit 2.0

  • WordPress sites can now be cloned between domains or subscriptions.
  • A WordPress site’s data (including files and/or database) can be synchronized with another WordPress site.
  • A WordPress site can now be imported from another server. The Plesk Migrator extension is required for this functionality.
  • Search engine indexing can now be enabled or disabled for a WordPress site.
  • The events of creating and removing WordPress instances can now be processed by Plesk.
  • It is now possible to enable debugging options for a WordPress site.
  • Automatic updates can now be configured to install only the minor (security) updates.
  • The WordPress instance management page was improved to display more clear and detailed information.
  • The process of WordPress installation is now faster and has more detailed reporting.
  • During WordPress installation, WordPress Toolkit did not check if a database with the same name and database user already exists. (EXTWPTOOLK-423)
  • During installing WordPress on additional domains in Plesk for Windows, the “write/modify” permissions to the “wp-content” folder were not set automatically. As a result, images and themes of the WordPress installation could not be managed. (EXTWPTOOLK-419)
  • When switching to another WordPress instance from a WordPress instance settings dialog, the list of other instances was displayed without URLs. (EXTWPTOOLK-407)
  • In some cases, a confusing error message was displayed after WordPress installation was completed. (EXTWPTOOLK-343)
  • If MySQL server data directory in Plesk for Windows was changed so that it differed from the location of MySQL server executable files, WordPress could not be installed. (EXTWPTOOLK-326)
  • The “wp-config.php” file of a WordPress instance installed via WordPress Toolkit did not contain the “multisite” string, therefore it was inconvenient to enable multi-site WordPress. (EXTWPTOOLK-322)
  • When the Keychain for API Secret Keys and WordPress Toolkit extensions were installed in Plesk for Linux, reseller could not log in to Plesk. (EXTWPTOOLK-317)
  • Two quick WordPress installations run one by one on a domain, could lead to conflicts.(EXTWPTOOLK-288)
  • If an error occurred during WordPress installation, the full error description was not displayed in the maximized progress dialog. (EXTWPTOOLK-286)
  • During WordPress installation, the progress dialog was initially displayed minimized without showing information about the installation, and the list of WordPress instances did not refresh after the installation completion. (EXTWPTOOLK-285)
  • After renaming a domain with installed WordPress the “Site Address (URL)” parameter in WordPress was not changed. (EXTWPTOOLK-250)
  • If the value of the “Preferred domain” parameter was changed for the domain with installed WordPress, the automatic log in to WordPress from the Plesk user interface failed. (EXTWPTOOLK-249)
  • When access to WordPress Toolkit was restricted in Plesk configuration, an unclear error message was shown when trying to open WordPress Toolkit. (EXTWPTOOLK-237)
  • The “Update” and “View details” links were displayed merged in the Themes and Plugins tabs. (EXTWPTOOLK-141)
  • The “Owner” column in the list of WordPress installations contained a broken link if a subscription belonged to the Plesk administrator. (EXTWPTOOLK-33)
  • In some cases, WordPress sites were updated automatically even if automatic updates were disabled in their settings. (EXTWPTOOLK-20)

Plesk Multi Server 1.1.3

  • Compatibility fixes with Plesk Onyx 17.5.
  • During upgrade of the Plesk Multi Server extension, service node synchronization was performed thus changing service nodes status to “Being activated” and making them unavailable for management. (EXTPMS-1293)
  • An administrator could not create a new subscription on a service node if a public IP address was assigned to the default shared IP address. (EXTPMS-1184)

Plesk Migrator 2.6

  • Migration of files, databases, and WordPress sites from any server available via FTP is now supported.
  • Database content could not be synchronized in Plesk for Windows when different remote Microsoft SQL servers were used by the source and the target servers. (PMT-3509)
  • A database was duplicated during second migration of a subscription having capital characters in name. (PMT-3535)
  • During migration from DirectAdmin, content of administrator’s subscription became unavailable if the owner of the document root folder was incorrect. (PMT-3508)
  • Migration from DirectAdmin could not be started if a customer with non-unicode symbols in the name was present on the source server. (PMT-3540)
  • Migration from DirectAdmin could not be started if a mail auto-reply had been created for a domain on the source server and then the file with the auto-reply message had been deleted. (PMT-3542)
  • Migration from DirectAdmin was blocked if a cron task on the source server could not be parsed. (PMT-3544)
  • After migration from a custom panel, the Apache error log file could not be opened in the Log Browser because of incorrect permissions. (PMT-3460)
  • MySQL server databases could not be migrated from DirectAdmin if a remote MySQL server was used on the source server. (PMT-3545)

20 March 2017

Plesk Onyx Update 20

Third-Party Updates

  • PHP 7.1 was updated to version 7.1.3.
  • PHP 7.0 was updated to version 7.0.17.

Extension Updates

Plesk Multi Server 1.1.2

  • Multiple performance improvements related to task management were made.
  • A confusing error message appeared in the Plesk Multi Server user interface during operations with prohibited domain names. (EXTPMS-1274)
  • During synchronizing a subscription with its service plan, the “Permanent SEO-safe 301 redirect from HTTP to HTTPS” option became disabled in the subscription’s hosting settings, though, in the service plan’s settings, this option was enabled. (EXTPMS-1239)
  • The “Tasks” page loaded too slowly during operations with tasks in case of many tasks. (EXTPMS-1240)
  • After renaming a subscription, its name was not changed in the list of subscriptions on the management node. (EXTPMS-1214)
  • If a task on a service node failed by timeout, the service node was always set to the “Unavailable” status. (EXTPMS-1235)
  • A service node became unavailable in the case of a web server configuration error. (EXTPMS-1212)
  • When a service node was disabled and then enabled, DNS zone template synchronization started while the DNS zone templates of the service node and the management node were already in sync. (EXTPMS-1217)
  • When clicking the “Manage Node” link in the management node user interface, the HTTP connection was changed to HTTPS in the service node’s URL. (EXTPMS-1164)
  • If there were non-critical issues during service nodes synchronization, the administrator was not notified about them. (EXTPMS-1110)
  • The administrator could not search for tasks with the “New” and “Queued” statuses in the tasks list. (EXTPMS-1121)
  • The administrator could not sort tasks in the tasks list by the “Action” field. (EXTPMS-1109)

15 March 2017

Plesk Onyx Update 19

Third-Party Updates

  • The CVE-2015-8994 vulnerability in PHP 5.5, 5.6, 7.0, and 7.1 could lead to disclosure of sensitive data. To fix this vulnerability, the following configuration changes were made:
    • For PHP 5.5: the OpCache extension was disabled, and the opcache.enable directive was set to 0 in /opt/plesk/php/5.5/etc/php.d/10-opcache.ini.
    • For PHP 5.6, 7.0, and 7.1: the opcache.validate_permission directive was set to 1 in /opt/plesk/php/<PHP version>/etc/php.d/10-opcache.ini.

Note: Existing PHP configurations that had been changed by users will not be affected by those updates.

14 March 2017

Extension Updates

Node.js 1.3.2

  • Node.js applications failed to operate correctly if a subdirectory inside the subscription’s virtual host directory was configured as the application’s document root. (EXTNODEJS-31)

Ruby 1.3.2

  • Minor improvements.

6 March 2017

Plesk Onyx Update 18

  • Some error messages that appeared in the Plesk user interface during saving backup to an FTP storage, were not displayed in logs. (PPPM-5767)
  • If Fail2ban was installed, full server backup did not include the ‘fail2ban.local’ file. (PPPM-5400)

Linux

  • Backing up more than 1 GB to an FTP storage increased CPU load to 90%. (PPPM-5779)
  • Some error messages that appeared in the Plesk user interface during saving backup to an FTP storage, displayed “Broken pipe” instead of the text of the original error returned from the FTP storage. (PPPM-5686)
  • A PostgreSQL database could not be opened in phpPgAdmin if the Dropbox Backup extension was installed. (PPPM-5751)

Windows

  • It was impossible to secure MailEnable mail server with a Let’s Encrypt certificate. (PPPM-5781)
  • Let’s Encrypt certificate was not applied to MailEnable mail server after renewing. (PPPM-5853)
  • A Microsoft SQL Server 2016 database could not be restored from backup and a confusing error message was displayed in the Plesk user interface. (PPPM-5754)

3 March 2017

Extension Updates

Security Advisor 1.4.0

  • The System tab now displays the promos of Virtuozzo ReadyKernel and KernelCare and allows installation of one of those tools.

2 March 2017

Extension Updates

Plesk Migrator 2.5

  • Migration from DirectAdmin 1.51 is now supported.
  • Migrated databases are automatically renamed before restoration to avoid conflicts in cases of the same names of databases and database users.
  • Administrator can now configure the depth of checked web site links in post-migration checks.
  • Migration from Plesk 11.0 failed when a custom button with an icon in PNG format was configured on the source server. (PMT-3458)
  • Migration on Windows could not start if the path to the ‘plesk’ utility was not specified in the PATH variable of the target server. (PMT-3452)
  • Migration on Windows could not start if no PHP handlers were installed on the target server. (PMT-3472)
  • MySQL databases could not be migrated if an incorrect or empty password was set in the MySQL configuration file. (PMT-3394)
  • Adjusting application settings could work infinitely in case when the parent folder of a web site on the source server contained symbolic links. (PMT-3412)
  • If an additional domain’s IP address differed from the subscription’s IP address, the DNS records of the additional domain could not be migrated. (PMT-3445)

21 February 2017

Extension Updates

Ruby 1.3.1

  • Ruby 2.4 is now supported.
  • Ruby 2.3 was updated to the version 2.3.3.
  • Ruby 2.2 was updated to the version 2.2.6.

20 February 2017

Plesk Onyx Update 17

Linux

  • PHP 7.0 packaged by Plesk is now shipped with the ‘redis’ and ‘xdebug’ PHP extensions.

Third-Party Updates

  • PHP 7.1 was updated to version 7.1.2.
  • PHP 7.0 was updated to version 7.0.16.

13 February 2017

Plesk Onyx Update 16

  • Sometimes, uploading Plesk backups to FTP failed because the stream cache size was being exceeded. (PPPM-5626)
  • Plesk always sent notifications whenever a scheduled full backup was created under a reseller account. (PPPM-5351)

Linux

  • On Ubuntu 16.04 servers, running the plesk repair fs -v command failed to correct permissions on file system objects. (PPPM-5712)
  • Under specific circumstances, full backups were created instead of incremental ones in Plesk. (PPPM-5447)

8 February 2017

Extension Updates

Virtuozzo ReadyKernel 1.0.1

  • If multiple versions of kernel were installed in the operating system, the extension could display an error even if the patch was installed successfully. (EXTPLESK-159)
  • If no patches were available for the operation system kernel, the extension displayed a non-informative message. (EXTPLESK-160)

2 February 2017

Extension Updates

WordPress Toolkit 1.4.0

  • WordPress is now installed directly from wordpress.org instead of the Applications Catalog.
  • Any WordPress installations (including manually installed ones) can now be removed via the WordPress Toolkit user interface.
  • Resellers now have access to a single screen that lists all WordPress installations that belong to them and their customers.
  • The default protocol during WordPress installation was HTTP. Now it is changed to HTTPS. (EXTWPTOOLK-245)
  • A non-informative message was displayed in the user interface for WordPress installations of earlier versions. (EXTWPTOOLK-238)
  • During custom installation, the prefix of database tables was different from the one specified in the installation settings. (EXTWPTOOLK-236)
  • If a WordPress site name contained special symbols (for example, apostrophe), HTML code was displayed instead of such symbols in the user interface. (EXTWPTOOLK-220)
  • The owner of a subscription without a permission to manage WordPress Toolkit could see an added installation in the WordPress Toolkit. (EXTWPTOOLK-206)
  • The “Synchronize” button name was confusing for the users, so this button was renamed to “Refresh”. (EXTWPTOOLK-199)
  • The display name of the WordPress administrator was displayed in the “Change Account on the WordPress Installation” dialog instead of the user name. (EXTWPTOOLK-185)
  • When trying to install WordPress 3.6 version (that is no longer supported) an incorrect version number was displayed in the error message. (EXTWPTOOLK-166)
  • When installing plugins or themes to all WordPress installations, broken WordPress installations were available for selection. (EXTWPTOOLK-135)
  • In some cases, the menu for selecting WordPress installations for installing plugins or themes was hidden in the user interface. (EXTWPTOOLK-134)
  • In some cases, WordPress installation settings could not be updated and a confusing error message was displayed. (EXTWPTOOLK-117)
  • If a WordPress installation was broken, no information about its domain was displayed in the list of WordPress installations. (EXTWPTOOLK-25)
  • If a WordPress installation had been manually removed, it could not be correctly removed from the list of WordPress installations. (EXTWPTOOLK-17)

1 February 2017

Plesk Onyx Update 15

Linux

  • On CentOS 6 and 7, CloudLinux 6 and 7, and Red Hat Enterprise Linux 6 and 7 servers, after installing Plesk Onyx update 14, mail retrieved via the POP3 protocol could not be read. (PPPM-5676)

30 January 2017

Plesk Onyx Update 14

  • API requests referring to a domain name including letters with umlauts or a number of other special symbols could not be completed successfully. (PPPM-5563)
  • Retrieving the list of available Plesk backups took a long time if the FTP repository was misconfigured. (PPPM-5438)

Linux

  • Plesk could not be updated if the Epel repository was enabled. (PPPM-5517)
  • Users could not create MariaDB database users via phpMyAdmin 4.6.5.1. (PPPM-5428)
  • On servers with phpMyAdmin version 4.6.5.1 installed, users could not execute routines. (PPPM-5413)
  • On servers with phpMyAdmin version 4.6.5.1 installed, exporting a MySQL database in the .sql format resulted in a malformed database dump that could not be imported. (PPPM-5418)
  • On servers with phpMyAdmin version 4.6.5.1 installed, database users could not be added via phpMyAdmin. (PPPM-5428)

Windows

  • Under specific circumstances, the creation of a subscription or a server backup failed with the “Unable to get file attributes. File will not be archived.” error. (PPPM-5575)
  • Creating an FTP or database user while a full server backup was being performed resulted in an error. (PPPM-5434)

Third-Party Component Updates

  • phpMyAdmin was updated to version 4.6.6.

23 January 2017

Plesk Onyx Update 13

  • A number of updates to the Plesk locale.
  • Plesk backups could not be managed in “Tools & Settings” > “Backup Manager”. (PPPM-5542)
  • When migrating via the command line, subdomains could not be migrated if the parent domain’s hosting type was set to “Forwarding”. (PPPM-5525)
  • Uploading a Plesk backup file 1 GB or greater in size to an FTP repository resulted in the backup process hanging and blocking further attempts to back up. (PPPM-5472)

Linux

  • Clicking “Retrieve Keys” in the Plesk interface failed to retrieve the Plesk Multi Server license from KA. (PPPM-5568)
  • Plesk backups stored if an FTP repository could not be restored if the size of user data for one or more subscriptions exceeded 2 GB. (PPPM-5532)
  • On CentOS 7 x64 servers, Plesk installed in a Virtuozzo 7 container incorrectly detected the environment as a physical server. (PPPM-5509)
  • Gracefully restarting Apache a number of times during a short period of time could result in the mod_fcgid process crashing. (PPPM-4567)

Windows

  • Plesk backups could not be created if certain information was missing from the Plesk database. (PPPM-5573)
  • Under specific circumstances, the creation of Plesk backups failed. (PPPM-5457)
  • Plesk backups could not be uploaded to the FTP repository if the name of the subscription’s system user contained the “@” character. (PPPM-5430)

Third-Party Component Updates

  • PHP 7.1 was updated to version 7.1.1.
  • PHP 7.0 was updated to version 7.0.15.
  • PHP 5.6 was updated to version 5.6.30.

20 January 2017

Extension Updates

Plesk Migrator 2.4

  • During migration of mail content from a custom panel, it is now possible to define configuration settings like for a subscription content. In particular, it is possible to specify files or directories that should be excluded from copying or to define advanced file mapping.
  • A subscription belonging to a reseller could not be synchronized with an add-on service plan after migration. (PMT-3413)
  • Post-migration checks did not detect error messages or warnings on a web page in case when the HTTP code and the title of the web page were identical on the source server and on the target server. (PMT-3388)
  • During migration from a custom panel, post-migration checks were run for an enabled subscription with disabled main domain. As a result, error messages were reported. Now no post-migration checks are run in this case. (PMT-3378)
  • During migration from a custom panel, post-migration checks failed if a subscription had an add-on domain with an IP address other than the subscription’s IP address. (PMT-3371)
  • Post-migration checks did not detect some typical PHP error messages or warnings on web pages. (PMT-3389)

Linux

  • Migration could not be started on CentOs 5. (PMT-3417)
  • An unclear error message was displayed during migration if the configuration files of migrated applications contained non-unicode symbols. As a result, the adjusting of all other applications of the migrated subscription failed. (PMT-3398)
  • An unclear error message was displayed during migration if WordPress configuration files contained non-UTF-8 symbols. As a result, the adjusting of a particular WordPress instance failed. (PMT-3400)

Windows

  • Plesk Migrator can now be configured to detect the scriptiong settings (PHP version, ASP.NET version, ASP) of a subscription on the source server and migrate them properly.
  • Migration from a custom panel failed if the hosting description contained binary data in password fields of hosting description. (PMT-3390)
  • If the web.config file of a web site contained XML namespaces, the web site could stop functioning after migration. (PMT-3387)
  • Migration could fail if many (more than 10000) application files were changed during adjusting. (PMT-3409)
  • After migration from a custom panel there were no write permissions in the document root of a migrated subscription, it these permissions were not set explicitly in the hosting description. Due to this issue, the permissions settings sometimes were lost during migration from Plesk Onyx to Plesk Onyx. (PMT-3407)
  • Web Presence Builder was not registered in Plesk after migration to Plesk for Windows 12.5 or Onyx. (PMT-3369)
  • Some errors related to Microsoft SQL Server were not reported in Plesk Migrator log. (PMT-3362)
  • If migration of a Microsoft SQL Server database failed, Plesk Migrator added a database dump to an existing dump file during each new attempt to migrate, thus increasing the size of the dump file. (PMT-3411)

18 January 2017

Extension Updates

Node.js 1.3.1

  • Node.js 7 is now supported.
  • In some cases a domain’s document root directory could not be changed in Node.js settings. (EXTNODEJS-36)
  • It was impossible to set an application startup file to a file located in a subdirectory. (EXTNODEJS-20)
  • The Node.js user interface contained no quick link for editing an application startap file. (EXTNODEJS-18)

26 December 2016

Extension Updates

Plesk Multi Server 1.1.1.

  • It is now possible to add service node in the sync mode via CLI. In this case the added node will get the Active status.
  • A new subscription was created without hosting if its service plan had the “SSH access to the server shell under the subscription’s system user parameter set to /bin/bash(chrooted). (EXTPMS-1200)
  • A customer could not select a subscription in the list of subscriptions. (EXTPMS-1181)
  • A wrong message was displayed when reissuing a secret key for a service node via CLI. (EXTPMS-1180)
  • A service plan with a disabled Web statistics parameter could not be synced. (EXTPMS-1176)
  • A customer could not create a new subscription at a service node with a public IP address. (EXTPMS-1171)
  • If no country was specified for a customer, a new subscription creation could fail for this customer. (EXTPMS-1054)
  • A new subscription could not be created with a system user that had been already used for a deleted subscription. (EXTPMS-1084)
  • A new subscription could not be created if another subscription creation task with the same ID had been created earlier. (EXTPMS-1186)

22 December 2016

Extension Updates

Plesk Migrator 2.3.2

  • A new mode was added to migration from Confixx so that mail users will be able to log in to their mail accounts on the target server with their original usernames and passwords.
  • During migration from cPanel, it is now possible to change the document root of a migrated domain.
  • It is now possible to migrate mail content to/from Plesk Onyx using a remote SmarterMail server.
  • Domain alias could not be migrated if its name was present in the DNS template. (PMT-3340)
  • During migration, long FTP user names (with 16 or more symbols) were truncated to 15 symbols. Now the maximum length for FTP names is 16 symbols that corresponds to the limitation of Plesk. (PMT-3320)
  • An error occured during adjusting application files after migration if the file names contained non-ASCII symbols. (PMT-3334)
  • The description of copy content options in Plesk Migrator user interface was insufficient. (PMT-3330)
  • Migration of additional users associated with a subscription was performed incorrectly. As a result, the corresponding subscription could fail to migrate.(PMT-3351)

Linux

  • Web content could not be migrated from cPanel, Confixx, or Parallels Pro Control Panel for Linux, if CageFS was enabled on the source or target server. (PMT-3333)
  • Mail users having the permission to log in to Plesk on the source server could not log in to Plesk on the target server after migration. (PMT-3354)

Windows

  • Mail flags and folders were lost during migration from hMailServer 3. (PMT-2943)
  • Migration to/from Plesk failed if the Plesk database had a name other than ‘psa’. (PMT-3329)

21 December 2016

Plesk Onyx Update 12

  • PHP versions 5.6 and 7.0 shipped by Plesk now come with the ioncube-loader extension.

Linux

  • CentOS 7.3 is now supported.

14 December 2016

Extension Updates

WordPress Toolkit 1.3.1

  • WordPress installations on subscriptions using an old PHP version (5.3 or earlier) could not be managed from Plesk. (EXTWPTOOLK-188)

13 December 2016

Plesk Onyx Update 11

  • Plesk backups including customer or reseller accounts wit hthe “&” symbol in the account name could not be restored. (PPP-27089)
  • Under specific circumstances, files uploaded via the File Manager were placed in a different directory than the one selected by the user. (PPP-27075)
  • Clicking “Edit error page” for a domain belonging to a suspended subscription resulted in an error. (PPP-27045)

Linux

  • The dovecot service could not start if IPv6 was disabled on the server. (PPP-27057)
  • On CentOS 7 x64 servers, Roundcube filters configured to forward incoming mail based on specific parameters did not work. (PPP-27056)
  • On Ubuntu 16.04 x64 servers with Dovecot installed, mail could not be delivered if apparmor was enabled on the server. (PPP-26959)
  • The backup.log file did not include the information about cartain issues encountered during the backup process. (PPP-26351)

Third-Party Component Updates

  • PHP 7.1 is now supported.

Linux

  • Pigeonhole was updated to version 0.4.16 on Ubuntu 16.04.
  • Dovecot was updated to version 2.2.26.0 on Ubuntu 16.04.

12 December 2016

Extension Updates

WordPress Toolkit 1.3.0

  • It is now possible to manage general settings (like the site name or the interface language) of manually added WordPress installations by means of WordPress Toolkit.
  • An unclear message was displayed in the Plesk user interface if an unsupported version of WordPress was detected on a web site. (EXTWPTOOLK-130)
  • The –wp-cli command of the wp-toolkit utility returned an empty output. (EXTWPTOOLK-165)
  • On Windows, securing WordPress did not work for installations on additional domains or subdomains. (EXTWPTOOLK-133)

9 December 2016

Plesk Onyx Update 10

Third-Party Component Updates

  • PHP 7.0 was updated to version 7.0.14.
  • PHP 5.6 was updated to version 5.6.29.

8 December 2016

Extension Updates

Plesk Multi Server 1.1.0.

  • Plesk administrator can now manage Plesk objects on the management node and the service nodes via CLI.
  • Mail sent between domains hosted on the same Plesk Multi Server infrastructure could not be delivered. (EXTPMS-954)
  • Under specific circumstances, IP addresses attached to a subscription could not be synced. (EXTPMS-949)
  • Plesk servers with missing entries in the DNS template could not be added to the master node. (EXTPMS-953)

Plesk Migrator 2.2.2

  • Migration to Plesk Multi Server is now supported.
  • Mail migration from hMailServer 5 is now supported.
  • During migration from cPanel, it is now possible to change document root of a subscription or a domain.
  • Migration of mail messages using the IMAP protocol from any custom server is now possible.
  • Administrator can now switch on automatic post-migration checks after migration.
  • After migration using the IMAP protocol, all messages on the source server were marked as read. (PMT-2939)
  • It was impossible to migrate several aliases of the same mail account. (PMT-3190)
  • Migration from Plesk Onyx could be blocked in cases of inconsistency of subscription limits or permissions on the source server. (PMT-3175)
  • It was impossible to enable automatic deployment of RPC agent after an attempt to start migration with manual deployment of RPC agent. (PMT-3229)
  • After custom migration, post-migration checks log file could contain error messages related to fake subscriptions that were created for grouping domains into a single subscription on the target server during migration. (PMT-2861)

Linux

  • In some cases, migration from Plesk failed if TLSv1.0 was disabled on the target server. (PMT-3276)
  • Migration failed if there were no ‘apache’ user on the source server. (PMT-3213)
  • If the Plesk Migrator extension installation failed, no error messages were displayed in the Plesk user interface. (PMT-3204)

Windows

  • A subscription with a DotNetNuke application failed to migrate from one Plesk Onyx server to another. (PMT-3192)
  • An incorrect message was displayed during migration of a subscription using a database with several tables. (PMT-3198)

6 December 2016

Plesk Onyx Update 9

  • The <hostname> placeholder can now be used in the Plesk DNS template.
  • Plesk license number was not included in the “Buy Now” URL. (PPP-26978)
  • Additional administrator account could not access the “My Profile” screen in Power User view. (PPPM-5272)
  • Plesk did not recognize the correct province code for Newfoundland & Labrador. (PPPM-5270)
  • MySQL databases moved from one subscription to another could not be opened in phpMyAdmin if both subscriptions used a common database user to manage all databases. Note: installing the update prevents the issue from occurring, but does not retroactively fix the already affected databases. To fix an affected database, create a new database user and assign the user to the database. (PPPM-5251)
  • Under specific circumstances, users could not upload files using the File Manager. (PPPM-5230)
  • Users could not configure or use the FTP repository for backups if the panel.ini file contained duplicate sections or other syntax errors. (PPPM-5317)

Linux

  • When restoring a full server backup, the logic for generating the event_handler processes was faulty. (PPP-27041)
  • Users could not authenticate via POP3 or IMAP after updating Dovecot manually or via the System Updates feature. (PPP-27009)
  • Browsing a domain alias resulted in an endless redirect loop if the alias domain name was similar to the name of the parent domain and the “Enable ‘Redirect with the HTTP 301 code” option was disabled in the alies settings. (PPPM-5290)
  • Changing PHP settings in Plesk resulted in the PHP handler for the domain being switched to ‘FPM application served by Apache’. (PPPM-5264)
  • Plesk installed on a VMware virtual machine sometimes incorrectly detected the environment as a physical server. (PPPM-5257)

Third-Party Component Updates

  • phpMyAdmin was updated to version 4.6.5.1.

Linux

  • Pigeonhole was updated to version 0.4.16 on Ubuntu 14.04.
  • Dovecot was updated to version 2.2.26.0 on Ubuntu 14.04.

Windows

  • ASP.NET Core was updated to version 1.1.

1 December 2016

Extension Updates

WordPress Toolkit 1.2.2

  • WordPress 4.7 is now supported.

28 November 2016

Plesk Onyx Update 8

  • Plesk administrators can now configure custom store hostname in the panel.ini file to be able to resell Plesk extensions in their own online store.
  • When backing up to an FTP repository, full backups were created instead of incremental ones. (PPPM-5274)
  • On the Plesk login page, selecting a different language from the menu did not result in the interface language changing. (PPP-26849)
  • Any FTP errors during the creation of a multi-volume backup stored in the FTP repository resulted in the backup file getting corrupted. (PPP-26843)
  • Under specific circumstances, users were unable to log in to Plesk via the Plesk Mobile application. (PPP-26768)

Linux

  • On CentOS 7 x64 servers with MySQL Community Edition 5.7 installed, the gems-pre component and the plesk-gems-pre package could not be installed. (PPP-26920)
  • Users could not use selective restore to recover individual Plesk objects from multi-volume backups stored in the FTP repository. (PPP-26869)
  • The dist-upgrade post_* script did not install Plesk updates. (PPP-26845)
  • When restoring a full server backup, the number of event_handler processes Plesk could create was not limited. (PPP-26817)
  • After restoring a domain with DKIM enabled, the “p=DKIM1;” prefix was added to the DKIM TXT record even it already existed. (PPP-26787)
  • The dist-upgrade script failed to update certain packages. (PPP-26765)
  • If Plesk was installed in a NAT environment, the default site preview failed to process HTTP headers in web server responses. In addition, links to resources (images, css, js on the same site) in the returned web page are broken. (PPP-26724, PPP-26726)
  • Mail headers of emails retrieved from a Plesk server via Outlook were blank if “DKIM spam protection” was enabled on the server. (PPPM-5070)

Windows

  • Disabled domains without a DNS zone could not be activated. (PPPM-5105)

Third-Party Component Updates

  • phpMyAdmin was updated to version 4.6.4.

Linux

  • Roundcube was updated to version 1.2.2.
  • Pigeonhole was updated to version 0.4.16 on all supported OSes except for Ubuntu 14.04 and Ubuntu 16.04.
  • Dovecot was updated to version 2.2.26.0 on all supported OSes except for Ubuntu 14.04 and Ubuntu 16.04.

Windows

  • BIND was updated to version 9.10.4-P4.

22 November 2016

Extension Updates

Multi Server 1.0.1

  • The command-line utility plesk ext plesk-multi-server for managing nodes and tasks was added.
  • Subscriptions could not be created if the A or AAAA records in the Plesk DNS template pointed to an public IP address. (PPP-26854)
  • Addon domain creation failed if the parent subscription was renamed before performing sync. (PPP-26669)
  • After sync, subscriptions exceeding plan limits were displayed as “Active” instead of “Unsynchronized” on the management node. (PPP-25327)
  • Installing a valid Plesk license on a service node with “Unsupported” status gave the Multi Server administrator access to controls they were not meant to have access to. In addition, it made returning to the management node interface impossible. (PPP-26437)
  • After a subscription was created, for the first few seconds it had “Provisioning Failed” status instead of “Provisioning”. (PPP-26771)
  • In status details of subscriptions with failed to be provisioned, the node status was listed as “Undefined” instead of “Unavailable”. (PPP-25334)

21 November 2016

Plesk Onyx Update 7

  • The help text for the Backup Manager ‘Exclude certain files from the backup’ control was improved.
  • When creating a Plesk backup, no useful information was displayed under “current operation” on the “Backup details” tab.(PPP-26740)
  • The unnecessary “[” and “]” symbols surrounding the “Install Now” prompt on the Plesk home page were removed. (PPP-26709)
  • HTML5 video tutorials could not be displayed properly. (PPP-26681)
  • Users could not upload files via the File Manager opened on a mobile device or in responsive view in a browser. (PPP-26644)

Linux

  • The reliability of the Plesk Installer repository was improved.
  • Users could not disable the Plesk implementation of Sender Rewriting Scheme due to the lack of controls. (PPPM-5227)
  • On Debian and Ubuntu servers, installing Plesk updates during cloning could fail with a “bad substitution” error. (PPP-26814)
  • On CentOS 7 x64 servers, creating an incremental backup stored in an FTP repository resulted in the backup process hanging and consuming a lot of memory if there was not enough free disk space in the DUMP_D directory. (PPP-26775)
  • After performing a “Debian 7 to Debian 8” dist-upgrade on a server with Plesk installed, Fail2ban could no longer be managed via the f2bmng utility. (PPP-26522)

Windows

  • Users could not use selective restore to recover individual Plesk objects from multi-volume backups stored in the FTP repository, and when backing up to an FTP repository, full backups were created instead of incremental ones. (PPP-26791)
  • The MySQL server could not start on a server with the “Active Directory Domain Services” role configured. (PPPM-5171)
  • After backing up and restoring extension data in Plesk, national characters were replaced with the “?” sign. (PPP-26332)

16 November 2016

Extension Updates

Ruby 1.3.0

  • Security enhancements.

Node.js 1.3.0

  • A quick link for editing the application startup file was added to the application settings screen.
  • The ability to set the domain’s document root directory was added to the application settings screen.
  • Security enhancements.

DNSSEC 1.2.0

  • The extension was translated into a number of languages.

Docker 1.3.1

  • The extension locale was updated.

14 November 2016

Plesk Onyx Update 6

  • The “additional_license_expired” event was added to the Event Manager.
  • A number of updates to the Plesk locale.
  • A number of security enhancements.
  • Trying to log in automatically using a relative path in the success_redirect_url resulted in a 404 error. (PPPM-3729)
  • After restoring in Plesk Onyx a Plesk backup made in an earlier Plesk version, DKIM keys in the Plesk database and the mail server configuration did not match those in the DNS zone. (PPP-25564)
  • Unclear errors were logged in the panel.log file if the psaadm user lacked permissions on the %plesk_dir%/var/backup_encrypt.lock file. (PPP-26653)

Linux

  • Signature verification failed for DKIM-signed mail sent from one Plesk server to another due to excessively strict DKIM canonicalization. (PPPM-5149)
  • Kaspersky Antivirus could not be enabled even if the corresponding additional license was installed in Plesk. (PPP-26739)
  • The plesk_cgroups service generated a lot of confusing error messages in the logs. (PPPM-5163)
  • On Ubuntu 14.04 servers, MySQL failed to start on server restart. (PPP-26472)
  • Mail sent from one Plesk server installed on Ubuntu 14.04 via Virtuozzo EZ templates to another was rejected due to identical hostnames being set in Postfix configuration files. (PPP-26735)
  • Dist-upgrade failed on Plesk servers with /bin/sh pointing to /bin/dash. (PPP-26764)
  • Disabled domains without a DNS zone could not be activated. (PPPM-5105)
  • Running the plesk sbin mchk utility removed all records from the local_domains table of the SpamAssassin’s greylisting database. (PPPM-5109)
  • Log Browser failed to properly parse the Phusion Passenger logs. (PPP-26586)
  • After upgrading to Plesk Onyx, Apache configuration files for domains could not be generated if a custom template containing non-existent files was used. (PPPM-5104)
  • The collectd service generated a lot of confusing error messages in syslog if one or more resource controllers were not installed. (PPP-26596)
  • Mailbox size was reported incorrectly if the directory storing the mailbox data was stored on a partition with a specific file system (e.g. xfs). (PPPM-5114)
  • Under specific circumstances, a large number of sw-engine processes for event handlers could be created, consuming server RAM and causing performance issues. (PPP-26712)
  • The “System Update” functionality was unavailable in Power User view with custom view settings configured.(PPP-26730)

Windows

  • When restoring a backup stored on an FTP repository, mail content was not restored. (PPP-26638)
  • Under specific circumstances, Plesk backup could hang indefinitely. (PPPM-5130)

Extension Updates

Plesk Migrator 2.1.12

  • The reliability of post-migration checks has been improved.

11 November 2016

Extension Updates

WordPress Toolkit 1.2.1

  • The list of WordPress installations was not displayed to users logged in to Plesk using the Turkish locale. (EXTWPTOOLK-121)

9 November 2016

Extension Updates

Plesk Migrator 2.1.11

  • Mail content from custom hosting was always migrated in one thread regardless of the configuration file settings. (PMT-3215)
  • Migration of big files (in particular, database dump files) from a Windows server was too slow. (PMT-3214)
  • Migration from Windows server with manual RPC agent deployment could not be started if the built-in administrator password of the source server was not specified. (PMT-3228)
  • During migration from Confixx, all domains were dumped without “www” prefix, so that “www”-records were absent in the domain’s DNS zone after the migration. (PMT-3209)
  • Migration of a subscription content started only after all hosting objects had been created in all migrated subscriptions. (PMT-3216)

2 November 2016

Plesk Onyx Update 5

  • Virtuozzo 7 is now supported, starting from Update 1 Hotfix 1 (7.0.1-686). For details, refer to: https://help.virtuozzo.com/customer/portal/articles/2622351. Note:
    • Virtuozzo increased security for CentOS 7 containers with this update. Now containers are created with firewall enabled by default.
    • Plesk administrator needs to open ports that are necessary for Plesk: https://kb.plesk.com/en/391.
  • The Resource Controller feature is now available on Virtuozzo 7. New Virtuozzo Application templates were created to support this functionality.
  • Plesk administrator’s PHP version was updated to 5.6.27.
  • Execution of system operations in Plesk user interface became faster.
  • Saving Plesk backup to FTP storage failed with a confusing error message in the backup log. (PPP-26576)
  • Customer could not restore several selected objects after server backup. (PPP-26564)
  • Plesk user interface view could not be changed via CLI.(PPP-26550)
  • It was impossible to use an FTP server with extended passive mode disabled as FTP storage for a backup. (PPP-26546)
  • A DNS record of PTR type could not be added in DNS settings of a subscription for an IPv6 address with a 3-digit netmask. (PPPM-5063)
  • When a suspended customer was removed and then restored from a backup, the status of the domain mail service on this customer’s subscription was not restored. (PPP-26450)

Linux

  • Virtuozzo Linux 7 is now supported on Virtuozzo 7. Plesk can be installed on Virtuozzo Linux container using Virtuozzo templates. Refer to https://virtuozzo.com/products/virtuozzo-linux/.
  • Unnecessary warning messages were displayed when Plesk was installed with the Phusion Passenger server component.(PPP-26597)
  • Garbage directories were present in the DUMP_D directory after restoring a subscription from a backup stored on FTP. (PPP-26517)
  • After installing Plesk, the automatic updates for third-party components shipped by Plesk were disabled. (PPP-26511)
  • SpamAssassin failed to start if Plesk was installed on CentOS with IPv6 support turned off. (PPP-26509)
  • Removing the Phusion Passenger server component did not disable Phusion Passenger in Apache, and the server configuration was broken. (PPP-26453)

Windows

  • Duplicated Node.js items were present in the components list of Plesk installer for Windows. (PPP-26387)
  • Server backup failed if an application was installed from the APS catalog but the APS package archive was absent in the file system.(PPPM-5030)

Extension Updates

Multi Server 1.0.0

Key Features
  • Automatic and manual distribution of subscriptions between connected service nodes.
  • All Plesk users, including administrators, can log into to all connected servers from a single place.
  • Centralized account management across multiple Plesk instances.
  • Centralized management of tools and settings across multiple Plesk instances.
  • API for billing / external system integration
  • WHMCS billing support out of the box

See more details: About Plesk Multi Server.

Limitations
  • CLI is not supported
  • Resellers are not supported
  • Linux only support
  • Extensions from Plesk Extensions catalog are supported, no custom extensions uploaded directly to panel supported
  • No dedicated mail service support
  • No central DNS support

See more details: Plesk Multi Server Roadmap.

Docker 1.3.0

  • Docker is supported on Virtuozzo 7 and separate Virtuozzo Application templates are now available for Plesk Docker.

WordPress Toolkit 1.2.0

  • If an extension version was changed from 2-digit to 3-digit, the extension upgrades were unavailable. (PPP-26678)

27 October 2016

Extension Updates

Plesk Migrator 2.1.8

  • Mail content can now be migrated from hMailServer 5.
  • Plesk Migrator can now be installed from Plesk Extensions Catalog on Linux.
  • In some cases, restoration of Microsoft SQL database or MySQL database on Windows failed with an error on access to the dump. (PMT-3187)
  • Secondary transfer of a mail message without header to SmarterMail failed. (PMT-3189)
  • When a subscription was migrated from Plesk Expand with Centralized Mail server, mail service was disabled on the target server. (PMT-3148)
  • The Overview tab of the Plesk Migrator user interface had bad appearance when some particular Plesk skins were used. (PMT-3201)
  • Sites having errors on both source and target servers were marked as migrated with errors during the post-migration check.(PMT-3172)
  • An add-on domain could not be migrated if a DNS record corresponding to its name already existed in the target server’s DNS template. (PMT-2580)

WordPress Toolkit 1.1.1

  • It was impossible to change administrator’s access credentials for automatic logging into WordPress 4.6. (EXTWPTOOLK-114)

24 October 2016

Plesk Onyx Update 4

  • Adding a second IP address to a Plesk server and configuring the mail server to use it for outgoing mail resulted in webmail becoming inaccessible. (PPP-26499)
  • Individual objects (such as mailboxes) could not be restored from server level Plesk backups. (PPP-26496)
  • Retrieving the status of the DNS zone template via XML API resulted in the “enabled” message even if the DNS zone template was disabled. (PPP-26484)
  • Backing up to the FTP repository failed if the backup file could not be uploaded in one hour. (PPP-26478)
  • Updated additional keys for ISV extensions could not be retrieved. (PPP-26447)

Linux

  • Plesk installed on a Xen virtual machine incorrectly detected the environment as a physical server. (PPPM-5075)
  • Backups stored in the FTP repository could not be restored if the DUMP_D and DUMP_TMP_D directories were located on different devices. (PPP-26469)
  • In Site Preview, users could not log in to Magento. (PPP-26455)
  • Plesk installed on a Proxmox virtual machine incorrectly detected the environment as a physical server.(PPPM-4825)
  • On Ubuntu 12.04 x64 servers, setting the PHP handler for a domain using PHP 5.3.10 supplied by the OS vendor to “FPM application served by nginx” resulted in an error. (PPP-19481)

Windows

  • Password-protected incremental backups stored in the FTP repository could not be restored if the “Input password manually” option was selected. (PPP-26461)

Extension Updates

Docker 1.2

  • Docker extension installation hung on Linode servers with Ubuntu 16.04. (EXTDOCKER-25)

Ruby 1.2

  • Ruby versions were updated to 2.1.10, 2.2.5, 2.3.1. Bundler version was updated to 1.13.5. The rbenv utility version was updated to 1.1.0. (EXTRUBY-13)

Node.js 1.2

  • Node.js versions were updated to 4.6.1 (npm 2.15.9) and 6.9.1 (npm 3.10.8). (EXTNODEJS-8)

18 October 2016

Plesk Onyx Update 3

Third-Party Component Updates

  • PHP 5.6 was updated to version 5.6.27.

Extension Updates

Docker 1.1

  • Incorrect hint was displayed in the Environmental variable value field in a container’s settings. (EXTDOCKER-19)
  • In the case of using a remote Docker, no hint was displayed for the SSL icon on the “Tools & Settings > Docker” page. (EXTDOCKER-8)
  • HTML tags were displayed in the Plesk search results for the found Docker Catalog location. (EXTDOCKER-6)
  • When a Docker proxy rule was deleted from the domain’s Proxy Rules page and from Websites & Domains, different confirmation dialogs were displayed. (EXTDOCKER-2)

Ruby 1.1

  • Security Improvements.
  • Application Root could not be changed from the Ruby page of a subscription. (EXTRUBY-8)
  • Environment settings were ignored during Rake tasks execution so that all Rake tasks were executed in the default “development” environment. (EXTRUBY-6)

Node.js 1.1

  • Security Improvements.
  • Button descriptions were missing on the Node.js page of a subscription. (EXTNODEJS-2)

WordPress Toolkit 1.1

  • In some cases, the extension upgrade failed. (EXTWPTOOLK-116)

Plesk Migrator 2.1.4

  • Migration from Plesk Onyx was blocked in case of data inconsistency on a source server. (PMT-3175)

17 October 2016

Plesk Onyx Update 2

  • Users had to enter the login and password In Plesk Mobile after they already logged in to Plesk. (PPP-26433)
  • The Plesk installer displayed incorrect information about available update for PHP 5.4 after installation. (PPP-26362)
  • If a subscription backup was encrypted with a password and stored in an FTP storage, it could not be decrypted during the restoration. (PPP-26355)
  • An additional license key for DNSSEC could not be renewed. (PPP-26307, PPP-26425)
  • A confusing error message “Zend_Exception: No entry is registered for key ‘dbAdapter’” was displayed in Plesk installed on Virtuozzo containers if Plesk was unavailable due to container offline management settings.

Linux

  • A confusing error message was displayed after removing a subscription with a mail alias and Plesk Premium Antivirus switched on. (PPP-26377)
  • It was possible to specify the soft limit greater than the hard limit on system resources. (PPP-26386)
  • Scheduled backup could not be run on Ubuntu 16.04. (PPP-26272)

Windows

  • A remote SmarterMail Server could not be set as default main server. (PPP-26364)
  • System time could not be saved if a one-digit number was set for hours. (PPP-26378)

Third-Party Component Updates

  • PHP 7.0 was updated to version 7.0.12.

11 October 2016

Plesk Onyx 17.0.17

  • Plesk installation using Virtuozzo Application templates is now available on Parallels Virtuozzo Containers 4.6/4.7.
  • Plesk installation using Virtuozzo Application templates is now available on Parallels Cloud Server 6.
  • PHP 5.6 was updated to version 5.6.26.
  • PHP 7.0 was updated to version 7.0.11.
  • A number of security and stability enhancements.
  • New sessions could not be created via XML API on Plesk servers where Plesk license was expired or license limits were exceeded. (PPP-26132)
  • Changing hosting settings of subdomains resulted in the PHP handler for the subdomain being changed as well. (PPP-25976)

Linux

  • MySQL Community Edition support was added to Plesk.
  • Plesk System Updates tool now allows installing updates from repositories other than those the packages were installed from.
  • On Centos 7, Debian 8, and Ubuntu 14.04 servers, OpenSSL for nginx was updated to version 1.0.2j.
  • Legacy migration manager component has been removed from the list of available components and EZ templates for Virtuozzo.
  • On Ubuntu 16.04 servers, logging in to Plesk resulted in errors if the “lxc” package was installed on the server. (PPP-25871)
  • Plesk Onyx installed in HyperV or XEN environments failed to recognize Plesk for HyperV and Plesk for XEN licenses as valid. (PPP-25993, PPP-25875)
  • On Red Hat Enterprise Linux 7 x64 servers, the Docker extension could not be installed. (PPP-25884)
  • On CentOS 7 and CloudLinux 7 servers, managing IP addresses in Plesk led to errors due to the absence of the “net-tools” package by default. (PPP-26049)
  • Plesk Server Health Monitor failed to display the correct information. (PPP-26205)
  • Plesk System Updates tool notifications did not include repository information. (PPP-25800)
  • On Ubuntu 12.04 servers, MySQL failed to start if IPv6 was disabled on the server and MySQL version was higher than 5.5.3. (PPP-19879)
  • The number of worker spamd processes in spam filter settings could not be set to greater than five. (PPP-21103)
  • Database users with usernames containing prohibited symbols could be created in Plesk which resulted in issues with database creation. (PPP-25979)

Windows

  • MySQL 5.5 used for storing the Plesk database was updated to version 5.5.52.
  • MySQL 5.6 used for storing customer databases was updated to version 5.6.33.
  • OpenSSL was updated to version 1.0.2j.
  • BIND was updated to version 9.10.4-P3.
  • MySQL instances no longer run under the local system account.
  • Changing system user passwords took progressively longer the more domains were assigned to the subscription. (PPP-26133)
  • Under certain conditions, PHP “notice” level errors were displayed in the Plesk interface. (PPP-25928)

14 September 2016

Plesk Onyx 17.0.16

  • The ability to add additional services to service plans and subscriptions was added to Plesk SDK.
  • The event listener fixing the permissions of the wp-config.php file now works even if the WordPress Toolkit extension is not installed.
  • The stability of backing up to an FTP repository has been improved.
  • The default Plesk skin was updated.
  • Information about SSL/TLS certificates securing the mail server and webmail is now included in Plesk backups.
  • Adding an SSL/TLS certificate to a domain’s certificate repository erased the certificates present in its subdomains’ certificate repositories. (PPP-25275)
  • Mail accounts with access to Plesk but no mailbox could not be restored from Plesk backups. (PPP-25403)
  • Installing both the Docker and the Amazon Route 53 extensions on a Plesk server resulted in issues with signing in. (PPP-23643)
  • Certain Plesk backup error messages were non-informative. (PPP-25360)

Linux

  • Ubuntu 16.04 is now supported.
  • Dist-upgrade from Ubuntu 14.04 to Ubuntu 16.04 is now supported.
  • MySQL Community Edition support was added to Plesk. (v5.6 is supported; v5.7 has open issue, will be resolved till RTM)
  • Plesk System Updates tool now logs its output to a separate file.
  • Plesk System Updates tool now checks for the activity of other package management tools.
  • Plesk now displays notifications about resource limits and thresholds being achieved.
  • Plesk can now be installed on Ubuntu 14.04 and 16.04 servers with AppArmor enabled.
  • Failed Plesk upgrades sometimes resulted in the ‘apsc.aps_application_resource’ table being removed from the ‘apsc’ database. (PPP-25200)
  • On Ubuntu 12.04 x64 servers with AppArmor enabled, the BIND DNS Server could not be started. (PPP-18290)
  • Trying to access Tools & Settings > Services Management resulted in an error if the ‘resource controller’ component was installed and enabled, but its configuration was missing from the Plesk database. (PPP-25364)
  • Scheduled tasks were executed in different environments depending on whether the user pressed ‘Run Now’ on the ‘Scheduled Tasks’ screen the ‘Edit Task’ screen. (PPP-25575)
  • On CloudLinux 7 x64 servers, issues could occur with the System Updates tool because the default system repositories were specified incorrectly. (PPP-25528)

Windows

  • Horde now uses PHP 5.6.
  • On Plesk servers with Web Presence Builder installed and WPB debug logging enabled, accessing the Backup Manager resulted in an error. (PPP-25433)
  • Creating a mail account resulted in an empty error message if specific settings were missing from the Plesk database. (PPP-25507)
  • AWStats statistics were sometimes calculated incorrectly for domains that were assigned as the default domain for an IP address. (PPP-25499)
  • Kaspersky Anti-Virus virus database was not updated. (PPP-25701)
  • Mail from email addresses added to the black list was delivered instead of being deleted. (PPP-22878)

16 August 2016

Plesk Onyx 17.0.15

  • SRS support was added to Plesk.
  • DKIM support was added to Plesk.
  • Node.js support was added to Plesk.
  • The support for notifications about reaching cgroup limits was added to Plesk.
  • The ability to secure the Plesk mail server with an SSL/TLS certificate was added to Plesk.
  • The ability to manage basic Rake tasks was added to Plesk.
  • Certain extension data is now automatically included in server level backups for all Plesk extensions.
  • The ability to manage email notifications was added to the Plesk SDK.
  • The ability to enable and disable extensions was added to the Plesk SDK.
  • The ability to add promotional blurbs about extensions on the “Websites & Domains” screen was added to the Plesk SDK.
  • The support for the Catalan language was added to Plesk.
  • Phusion Passenger 5.0.30 is now supported.
  • The ability to generate a one-time URL for logging in was added to Plesk.
  • PHP 5.5 was updated to version 5.5.38.
  • PHP 5.6 was updated to version 5.6.24.
  • PHP 7.0 was updated to version 7.0.9.
  • Horde was updated to version 6.2.15.
  • Roundcube was updated to version 1.2.1.
  • The “Let’s Encrypt” extension is now included in the “typical” Plesk distribution.
  • The “Security Advisor” extension is now included in the “typical” Plesk distribution.
  • The “DrWeb” component was removed from the “typical” Plesk distribution.
  • The “Without DNS server” Plesk installation preset was removed.
  • The “WordPress Toolkit” component was added to the list of components available in Plesk Installer.
  • Deleting a customer account now results in all backups belonging to that account being deleted as well.
  • Plesk copyright information was moved to the “Tools&Settings” > “About Plesk” screen.
  • Plesk EULA was moved to the “Tools&Settings” > “About Plesk” screen.
  • Starting with Plesk Onyx, Plesk will no longer provide Virtuozzo for Windows templates.
  • The ability to integrate with the Customer and Business Manager was removed.
  • The “SSH terminal” feature was removed.
  • Web Presence Builder was rebranded in accordance with the Plesk brand.
  • Plesk backup performance was improved.
  • The ability to perform a direct upgrade to Plesk Onyx from Plesk 10.4 and earlier was removed.
  • The ability to restore backups created in Plesk 10.4 and earlier in Plesk Onyx was removed.
  • The ability to install Plesk on 32-bit OSes was removed.
  • Internet Explorer 10 and earlier are no longer supported.
  • In WordPress Toolkit, activating or updating multiple plugins or themes at once resulted in an error. (PPP-19320)
  • Plesk users could have been affected by the HTTPoxy vulnerability (CVE-2016-5385, CVE-2016-5386, CVE-2016-5387, CVE-2016-5388, CVE-2016-1000109, and CVE-2016-1000110). See KB article #129391 for more information. (PPP-24691, PPP-24825)
  • Customer passwords contained in Plesk backups created via a scheduled task and saved to the FTP repository were encrypted even if the “Use password protection” option was disabled. (PPP-24917)
  • OBAS failed to validate XML responses from Plesk nodes if ModSecurity was enabled and the “Atomic ModSecurity (subscription)” ruleset was in effect. (PPP-24743)
  • Trying to scan for WordPress installations stopped certain operations in Plesk from working properly. (PPP-24493)
  • Changing password for the system user of a suspended domain belonging to an active subscription made FTP and SSH access to the domain under that system user impossible. (PPP-21960)
  • Using WordPress Toolkit to update plugins installed on a WordPress installation resulted in an error if the plugin was not installed on all WordPress installations. (PPP-22657)

Linux

  • The “perl-apache-asp” component is no longer supported.
  • Plesk could not be installed on Debian 8 servers if the “Ruby support” component was selected for installation. (PPP-24954)
  • The SPF record included in the default Plesk DNS template contained a syntax error. (PPP-24787)
  • The ‘access_log.processed’ file located in the home directory of Plesk domains was not rotated. (PPP-24723)
  • Proxmox LXC was not detected as a VM environment. (PPP-25201)
  • The default PHP “open_basedir” value was missing from the configuration files. (PPP-24914)
  • Under specific conditions, the list of server components could become empty. (PPP-25135)
  • Trying to create a customer belonging to a reseller in Plesk resulted in the “The plan was not applied: Hosting performance settings management” error. (PPP-24525)

Windows

  • Microsoft SQL Server 2016 is now supported.
  • Microsoft SQL Server 2012 SP3 is now included in the Plesk for Windows distribution.
  • Web Deploy 3.6 is now included in the Plesk for Windows distribution.
  • BIND was updated to version 9.10.4-P2.
  • MySQL ODBC connector was updated to version 5.3.
  • MySQL used for the Plesk database was updated to version 5.5.50.
  • MySQL used for customer databases was updated to version 5.6.32.
  • Tomcat was updated to version 7.0.70.
  • Tomcat connector was updated to version 1.2.41.
  • ModSecurity was updated to version 2.9.1.
  • ModSecurity ruleset files were updated to version 2.2.9-30-g520a94b.
  • phpMyAdmin was updated to version 4.6.3.
  • AWStats was updated to version 7.5.
  • Web statistics calculation could fail if the log files contained lines longer than 4096 symbols. (PPP-24688)
  • Maximum bandwidth in service plan settings could not exceed 31 MB/s. (PPP-24276)
  • Vhost location could not be changed for domains whose IIS configuration files contained duplicate entries in the section. (PPP-25102)
  • Mobile Preview failed to display websites created in Web Presence Builder. (PPP-18938)

19 July 2016

Plesk Onyx 17.0.14

  • Users now can switch on SEO-safe redirect from HTTP to HTTPS for their websites in Plesk.
  • The “DNSSEC Support” Plesk extension was published.
  • The support for automatic DNSSEC key rollover was added to Plesk.
  • Error messages about failed DNSSEC key rollover attempts are written to the Plesk log.
  • Notifications informing users of manual actions that need to be taken are displayed in the Plesk interface.
  • The ability to secure webmail with an SSL/TLS certificate was added to Plesk.
  • PHP 5.5 was updated to version 5.5.37.
  • PHP 5.6 was updated to version 5.6.23.
  • PHP 7.0 was updated to version 7.0.8.
  • Upgrading from Plesk version 10.4.4 and earlier to Plesk Onyx is no longer supported.
  • The Docker service is now being monitored by Watchdog.
  • The default “document root” value could not be changed for websites hosted in Plesk. (PPP-24236)
  • Users could not change backup settings if their subscription did not include the permission to back up to the server storage. (PPP-19991)

Linux

  • The “Ruby Support” Plesk extension was published.
  • Plesk admins now can manage Ruby settings for hosted domains via CLI and XML-RPC.
  • The permissions enabling Plesk admins and resellers to manage Ruby availability were added to service plans and subscriptions.
  • Users can now manage Ruby settings for hosted domains in Plesk.
  • A message explaining how to log in to Plesk is displayed when logging in to a server with Plesk installed via SSH.
  • On CentOS 7, Debian 8, and Ubuntu 16 servers, the “Resource Controller” component can now be installed via Plesk Installer.
  • The ability to manage Cgroups limits for subscriptions was added to Plesk.
  • The ‘delv’ utility is now shipped with Plesk.
  • Files could not be attached to auto-reply messages for mail accounts if the name of the parent domain contained Cyrillic letters. (PPP-23938)

Windows

  • Microsoft SQL Server 2016 is now supported.
  • The support for remote SmarterMail servers was added to Plesk.
  • The data about Plesk extensions’ limits and permissions can now be included in Plesk backups.
  • MailEnable was updated to version 9.15.
  • Entries from the ModSecurity log were not displayed in Plesk Log Browser. (PPP-24277)
  • Passwords of mail users blocked due to the MailEnable security policy could not be changed in Plesk. (PPP-23645)
  • After upgrading from Plesk 11.0 or earlier to Plesk 12.5, if Microsoft DNS Server was used, users could no longer manage DNS settings. (PPP-24014)

20 June 2016

Plesk Onyx 17.0.13

  • The “Ruby support” Plesk extension was published.
  • The ability to scan for Ruby applications was added to the “Ruby support” Plesk extension.
  • The ability to configure proxying of domain requests to docker containers was added to Plesk.
  • Git extension data is now included in Plesk backups.
  • The ability to retrieve Plesk server’s OS name, version, architecture, as well as the type of virtualization being used (if any) was added to the Plesk SDK.
  • The support for “DS” type DNS records was added to Plesk.
  • Managing Git repositories for addon domains via the Git extension in Plesk could result in the “Error: Unable to find the repository with ID = 1” error. (PPP-23127)
  • A duplicated notification was displayed in Plesk when running a Docker image from the catalog via the Docker extension. (PPP-23150)
  • Trying to unset a public IP address via the Plesk XML API operator produced no effect. (PPP-23522)
  • The procedure for editing files using the Plesk built-in code editor was too complicated. (PPP-23401)
  • The subscription owner could not be changed if the password for a database user belonging to the subscription could not be decrypted. (PPP-23317)
  • An unhandled error was displayed during Plesk installation if the host ‘getcomposer.org’ could not be resolved. (PPP-23388)
  • When ‘quick installing’ certain applications in Plesk, the custom database prefix was not validated, which led to installation failures if the prefix started with a digit. (PPP-23257)

Linux

  • The support for nginx ALPN was added to Plesk.
  • The ability to run websites on nginx only (no Apache) was added to Plesk.
  • nginx was updated to version 1.11.1 (CVE-2016-4450)
  • After PHP was upgraded via Plesk Installer, the permissions and ownership information for the /var/lib/php/session directory were reset. (PPP-23093)
  • On Centos 7 x64 servers, running Plesk Installer resulted in all *.log files in the /tmp directory being removed. (PPP-23220)
  • On Centos 7 x64 servers, using the Site Preview feature resulted in a 403 error. (PPP-23087)
  • The “Refresh” button was missing from the Tools & Settings > Services Management screen in the Plesk interface. (PPP-23344)

Windows

  • ASP.NET Core 1.0 is now supported.
  • The support for remote SmarterMail servers was added to Plesk.
  • Fresh Plesk installations without either Microsoft DNS Server or BIND DNS Server installed could not be initialized. (PPP-23556)
  • After changing the IPv4 IP address for a subscription, the IP address change was not applied to additional FTP accounts created in Plesk. (PPP-22586)

24 May 2016

Plesk Onyx 17.0.12

  • If you used Plesk tools for working with Git (such as the Gitman extension), then upon upgrading to Plesk Onyx your existing repositories are automatically added to Git Manager, the new Plesk extension. This is true when you upgrade from older Plesk versions, for example, 12.5, and not true when you update to a newer Plesk Onyx preview version.
  • The Git Manager extension now allows you to create a repository without deploying its files.
  • The capability to view the log of commits was added to the Git Manager extension.
  • The Docker Manager extension now allows you to add multiple remote Docker nodes to Plesk and switch among them.
  • Action Log API was added to the Plesk SDK.
  • The ability to add custom web server configuration and run web server reconfiguration was added to the Plesk SDK.
  • The support for Hebrew language was added to Plesk.
  • The stability of backing up data to FTP was increased.
  • Obsolete options and functionality were removed from Plesk Installer.
  • It was impossible to login to Plesk if the license had expired and the Google Auth extension was switched on in Plesk. (PPP-22897)
  • The shell preferences of the system user were ignored on Git additional deploy actions. (PPP-22556)
  • The title of the web server’s default page in the browser was incorrect. (PPP-22785)

Linux

  • phpMyAdmin 4.6.0 is now supported.
  • It was impossible to install Docker on RHEL 7 (64-bit). (PPP-22053)
  • phpMyAdmin 4.6 caused the error “Class ‘PMA_Util’ not found”. (PPP-22515)
  • HTTP/2 was not enabled on clean Plesk installation. (PPP-22208)
  • Ruby component was not found in Plesk for Ubuntu-12.04 (PPP-22689)
  • On CentOS 6, SSH authorization failed under some conditions. (PPP-22364)
  • Websites created in WordPress were displayed incorrectly in the quick preview mode. (PPP-22719)
  • On some operating systems, Plesk’s full installation did not include Ruby interpreter and rbenv components. (PPP-22751)

Windows

  • The support for SmarterMail 15 was added to Plesk.
  • After the user disabled ASP.NET support on a subscription, the applicationHost.config file size increased due to unnecessary elements in the section. (PPP-22303)
  • It was possible to change the FTPS usage policy on a per IP basis, despite the fact that FTPS was enforced in Security Policy settings. (PPP-22452)
  • In PHP settings, by default the value of post_max_size was smaller than that of upload_max_filesize. (PPP-22435)
  • In some cases, the installation of the Let’s Encrypt extension failed with the error “The executable python.exe could not be run”. (PPP-22098)

19 April 2016

Plesk Onyx 17.0.11

  • The support for HTTP/2 was added to Plesk.
  • The ability to use Active List components was added to the Plesk SDK.
  • The ability to embed 3rd-party PHP libraries using Composer was added to the Plesk SDK.
  • The ability to use custom PHP namespaces was added to the Plesk SDK.
  • The ability to execute long tasks and display their progress in the Plesk GUI was added to the Plesk SDK.
  • The ability to use the Plesk GUI navigation tools was added to the Plesk SDK.
  • The ability to add custom content to Plesk forms was added to the Plesk SDK.
  • The “Docker Manager” Plesk extension was published. The extension is available here.
  • The “Git Manager” Plesk extension was published. The extension is available here.
  • The custom buttons functionality of the Plesk SDK was improved.
  • The stability of the Plesk backup process when backing up to FTP was improved.
  • Operations in the File Manager could result in an error if the Plesk interface was open in two or more browser tabs. (PPP-21812)
  • Users could not log in to WordPress using the “admin” user credentials, even if administrative access was granted to the user during installation. (PPP-22068)
  • Tab titles in WordPress Toolkit were not translated in the Korean locale. (PPP-21902)
  • The ability to suspend a domain via the Plesk API was missing, and the status of suspended domains was returned incorrectly when queried via an API call. (PPP-21948)
  • Users could not set specific limits when using the Plesk SDK. (PPP-22093)
  • An incorrect event was being generated when a subdomain was created via the Plesk API. (PPP-22160)

Linux

  • The ability to register services was added to the Plesk SDK.
  • Enabling the SPF spam protection on the server resulted in unclear delivery failure notifications when mail was rejected. (PPP-19877)
  • Enabling the greylisting spam protection on the server resulted in all mail from Office365 being deferred. (PPP-22018)
  • phpMyAdmin configuration storage could not be configured for remote MySQL servers. (PPP-21824)

Windows

  • The ability to execute binary tools with elevated privileges was added to the Plesk SDK.
  • The support for wildcard subdomains was added to Plesk (this feature is only available on Windows Server 2016 or later).
  • On Windows 2012 x64 servers, the creation of multi-volume backups failed if the customer data included one or more files of the size greater than the specified volume size. (PPP-21911)
  • Users could not create or upload Microsoft SQL Server dumps if the passwords of one or more database users contained the “;” symbol. (PPP-22161)
  • Users could not manage error documents for virtual directories whose physical path was mapped to the document root. (PPP-21343)
  • Plesk upgrade attempts failed if the Plesk Installer could not find the .msi file for one or more currently installed packages. (PPP-18418)
  • After removing and re-installing Horde via the Plesk interface, the Horde application pool was not re-created. (PPP-21036)

25 March 2016

Plesk Onyx 17.0.10

  • CGI support, Perl support, and Python support are disabled in all Plesk service plans by default.
  • A connection string for Docker is now added to the psa.conf file allowing Plesk to communicate with the Docker service.
  • It is possible to use Docker installed on a remote machine (learn more).
  • Git management permission can be set in service plans (learn more).
  • Additional deployment actions can be used in Git (learn more).
  • Administrator can start, stop, or restart Docker from the Services Management page (learn more).
  • A number of improvements for managing Docker images and containers have been introduced (learn more).
  • Administrator can perform a number of new operations on a Docker container, in particular, recreate, commit, download snapshot, or remove a container (learn more).
  • Auto-reply messages were not sent when SpamAssassin detected spam messages. (PPP-20562)
  • XML API request for generating self-signed SSL certificate with wildcard resulted with an error. (PPP-20781)
  • After saving a DNS record of the SRV type its value was displayed incorrectly. (PPP-21078)
  • A server backup could not be restored if additional services were configured for service plans. (PPP-20711)
  • Creation of a reseller’s subscription failed if an administrator added PHP directives to the reseller’s service plan. (PPP-20205)
  • An invalid response was received for an XML API request getting aliases of a non-existing domain. (PPP-21209)
  • A response for an XML API request getting information about webspaces contained no information about webspaces of reseller’s customers. (PPP-19986)
  • In a response for an XML API request getting information about webspaces, the real_size node did not include size of additional domains. (PPP-21329)
  • In case of many custom directories in the /var/lib/psa/dumps directory, the consuming disk space in /usr/local/psa/PMM/logs was growing every day after runnung the daily maintenance script. (PPP-19833)
  • In some cases the default Plesk page could not be opened. (PPP-17514)
  • Service plan without hosting could not be created via XML API. (PPP-21334)
  • If RSS feed was enabled in Plesk without specifying URL, Plesk pages in Power User view could not be opened. (PPP-21267)
  • In some cases backup was blocked due to incorrect free disk space calculation. (PPP-21344, PPP-20730)
  • In some cases subdomain name validation failed because the name of the subdomain was overlapped by DNS zone of the domain. (PPP-21071)
  • Database user password could not be changed if a remote MySQL 5.7 database server was used. (PPP-20792)
  • A subdomain could not be created if a DNS template contained two records with the same host and record type. (PPP-21332)
  • When Postfix mail server was used, emails could not be forwarded from dedicated IP. (PPP-21360)
  • It was impossible to install new license after Plesk had removed a terminated license key. (PPP-20837)
  • If full server backup completed with warning, the Backup Manager screen displayed two items. (PPP-18070)

Linux

  • CentOS 5, Red Hat Enterprise Linux 5, and CloudLinux 5 are no longer supported.
  • nginx was updated to version 1.9.12.
  • The list of patterns for black/white list mail addresses could not be retrieved via the grey_listing command line utility. (PPP-21006)
  • Dr.Web keys were not updated during the daily maintenance task run. (PPP-20585)
  • Wrong PHP version was displayed for a web page if PHP was run as FPM application served by nginx. (PPP-20336)
  • Synchronizing DNS zones information using the “plesk repair –dns” command failed when the /var/named/chroot/etc/named.conf file was absent. (PPP-20965)
  • On CentOS 7x64 Watchdog reported that Apache 2.4 was out of date. (PPP-17755)
  • MySQL database dump could not be imported if a database contained a trigger. (PPP-20972)
  • The dist-upgrade from Debian 7 x64 to Debian 8 failed. (PPP-19430)
  • When a subscription was backed up on Plesk with nginx and then restored to Plesk without nginx, the restoration failed. (PPP-21090)
  • Using short mail account names became unavailable after upgrade from Plesk 12.0 to Plesk 12.5. (PPP-20913)
  • In some cases, the ‘Internal error: Permission denied’ error occured after Plesk cloning in Virtual Environment. (PPP-18646)
  • When Apache graceful restart was enabled in Plesk, a domain could not be reconfigured. (PPP-19527)
  • Java Applications were available in Plesk Web Admin edition though it does not include Developer Pack. (PPP-21075)
  • Plesk configuration was broken if Atomic ModSecurity installation failed. (PPP-18732)
  • If MySQL was restarted during full server backup, the backup failed with multiple warnings. (PPP-20248)
  • Rewrite rules from the .htaccess file do not work when PHP support is enabled with PHP-FPM handler. (PPP-19965)
  • The psa-firewall service failed to load after server restart.(PPP-20899)
  • If Plesk was installed on Amazon AWS or any other VM behind NAT with set public IP, FTP connection did not work. (PPP-17545)
  • A backup could not be restored if a custom password was specified in the backup security settings. (PPP-21372)
  • Extracting files from an archive via File Manager did not replace already existing files. (PPP-21450)
  • Plesk mail user could not switch on mail forwarding. (PPP-21481)
  • In some cases Plesk Migrator did not work because it failed to connect to the source server via SSH. (PPP-18722)
  • A backup created by the pleskbackup utility with the –backup-password option could not be decrypted. (PPP-21484)
  • When trying to update WordPress, the /httpdocs directory was removed with all the data. (PPP-20510)
  • Free memory check before Plesk upgrade worked incorrectly. (PPP-17281)
  • IP address of the domain hosting was changed to outgoing mail IP address after server restoration from a backup. (PPP-20738)

Windows

  • Shared SSL is no longer supported.
  • Microsoft ASP.NET 1.1 version is no longer supported.
  • Backup download is now performed without using temporary files.
  • SmarterMail versions 6.x, 7.x, 8.x, 9.x are no longer supported.
  • If a backup to FTP is performed with an error, all temporary files are removed.
  • Mailbox quota could not be updated via XML API for a domain using MailEnable mail server. (PPP-21161)
  • Installation of WordPress failed on a disabled web site or subscription. (PPP-20840)
  • Updating administrator’s email failed with an error. (PPP-21261)
  • If and APS package with colon in name was uploaded to the server, the server backup was marked as invalid and could not be restored. (PPP-21145)
  • The value of the max_input_time parameter in PHP settings could not be customized and was always equal to the value from the server’s php.ini file. (PPP-20214)
  • WordPress could not be installed for the domain with PHP version 5.3 under a subscription with PHP version 5.2.17.(PPP-19624)
  • If SmarterMail was used as a mail server, the mailing list could not be created. (PPP-20204)
  • Free disk space on destination location was not verified before changing virtual hosts directory. (PPP-21111)

24 February 2016

Plesk Onyx 17.0.9

  • Users now can create event handlers triggering on customers changing their locale in Plesk.
  • Users now can install Ruby and a number of gems from the Plesk interface. Multiple Ruby versions are supported.
  • Users can now deploy websites by pulling the content from a remote Git repository from the Plesk interface.
  • The Docker service has been added to the list of services monitored by Watchdog.
  • A number of improvements for the Git support feature have been introduced.
  • Resellers could see sessions of customers owned by the administrator and other resellers in the “Active Plesk Sessions” menu. (PPP-20829)
  • Using the plesk bin locales utility resulted in erroneous output. (PPP-20378)
  • Incorrect event handlers input parameters were being passed when service plans were created or edited. (PPP-20064)
  • Resellers could not resume subscriptions they manually suspended. (PPP-19494)

Linux

  • Some non-allowed instance types for Plesk 12.5 on Ubuntu 14.04 x64 AWS images were listed as allowed. (PPP-17479)
  • The default WordPress Fail2ban jail could be circumvented by adding certain symbols to the request URL. (PPP-20758)
  • On CentOS 7 x64 servers, trying to reinstall Plesk updates after switching MariaDB to Percona 5.6 resulted in an error. (PPP-20801)
  • Certain Plesk operations could fail if the maximum number of open file descriptors for the psaadm users was too low. (PPP-20798)
  • Custom SpamAssassin options configured in the /etc/default/spamassassin file were ignored. (PPP-20827)
  • On CentOS 7 x64 servers, changing the document root directory for a subdomain resulted in the creation of a /var directory under domain root. (PPP-20500)
  • Users could delete and edit tasks scheduled under the root user even if the root.crontab.lock file was created. (PPP-20625)
  • If the “FPM served by nginx” PHP habdler was set as the default in a service plan, syncing subscriptions with that plan resulted in the PHP handler being changed to “FPM served by nginx” even if the subscription settings allowed selecting the PHP handler. (PPP-20589)
  • Sending API requests to Plesk resulted in the timestamp of the psa.conf file being changed. (PPP-20201)
  • Applying firewall rule changes resulted in the temporary rules added by Fail2ban being dropped. (PPP-20258)
  • On CloudLinux 7 x64 servers, browsing Tools & Settings > Server Management > Server Information resulted in an error if cagefs was enabled. (PPP-18287)
  • Trying to start the SpamAssassun service resulted in an error if IPv6 support was disabled on the server. (PPP-18292)
  • Trying to restart the Fail2ban service resulted in it hanging if the number of domains on the server was large. (PPP-19355)
  • On CentOS 7 x64 servers, the MariaDB 10.0 service was not automatically started by Watchdog if it crashed or was stopped. (PPP-17853)
  • The psa-horde.log file was getting truncated with every failed login attempt. (PPP-19878)
  • Under specific circumstances, Fail2ban could block the Plesk server IP resulting in a 502 error. (PPP-17542)
  • On Ubuntu 14.04 x64 servers with Plesk deployed from the Amazon Web Services image, the socket for the MySQL service was not created after server restart. (PPP-17436)

Windows

  • ionCube version was updated to 5.0.21.
  • Trying to upload a file greater than 2 GB in size resulted in a misleading progress indicator. (PPP-19317)
  • Scheduled tasks were not included in subscription backups. (PPP-20293)

01 February 2016

Plesk Onyx 17.0.7

  • Users can view arbitrary logs in the Log Browser.
  • Plesk allows management of Git repositories and automated deployment of web sites from such repositories to a target public directory.
  • MySQL database users now have permissions to create a procedure.
  • The “Change Hosting Settings” screen for a subscription was eliminated as its features are available on other screens.
  • It was not possible to use relative URL as a redirect in the automatic login form. (PPP-20198)
  • The information about outgoing email messages limits was returned in an XML API response for getting a service plan, even if these limits were switched off. (PPP-20055)
  • If an additional administrator’s profile was updated via XML API or via the user interface, the “Allow multiple sessions under this account” setting became switched on even if it has been switched off before. (PPP-20022, PPP-20016)
  • A DNS record of the SRV type with a combined protocol could not be added. (PPP-19980)
  • If the interface language was changed in an additional administrator’s profile, this change did not work after re-login of the additional administrator. (PPP-19973)
  • An XML API response for getting DNS records returned all text DNS records in lowercase, which was an issue in case of case-sensitive records. (PPP-19907)
  • Plesk generated wrong login of a WordPress administrator after WordPress installation so that the administrator could not neither login to WordPress from Plesk nor change the password. (PPP-19579)
  • If a self-signed SSL certificate was created for a subscription, the subscription became locked. (PPP-19546)
  • The tabs of the “Mail Server Settings” screen were not available on a mobile device or in a browser window of a small size. (PPP-19504)
  • A multivolume backup created in an FTP storage and downloaded from it could not be uploaded again via the Plesk interface. (PPP-18381)

Linux

  • An XML API response for getting a service plan with additional Apache or nginx directives was invalid. (PPP-19998)
  • A running nginx web server failed to re-start if it was uninstalled and then installed again. (PPP-19462)
  • A password for web statistics of an additional domain or a subdomain was not changed after a password for the subscription FTP account was changed. (PPP-19529)

Windows

  • The “Idle timeout action” parameter in the “Dedicated IIS application pool” settings of a subscription was not updated after changing the service plan. (PPP-19724)
  • If a server backup was downloaded with a password, and then restored without password, the restore was too slow. (PPP-19935)
  • If a server backup was downloaded with a plain password, and then restored on another server without password, the password for a mailbox user was regenerated, so that the user could not access the mailbox with an old password. (PPP-19880)
  • WordPress management in Plesk worked incorrectly if the extension.dir parameter in the php.ini file contained a path ended with a slash. (PPP-19673)
  • After restore of an incremental backup of a subscription with an additional domain, the custom mail directories of the additional domain’s mailboxes were not restored. (PPP-19340)
  • If an Microsoft SQL Server database dump was created in Microsoft SQL Server Management Studio with multiple restore points and then imported to Plesk, only the data related to the first restore point was restored. (PPP-19133)

28 December 2015

Plesk Onyx 17.0.6

  • The names of files mentioned in the Message part of logs monitored in the Log Browser are now highlighted and clickable, and the corresponding files can be opened from the Log Browser interface.
  • Incremental backup for mail content is now supported.
  • Miva e-commerce applications are no longer supported.
  • Actual Plesk server IP address was displayed in the System Overview block in Power User view instead of the public IP address. (PPP-19442)
  • Trying to view Plesk video tutorials from the Plesk interface resulted in a malformed page if Flash was not enabled on the user’s computer. (PPP-19334)
  • Sending an XML API request using the operator specifying multiple WordPress instances at once resulted in receiving a confusing response packet. (PPP-19071)

Linux

  • Docker CLI and daemon are available as Plesk components on CentOS/Red Hat Enterprise Linux/CloudLinux 7, Debian 8, and Ubuntu 14.04 (x64 only). They can be installed via the Plesk Installer.
  • nginx was updated to version 1.9.9.
  • Git support was added in Plesk for Linux. The corresponding component can be installed via the Plesk Installer.
  • On Debian 7 x64 servers, distupgrade to Debian 8 failed if the server was previously distupgraded from Debian 6. (PPP-19384)
  • On CentOS 7 x64 servers with Dovecot and Postfix installed, enabling the Outgoing Antispam feature resulted in confusing error messages being written to the mail log. (PPP-19169)
  • Users could not update hosting settings via API-RPC if the mod_perl module was not installed. (PPP-19141)
  • On CentOS 6 x64 servers, Dovecot installed as a Plesk component could not be started if a different version of Dovecot was installed on the server prior to the Plesk installation. (PPP-18620)

Windows

  • Git support was added in Plesk for Windows. The corresponding component can be installed via the Plesk Installer.
  • Under very specific circumstances, MicrosoftSQL Server databases could not be restored from Plesk backups. (PPP-19342)
  • The Host parameter in the Connection Information menu was missing the backslash character. (PPP-19212)
  • Clicking the “Learn about secure hosting setting” in the Plesk interface resulted in the Advanced Administration Guide for Linux being opened. (PPP-18504)
  • Upgrade from Plesk 12.0 to Plesk 12.5 hung if there was an unresponsive process on the server at the time the upgrade was performed. (PPP-18423)

Your Comments