Release Notes for Plesk 12.5 for Linux Systems

What's New Change Log Software Requirements Upgrade Notes Contact Us


  1. Plesk 12.5.30 Update 10
  2. Plesk 12.5.30 Update 9
  3. Plesk 12.5.30 Update 8
  4. Plesk 12.5.30 Update 7
  5. Plesk 12.5.30 Update 6
  6. Plesk 12.5.30 Update 5
  7. Plesk 12.5.30 Update 4
  8. Plesk 12.5.30 Update 3
  9. Plesk 12.5.30 Update 2
  10. Plesk 12.5.30 Update 1
  11. Plesk 12.5.30

Change Log


[+] new feature

[*] functionality improved

[-] issue resolved

12.5.30 Update 10 [9 November 2015]

  1. [*] A number of fixes to non-English Plesk locales.

  2. [-] On CentOS 6 and RHEL 6 servers, Apache failed to start after server restart if the httpd service was being monitored by Watchdog. (PPPM-3457)

  3. [-] An unnecessary warning was displayed when users backed up domains with hosting type set to "forwarding" or "no web hosting". (PPP-18396)

12.5.30 Update 9 [2 November 2015]

  1. [*] Plesk PCI compliance resolver was updated and improved.

  2. [*] Helper scripts used in Plesk distupgrade were moved from /usr/lib/plesk-9.0 to /usr/local/psa/bin.

  3. [-] Plesk configuration defined on Partner Central could not be applied to Plesk servers. (PPP-18302)

  4. [-] Disk usage data retrieved via Plesk API XML did not include the disk space taken up by mailboxes belonging to addon domains. (PPP-18266)

  5. [-] The "Scheduled backup" comment was always displayed in English, even to users logged in under a non-English locale. (PPP-18176)

  6. [-] Trying to retrieve data about a webspace via XML API without specifying the webspace name resulted in an unclear error message. (PPP-18072)

  7. [-] Upgrade to Plesk 12.5 failed if a database contained two users with identical names written in different combinations of upper and lower case letters. (PPP-18219)

  8. [-] After upgrading to Plesk 12.5, confusing error messages were written to the PHP-FPM error log if no domain used the PHP-FPM handler. (PPP-18089)

  9. [-] On CentOS 7 x64 servers, installation of Plesk 12.5 failed if Fail2ban from EPEL had already been installed. (PPP-17535)

12.5.30 Update 8 [26 October 2015]

  1. [*] phpMyAdmin was updated to version 4.5.

  2. [-] Creating domains and subdomains could fail if the "Use serial number format recommended by IETF and RIPE" option was enabled on a Plesk server and a large number of subdomains was created within a short period of time. Migration from servers with a large number of subdomains could also fail. (PPP-18158)

  3. [-] The default values were always used for the max_execution_time and max_input_time PHP directives if mod_php was used. (PPP-18133)

  4. [-] Under specific circumstances, all Plesk backups were being created invalid. (PPP-18097)

  5. [-] Under specific circumstances, trying to see the list of databases for a domain resulted in the "Error: Call to a member function getApplicationContext() on null" error message. (PPP-18048)

  6. [-] Plesk backups failed if the file /usr/local/psa/admin/bin/backup_restore_helper was tampered with. (PPP-18034)

  7. [-] On CentOS 7 x64 servers, trying to upgrade from Plesk 12.0 to Plesk 12.5 resulted in an error if an IP address on the server was assigned a peer before Plesk 12.0 was installed. (PPP-18067)

  8. [-] On Debian 8 and Ubuntu 14.04 servers, ionCube loader was not enabled for the system PHP-FPM handler. (PPP-18049)

  9. [-] On CentOS 6 x86 servers, the Typo3 CMS could not be installed because the version of PCRE shipped with the Plesk PHP was outdated. (PPP-18022)

  10. [-] The '/etc/cron.hourly/plesk-php-cleanuper' cron job sent an email with confusing error messages to the administrator's email address every hour. (PPP-17941)

12.5.30 Update 7 [19 October 2015]

  1. [*] The ionCube loader was upgraded to version 5.0.

  2. [*] Plesk showed both public and private IP addresses, which could confuse administrators willing to select an IP address for use by subscriptions and resellers' IP pools. Now administrators can hide private IP addresses from Plesk by modifying the panel.ini file. To do so, they should add the [ip] section and list addresses separating them with a whitespace and a comma. For example:

    blacklist=", 2002:5bcc:18fd:c:f482:d057:9ccf:993D"

    After they finish with editing the panel.ini file, they should go to Tools & Settings > IP Addresses, and click Reread IP.

  3. [-] On servers running CentOS, Red Hat Enterprise Linux, and CloudLinux versions 5 or 6, upgrading to Plesk 12.5 led to the mod_rpaf Apache module getting disabled. (PPP-18044)

  4. [-] IP addresses registered in Plesk were not added to the Fail2ban whitelist. (PPP-18023)

  5. [-] Full backups were being created instead of incremental ones. (PPP-18003)

  6. [-] On CentOS 7 x64 servers, after installing MariaDB version 10 or 10.1 the MySQL component was marked as “not installed” in the Plesk Installer. (PPP-18000)

  7. [-] The Plesk configuration troubleshooter incorrectly reported an inconsistency if an application was installed via Plesk on a subscription with the same id in the Plesk database as a reseller subscription. (PPP-17933)

  8. [-] When changing the password for a mail account in Plesk via the Plesk XML API, sending the new password as CDATA resulted in the password being changed, but the user being unable to log in. (PPP-17929)

12.5.30 Update 6 [12 October 2015]

  1. [-] Attempts to use the "Check Configuration" function of the "Webserver Configurations Troubleshooter" extension resulted in a PHP error. (PPP-17869)

  2. [-] Switching a subscription from a hosting plan with no mail service to one with a mail service, or vice versa, did not result in the mail service for the subscription getting enabled or disabled. (PPP-17833)

  3. [-] On CentOS 7 x64 servers, the Watchdog service failed to start on server restart. (PPP-17807)

  4. [-] Plesk resellers could see the list of all customer accounts on the server, including those belonging to the administrator and other resellers. (PPP-17795)

  5. [-] On CentOS 6 x86 servers, custom PHP extensions could be built with the wrong phpize. (PPP-17774)

  6. [-] On CentOS 7 x64 servers, after installing MariaDB version 10 users were unable to log in to Plesk due to the sw-cp-server service failing to start. (PPP-17732)

  7. [-] Users could not create Unity mobile sites, even if a Unity One (Monthly Lease) unlimited domains license was installed on the server. (PPP-17708)

  8. [-] After upgrading to Plesk 12.5, opening the list of PHP extensions for a PHP handler resulted in an error if there was a custom extension with a white space character in the name. (PPP-17696)

12.5.30 Update 5 [5 October 2015]

  1. [-] The "ip > get" XML API request failed if the credentials of an additional administrator account were used for authentication. (PPP-17717)

  2. [-] Plesk extensions displayed in Customer Panel were being reloaded every five seconds when there was a long-running task active in background. (PPP-17711)

  3. [-] Users can now see the contents of rotated Fail2ban logs in "Tools & Settings" > "IP Address Banning (Fail2Ban)" > "Logs". (PPP-17672)

  4. [-] The effects of the "DNS zone management" permission were applied inconsistently if the permission was granted to one subscription belonging to a specific customer account, but was not granted to a different subscription belonging to the same account. (PPP-17683)

  5. [-] In Power User view, additional administrator accounts could see and manage all subscriptions, even if the account was limited to seeing and managing only specific subscriptions. (PPP-17679)

  6. [-] Joomla was not functioning if it was installed on a website with the PHP handler set to PHP-FPM. (PPP-17678)

  7. [-] On servers running Ubuntu 14 x64, if Plesk was installed from the ISO image, the MySQL service failed to start on server restart. (PPP-17624)

12.5.30 Update 4 [28 September 2015]

  1. [+] Roundcube webmail client installed on Linux servers was updated to version 1.1.3.

  2. [-] Email users could not change their mail account settings such as password, forwarding, and auto-reply. (PPP-17671 )

  3. [-] On CloudLinux 7x64, customers could not select FastCGI handlers for their websites, if they were not granted the permission "Setup of potentially insecure web scripting options that override provider's policy". (PPP-17643)

  4. [-] When the PHP version was changed in Power User View in Tools & Settings > Custom View Settings > PHP Settings, this change sometimes was not saved. (PPP-17595)

  5. [-] Applications that run on Phusion Passenger (RoR, Rack, Django) did not work due to variables missing in the locations.ini file. (PPP-17589)

  6. [-] Duplicated items in the PHP handlers menu were displayed if the PHP handlers installed on the operating system had the same versions as in Plesk.

  7. [-] If ModSecurity was enabled with the basic rule set, and a customer having a subscription with many domains logged in to Plesk, Apache restarted many times. (PPP-17563)

  8. [-] If a PHP-FPM handler was enabled on a domain, the PHP-FPM service did not start after the server restart. (PPP-17561)

  9. [-] In some cases, migration of a domain with SSL certificate installed could lead to a fatal PHP error. (PPP-17557)

  10. [-] Plesk could not be started after execution of the pci-compilance-resolver tool. (PPP-17367)

12.5.30 Update 3 [21 September 2015]

  1. [*] phpMyAdmin was updated to

  2. [-] Domains on which applications were installed could not be migrated from Plesk 8.6 and 9.5 to Plesk 12.5 if a domain with an identical name already existed on the destination server. (PPP-17571)

  3. [-] Resellers converted from customer accounts were suspended if the number of domains they hosted exceeded the limit set for the customer account and the overuse policy was set to "not allowed". (PPP-17549)

  4. [-] Manual WordPress installations could not be detached from the WordPress Toolkit. (PPP-17531)

  5. [-] Users could not remove mailboxes belonging to subscriptions migrated from Plesk 12.0 if a mail alias had been created for them prior to the migration. (PPP-17523)

  6. [-] The "Hosting Settings Updated" event handler was not triggered on PHP handler or PHP version change. (PPP-17515)

  7. [-] Users could not restore the data of applications that belonged to different domains and subdomains, but were installed in directories with identical names. (PPP-17504)

  8. [-] Editing the properties of a reseller account when there were no shared IP addresses in Plesk resulted in a PHP warning message. (PPP-17496)

12.5.30 Update 2 [14 September 2015]

  1. [+] The MagicSpam Plesk extension can now be installed via the Plesk Installer.

  2. [*] Plesk administrators can now disable PHP handlers even if they are in use.

  3. [-] Domains without hosting could not be removed from Plesk. (PPP-17369)

  4. [-] Changing the SSL certificate for webmail did not take effect unless the httpdmng --reconfigure-all command was run afterwards. (PPP-17364)

  5. [-] Administrator could not see a form with WordPress settings when clicking Change Settings for an installed WordPress instance. The log displayed an exception. (PPP-17463)

  6. [-] When the default system PHP version running as FastCGI was set for a subscription on Debian 8.0, a PHP session could not be saved for a PHP script. (PPP-17456)

  7. [-] If an administrator installed an old version of the Plesk Mobile Center extension, and then tried to re-log in to Plesk, the error message was displayed. (PPP-17413)

  8. [-] Administrators could not change file permissions for a file via the File manager on Linux. (PPP-17389)

  9. [-] If a custom PHP handler name was set via the command-line interface, it was not displayed in the list of PHP handlers in PHP settings of a subscription. (PPP-17380)

  10. [-] In some cases, the PHP settings page displayed a PHP catchable fatal error. (PPP-17371)

  11. [-] On Plesk for Linux servers, the sendmail utility produced unneeded debug output every time it ran. (PPP-17370)

  12. [-] After the DNS zone was enabled for a subdomain on a Plesk for Linux server, the zone was not loaded until BIND was restarted. (PPP-17348)

12.5.30 Update 1 [8 September 2015]

  1. [+] A default Fail2ban jail (plesk-wordpress) and a filter were added for protection of WordPress installations from brute force attacks. The filter and the jail are switched off by default. You can switch them on in Tools & Settings > IP Address Banning (Fail2Ban).

  2. [-] Customers could not back up a subscription with a domain for which web hosting was not configured. The following error was recorded in log files: Can't use string ("") as a HASH ref while "strict refs" in use. (PPP-17356)

  3. [-] If WHMCS was configured using a reseller account, the reseller's customers could not log in to Plesk from the WHMCS interface. They encountered the "Permission Denied" error. (PPP-17341)

  4. [-] After transferring a subscription to another owner, the email address in domains' SOA records remained unchanged. (PPP-17340)

  5. [-] Administrators could not hide commercial applications from Plesk by editing the panel.ini configuration file. (PPP-17322)

  6. [-] Plesk could not start after upgrade to version 12.5 if the Logjam patch from the KB article #125741 ( was applied previously. (PPP-17296)

  7. [-] Administrators encountered the following error while trying to back up data by means of the pleskbackup command-line utility: "Runtime error: Not a HASH reference at /opt/psa/PMM/agents/PleskX/ line 65." However, backups were created. (PPP-17292)

  8. [-] In some cases, the left navigation menu could not be loaded after Plesk was switched to the Power User view. (PPP-17272)

  9. [-] It could take too much time to apply changes to PHP settings at the server level. (PPP-17270)

  10. [-] PHP FPM services were incorrectly named. (PPP-17269)

  11. [-] Running the command /usr/local/psa/bin/migrate --list-subscriptions with an incorrect username or password resulted in an error report. (PPP-17268)

  12. [-] Changes to a subdomain's DNS zone were not applied immediately. (PPP-17267)

  13. [-] The self-repair utility could not resolve database inconsistencies when IP addresses were accidentally removed from the database. (PPP-17266)

  14. [-] PHP processes launched by Plesk, such as upgrade steps and daily maintenance actions, could consume more memory than it was defined in php.ini. (PPP-17264)

  15. [-] Administrators could not restore data from backups if they contained subscriptions without information about IP addresses. (PPP-17260)

  16. [-] Administrators could see numerous warning messages in Backup Manager. (PPP-17259)

  17. [-] There was no separator before the "Remove"link in toolbar in Home > Domains > Mail. (PPP-17258)

  18. [-] Users of Internet Explorer 11 could see an unnecessary element '_' near the status of PHP handler in Tools & Settings > PHP Settings. (PPP-17257)

  19. [-] A notice about the MailMan requiring localhost in mail server's white list was added to Plesk. (PPP-17255)

  20. [-] File sharing settings could not be restored from backups. (PPP-17254)

  21. [-] Plesk did not switch to the proper document root directory when users switched between subdomains. (PPP-17253)

  22. [-] The Statistics tab displayed incorrect percentage of disk and traffic overuse. (PPP-17252)

  23. [-] Users of Internet Explorer 11 could not open files in HTML Editor. (PPP-17251)

  24. [-] Plesk incorrectly formed HTTP requests to check PHP requirements of installed web applications on IDN sites. (PPP-17248)

  25. [-] When users attempted to create database users, wrong database server was suggested by default. (PPP-17247)

  26. [-] After upgrade from older Plesk versions, database inconsistency occurred that broke the page Tools & settings > Services Management. (PPP-17246)

  27. [-] Auto-reply end date could not be set via the XML-API. (PPP-17245)

  28. [-] On CentOS 7, users could not select the paid ModSecurity subscription rule set by Atomic. (PPP-16936)

12.5.30 [31 August 2015]

  1. [+] Users can improve the performance of PHP applications by switching on the PHP accelerator module in the website's PHP settings. By default, the APC module is activated for PHP versions earlier than 5.5, xcache for PHP 5.4.x, and Zend OPcache for PHP 5.5 or later.

  2. [+] FastCGI Process Manager (FPM) for PHP versions 5.4, 5.5, and 5.6 is now shipped with Plesk.

  3. [+] Administrators can configure the global settings of PHP handlers in Tools & Settings > PHP Settings, and select which PHP handlers should be available on the server.

  4. [+] Administrators and resellers can define whether their customers will be able to select PHP versions and PHP handlers for their sites. The corresponding permission is available in service plans and subscription settings. It can be managed from the GUI, as well as by means of command-line tools and XML-API requests. The "Manage PHP version" permission does not depend on the "Hosting settings management" permission.

  5. [+] Users can configure the PHP handlers and switch PHP support on or off in Websites & Domains > PHP Settings. They can also view the default settings for the selected PHP handlers. Administrators and resellers can view the default settings of PHP handlers, select PHP handlers, and switch PHP support on or off while configuring service plans (in Service Plans > plan name > PHP Settings tab).

  6. [+] The ability to manage PHP handlers via API and CLI was added.

  7. [+] Plesk users can select FPM as the PHP handler for their domains.

  8. [+] The PHP handler for websites using nginx+PHP-FPM is automatically switched to the most suitable one after nginx is disabled.

  9. [+] Support for the Composer PHP dependency manager was added.

  10. [+] Administrators can update the PHP version provided with Plesk to the next minor version via the standard "apt" or "yum" packaging tool.

  11. [+] The ability to manage PHP modules independently for each PHP handler was added.

  12. [+] Users can access reports on PHP settings for websites (phpinfo output) from Websites & Domains tab > PHP Settings.

  13. [+] Plesk is now shipped with PHP 5.2, 5.3, 5.4, and 5.5, and installing PHP 5.6 using the Plesk Installer is now supported

  14. [+] Users can create and download dumps of their databases from Plesk. (PPP-10914)

  15. [+] Users can upload dumps of their databases to the server and restore data from them by means of Plesk.

  16. [+] Users can now manage permissions of database users.

  17. [+] Users can specify database user roles while editing MySQL database users.

  18. [+] Users can use Plesk for checking and repairing MySQL databases.

  19. [+] A new command-line tool was added to enable administrators to check and repair Plesk's database. The tool can be executed by issuing the command plesk repair --check-db.

  20. [+] Users can move databases among their subscriptions, and administrators can move databases among all subscriptions in Plesk.

  21. [+] The ability to enable direct access to phpMyAdmin was added.

  22. [+] Links for managing databases were added to Plesk navigation areas.

  23. [+] Plesk supports MariaDB 10.

  24. [+] Plesk can count disk space occupied by remote databases.

  25. [+] For each of their databases, users can now specify the site that uses a database, and they can see the names of such sites directly in the list of databases.

  26. [+] Odin branding was applied to the Plesk interface.

  27. [+] New user interface theme and fully responsive design.

  28. [+] Plesk interface no longer uses frames. Now administrators and resellers can share direct links to Plesk screens with other authorized users, and bookmark their favorite Plesk pages in the browser.

  29. [+] New left navigation menu in the Customer Panel.

  30. [+] The ability to disable logging in to Plesk using the system user 'root' credentials was added.

  31. [+] The ability to log in to Plesk automatically from external resources was implemented.

  32. [+] Plesk interface is now available in the Indonesian language.

  33. [+] On CentOS 7 and Ubuntu 14 with Apache 2.4 or later, administrators can select multi-processing modules (MPMs) for Apache in Tools & Settings > Apache Web Server.

  34. [+] The support for mod_passenger was added to nginx.

  35. [+] Administrators can use the command plesk repair installation to repair Plesk configuration after upgrade.

  36. [+] Administrators can use the plesk repair tool to resolve various issues at a domain level. For example plesk repair all will run all check and repair operations for the domain Running plesk repair fs will run all file system check and repair operations for that domain.

  37. [+] Administrators can use the plesk repair mail command to resolve various issues with mail services at a domain or mailbox level.

  38. [+] Administrators can use the plesk repair tool to resolve inconsistencies between Plesk and MySQL or Microsoft SQL Server databases: restore databases, database users, and database users' credentials.

  39. [+] Administrators can use the plesk repair tool to restore web server configuration files:

  40. [+] Administrators can now resolve inconsistencies between the DNS server configuration and DNS records in the Plesk database. They can do it by means of the command plesk repair dns (on Linux) and <Plesk installation directory>\bin\repair.exe --reconfigure-dns (on Windows).

  41. [+] Administrators can now check whether database servers registered in Plesk are accessible over the network. They can do it by means of the commands <Plesk installation directory>/bin/repair --check-mysql and <Plesk installation directory>/bin/repair --check-mssql (on Windows).

  42. [*] Users can see security status of all WordPress instances in the list of instances in WordPress Toolkit. Clicking "Scan" while no instances are selected will recheck the security status of all instances in the list.

  43. [*] Users can select WordPress instances where plugins or themes should be installed if installing from the Plugins or the Themes tab in WordPress Toolkit.

  44. [+] Quick installation of WordPress now automatically sets the locale to that configured in Plesk user's settings.

  45. [+] Users can access redesigned Log Browser and see web server logs updated in real-time (similar to tail –f command). In Log Browser, date and string filters are available, and they work in real-time mode as well. Users can see multiple combined logs on one screen at once and choose which logs should be displayed.

  46. [+] The support for incremental backups was introduced. Users and administrators can create, download, upload, and remove incremental backups.

  47. [+] Users can perform operations on incremental backups kept at an FTP storage.

  48. [+] Now administrators can set up a special password for protecting sensitive information (such as user passwords, ODBC connections, and so on) contained in backups. This enables restoring backups on a different Plesk server with sensitive information intact if the password is specified during the restoration.

  49. [+] Administrators can adjust global settings for scheduled backups via the XML-API.

  50. [+] Administrators can view and manage the list of Plesk interface languages by using the new locales command-line tool.

  51. [+] Administrators can retrieve information about existing mail accounts and their aliases by using the command-line calls mail --list and mail --info.

  52. [+] Administrators can manage SSL cyphers and protocols for all services by means of the server_pref command-line tool. For example: server_pref --update -ssl-protocols 'TLSv1 TLSv1.1 TLSv1.2' -ssl-ciphers 'HIGH:!aNULL:!MD5'.

  53. [+] Users can enable and disable the Fail2Ban service by using the ip_ban command-line utility.

  54. [+] A new jail rule for Fail2Ban and ModSecurity (Web Application Firewall) was added. Fail2Ban will now block suspicious connections detected by Web Application Firewall.

  55. [+] Plesk packages are now signed with a GPG key to prevent installation of unauthorized packages. If a signature check fails for one or more packages, installation of Plesk will not continue (unless the check is switched off manually).

  56. [+] Debian 8 and dist-upgrade from Debian 7 to Debian 8 are supported. Before performing the operating system upgrade, make sure you have read about the possible issues you may encounter here.

  57. [+] The support for dist-upgrade of Debian 6 to Debian 7 was added. Before performing the operating system upgrade, make sure you have read about the possible issues you may encounter here.

  58. [+] The support for dist-upgrade of Ubuntu 12.04 to Ubuntu 14.04 was added.

  59. [+] Developers of Plesk extensions can retrieve information about the features available in Plesk license keys by means of SDK methods.

  60. [+] Administrators can switch on automatic upgrade of Plesk extensions in Server Management > Extensions > Settings.

  61. [+] Users can view web server logs in Plesk.

  62. [+] Administrators and resellers can conveniently operate Plesk from smartphones and tablets when in the Service Provider View.

  63. [+] Plesk now looks better on devices with Apple Retina display and other devices with high PPI displays.

  64. [+] Administrators and resellers can switch between Power User view and Service Provider view by clicking Change View in the navigation pane.

  65. [+] Users can configure mail auto-reply to switch off on a specific date.

  66. [+] PostgreSQL 9.4 is now supported.

  67. [+] CloudLinux 7 is now supported.

  68. [*] Plesk design and usability were improved, multiple user experience issues were addressed.

  69. [*] Multiple improvements in Backup Manager: incremental backup support, quicker backing up process, UI improvrments.

  70. [*] Security improvements.

  71. [*] Improved usability and user experience of several WordPress Toolkit scenarios.

  72. [*] The repair utility was improved: new aspects and commands were added.

  73. [*] Multiple improvements in scheduled tasks manager. Users can now set up tasks of various types (command, PHP script, URL), and manage them more easily.

  74. [*] Numerous improvements were made to the upgrade process.

  75. [*] Multiple API improvements.

  76. [*] Support for the apc and the xcache modules was added in PHP versions 5.4 and earlier. Support for the opcache module was added for PHP version 5.5 and later.

  77. [*] The command-line utility call wp_instance -get-list now returns the full path to a WordPress installation. Users can use this path in custom scripts. Before, the command returned only the ID, URL, and the owner of each installation.

  78. [*] Users have an option to recreate a database to which they are restoring a database dump. Also, a progress bar for the dump uploading and the support of gzip format were added. (PPP-12007)

  79. [*] Users can export database dumps to their webspaces without downloading files to their local computers.

  80. [*] The "Skins and Color Schemes" Plesk extension is now included in the default Plesk installation.

  81. [*] The SDK API now allows Plesk administrators to forbid authenticating using the native credentials if a different authentication method exists (for example, the "LDAP auth" Plesk extension is installed).

  82. [*] The gpgcheck=0 setting in the Plesk PHP repository files was replaced with gpgcheck=1.

  83. [*] A number of legacy modules that can be insecure for shared hosting environments were removed from the default Plesk installation.

  84. [*] During Plesk upgrade, unsupported extensions are disabled.

  85. [*] Instead of private IP addresses, Plesk behind NAT now displays the corresponding public IP addresses in its interface.

  86. [*] The "Allow activating APS apps using license keys from the Plesk license pool" permission was removed.

  87. [*] The "Use FTP storage" checkbox was added to the "FTP Storage Settings" screen.

  88. [*] By default, the first application you install on a domain is now installed in the domain root. Subsequent applications are installed in subfolders, as previously.

  89. [*] New permissions were added to service plans: "Allow customers to back up and restore data related to their account", and "Allow customers to back up and restore data related to their subscription".

  90. [*] On CentOS 5, RedHat Enterprise Linux 5, and CloudLinux 5, MySQL was updated to version 5.5.

  91. [*] CodeEditor is now integrated with File Manager. A new option to edit files with CodeEditor is available from the File Manager's context menu.

  92. [*] phpMyAdmin was updated to version 4.4.9.

  93. [*] Customers and resellers are no longer required to specify a telephone number upon the first login to Plesk.

  94. [*] A new user interface theme was applied to Plesk Installer.

  95. [*] Dovecot IMAP mail server is offered by default for new Plesk installations.

  96. [*] Autocompletion logic for Plesk self-repair tools was improved.

  97. [*] The list of websites on the Websites & Domains tab is now loaded faster. (PPP-14536)

  98. [*] Mailman mailing lists manager was excluded from the "typical" installation offered by the Installer.

  99. [*] The administrator can now prohibit creation of domains (including also domain aliases, subdomains, and subscriptions) with the www prefix, by adding the following line to the [domainManagement] section of the panel.ini file: features.restrictStartWithWww = on (PPP-11842, PPPM-1946)

  100. [*] Plesk Installer now writes the progress status of slow operations in the log file, preventing users from thinking that the process has stopped responding. (PPP-12111)

  101. [*] Plesk users can see the database server addresses for all databases. (PPP-12114, PPM-74)

  102. [*] Data restoration from backups now takes less time. (PPP-11967)

  103. [*] Now users can include files into webspace root directories by means of virtual host templates. (PPP-5631)

  104. [*] WordPress installation by means of the WordPress toolkit now takes less time.

  105. [*] Administrators can resolve database consistency issues described in by running the repair --check-db command.

  106. [*] Administrators can check the Plesk's database for consistency issues by running the repair --check-db command.

  107. [-] The "" email address in the Plesk GPG key was replaced with "". This also led to the Plesk GPG key being re-issued and the Plesk packages signed with the new key. (PPP-16668)

  108. [*] The site preview mechanism was improved. Users now face fewer restrictions on the type of content that can be viewed in the preview mode. In addition, the preview link now works outside Plesk by default.

  109. [*] Web Presence Builder has become an optional component of Plesk. You can choose not to install it. (PPP-10390)

  110. [*] Now TLS versions 1.1 and 1.2 are enabled for nginx by default.

  111. [*] ProFTPD was updated to version 1.3.5a.

  112. [*] Rsync was updated to version 3.1.1.

  113. [*] Passenger was updated to version 5.0.10.

  114. [*] Dovecot was updated to version 2.2.18.

  115. [*] Courier and authlib were updated to version 4.16.1.

  116. [*] Postfix was updated to version 2.11.5.

  117. [*] Roundcube was updated to version 1.1.2.

  118. [*] Nginx was updated to version 1.9.2.

  119. [*] phpMyAdmin was updated to version 4.4.9.

  120. [*] mod_security was updated to version 2.9.0.

  121. [*] mod_cloudflare was updated to version

  122. [*] Fail2ban was updated to version 0.9.2.

  123. [*] MySQL used for customer databases was updated to version 5.5.41

  124. [*] Support for MariaDB version 10 was added.

  125. [*] Awstats was updated to version 7.4.

  126. [*] PHP used to run Plesk was updated to 5.6.12.

  127. [-] PHP builds for Debian 6 are no longer supported, as Debian 8 has been released and Plesk supports only the two latest major versions of each operating system.

  128. [-] Custom PHP builds for Debian 6 were removed from the Plesk repositories.

  129. [-] Adobe ColdFusion is no longer supported by Plesk.

  130. [-] The "Loading..." message is no longer shown when administrators visit Server Administration Panel > Server Management > Tools and Settings.

  131. [-] Plesk no longer offers commercial applications sold through Storefront. All premium commercial application offers were removed from the Plesk UI, and corresponding controls have also been removed. (PPP-11964)

  132. [-] Creating a backup including an inconsistent database resulted in an error message. (PPP-17008)

  133. [-] Plesk upgrade failed if there were two or more databases with the same name but using different combinations of upper/lower case letters. (PPP-16969)

  134. [-] On CentOS 7, the nginx service failed to start on boot if the network service had not started. (PPP-16921)

  135. [-] A domain created with no hosting and then renamed could not be switched to website hosting. (PPP-16720)

  136. [-] The PHP-FPM handler could be selected even if the server was running a version of Apache earlier than 2.4. (PPP-15219)

  137. [-] Plesk users granted a certain combination of permissions could shut down the Tomcat service on the server. (PPP-16843)

  138. [-] The installation of the Plesk 12.5.29 update failed if the number of MySQL connections set in the my.cnf file was too low. (PPP-16817)

  139. [-] Backup files created in Plesk 12.0 were not rotated after upgrading to Plesk 12.5. Note that the new behaviour means that dumps with different prefixes are now rotated (previously, dumps with the prefix different from the currently configured one were exempt from rotation). (PPP-16793)

  140. [-] After a domain was renamed, backup files created prior to the renaming were not rotated. (PPP-16659)

  141. [-] The Plesk Backup Manager treated any file uploaded to an FTP repository as a Plesk backup file. (PPP-16758)

  142. [-] Updating the settings of a subscription via the Plesk XML-API resulted in all requisite backend calls running twice. (PPP-16660)

  143. [-] plesk-php*-release packages were installed on Plesk 12.0 installations. (PPP-16630)

  144. [-] PHP files were downloaded instead of being executed if the PHP handler for the corresonding domain was set to "Apache module". (PPP-16599)

  145. [-] The xinetd service did not start automatically after upgrading to Plesk 12.5 from Plesk 11.5 on Debian 6 and 7. (PPP-15759)

  146. [-] On certain Plesk GUI screens, trying to change the active subscription resulted in the "Error: Permission denied" message. (PPP-15059)

  147. [-] The session.save_path configuration directive pointed to a non-existing directory in the default Plesk PHP settings. (PPP-14783)

  148. [-] Emails were not delivered to mailboxes with the "&" symbol in the name on Plesk servers with Dovecot installed. (PPP-14426)

  149. [-] PHP versions 5.1 and 5.2 were displayed as 5 in the Plesk GUI. (PPP-13393)

  150. [-] The database containing the data about outgoing mail sometimes became corrupted. (PPP-12738)

  151. [-] The amount of disk space taken up by logs of add-on domains was added twice when calculating the subscription's disk usage. (PPP-12636)

  152. [-] Plesk administrators were unable to set the default SSL certificate via the CLI. (PPP-8916)

  153. [-] The Drupal application could be installed without saving an administrative password. (PPP-16650)

  154. [-] A website with forwarding to an IDN domain could not be opened. (PPP-16648)

  155. [-] Plesk generated SSL certificates using the old SHA1 algorithm instead of the new SHA256 algorithm. (PPP-16634)

  156. [-] A reseller with a custom service plan could not create subscriptions because of an empty IP pool. (PPP-16236)

  157. [-] Information about the subscription settings obtained via the command line contained a wrong expiration date. (PPP-16055)

  158. [-] Mass email notifications could not be sent when Plesk was installed on CentOS 7 and MSMTP was used as an SMTP client. (PPP-14865)

  159. [-] The session.save_path parameter in the php.ini file pointed to a non-existent directory. (PPP-14783)

  160. [-] While backing up the security policy settings, the secure FTP settings were missed from the backup. (PPP-14038)

  161. [-] On CentOS 5, custom MySQL 5.5 package was replaced with another version by Plesk Installer. (PPP-13936)

  162. [-] An unclear error message was displayed if a customer changed password and an application installed for this customer’s subscription was removed. (PPP-8578)

  163. [-] The "What to do with mail for non-existent users" setting of a service plan was not applied to a subscription based on that service plan. (PPP-7386)

  164. [-] If the "FPM application served by nginx" PHP handler was used for a subscription, the "max_execution time" option was not applied to PHP scripts. (PPP-16509)

  165. [-] When retrieving information about the currently installed Plesk version via the command line, CloudLinux could not be detected properly. (PPP-13826)

  166. [-] On CentOS 7, starting Plesk after Dr.Web service had been started could make this service unmanageable. (PPP-13948)

  167. [-] Trying to rename a domain to a name matching the name of an already existing subdomain resulted in an unclear error. (PPP-16270)

  168. [-] Users could not migrate WordPress installations from servers with the WordPress Toolkit installed to servers without the WordPress toolkit. (PPP-15073)

  169. [-] The server_prefs utility did not show the values of some service settings. (PPP-15920)

  170. [-] During the creation of additional FTP accounts, customers could not browse the file system to specify a home directory. (PPP-15907)

  171. [-] On attempting to upgrade Plesk 10.0.0 to version 10.4.4 on CentOS 5, users could encounter the error "Unexpected 'St11logic_error' caught: basic_string::_S_construct NULL not valid". (PPP-15479)

  172. [-] Users could not find installed WordPress plugins by searching in WordPress Toolkit; the search mechanism was case-sensitive. (PPP-15379)

  173. [-] Backups could be lost if the user's name and subscription name were too long (more than 47 characters in length). (PPP-3404)

  174. [-] Users could not install any applications on CentOS 7 installations with MariaDB 10. (PPP-15702)

  175. [-] Users could not set up personal FTP storage with support for FTPS. (PPP-13522)

  176. [-] Users could not transfer data from Plesk on CentOS 7 servers to Plesk on CentOS 7 servers. They encountered the following error: "Perhaps /usr/local/psa/admin/bin/deployer application missing, has incorrect permissions or unexpectedly terminated". (PPP-15332)

  177. [-] Customers could not use incremental backup and granular restoration if they used a ProFTPD-based server as a personal FTP storage. (PPP-15542)

  178. [-] Actions performed by administrators and additional administrator accounts were attributed to the user "admin" in the action log. This made it impossible to determine who performed a specific operation. (PPP-15318)

  179. [-] Clicking a custom button configured to open a website could result in an "Uncaught ReferenceError: openScreen is not definedonclick @ (index):392" error. (PPP-14942)

  180. [-] Plesk would sometimes send out notifications warning of MySQL and MSSQL soft limits being exceeded when there was actually no overuse. (PPPM-2740)

  181. [-] Plesk Installer could not revert to the original sources list if no source for system packages could be found. (PPP-14887)

  182. [-] Users could disable proxy and proxy_fcgi Apache modules for a domain using the FPM PHP handler on Plesk for Linux installations. This led to broken Apache configuration for the domain. (PPP-14853)

  183. [-] The fpm-service process listened on port 9000 after enabling PHP-FPM support in Plesk for Linux. (PPP-14733)

  184. [-] Privileges for database users assigned to manage all databases for a subscription could be reset under specific circumstances. (PPP-14563)

  185. [-] The Websites & Domains screen loaded slowly on Plesk servers with a very large number of subscriptions. (PPP-14536)

  186. [-] Wording of the mail server option in GUI enabling an alternative SMTP port has been improved. (PPP-14359)

  187. [-] The xinet.d service did not start after the installation of Plesk microupdates. (PPP-14006)

  188. [-] Plesk installer displayed an unclear error message in GUI if apt-get configuration was corrupted. (PPP-13720)

  189. [-] Replacing the default Plesk MTA with MSMTP resulted in some courier-imap packages not being removed. (PPP-12819)

  190. [-] The names of some languages in the language selection menu in Plesk were inconsistently formatted. (PPP-12729)

  191. [-] The startup scripts of Plesk for Linux installed in a Virtuozzo container started the postgresql service even if it was disabled by the chkconfig utility. (PPP-8791)

  192. [-] After installation of WordPress, users were prompted to add it to WordPress Toolkit, even if WordPress Toolkit was not available in Plesk. (PPP-14784)

  193. [-] Administrators could not remove IP addresses if site preview was switched on in Tools & Settings > Website Preview Settings. (PPP-14591)

  194. [-] Users could not update the Moodle application via Plesk. Updating failed with the error "Non-zero exit status returned by script". (PPP-14196)

  195. [-] After changing the default SSL certificate on the server, administrators could encounter issues with nginx configuration. (PPP-13673)

  196. [-] Website owners could not view real IPv6 addresses of website visitors in access_log files. (PPPM-2672)

  197. [-] Users could not back up website files that contained the percentage sign (%) in the file names. (PPP-14722)

  198. [-] Subscriptions could be suspended automatically due to the expiration date being reached or resource usage limits being exceeded even if Plesk was running in the Power User mode. (PPP-14533)

  199. [-] Password recovery emails were being tagged as spam by email providers due to the recipient's address being simultaneously used as the sender's address. (PPP-14475)

  200. [-] Backing up data to the FTP repository required a local backup to be created first. Backup failed if there was not sufficient disk space for the local backup. (PPP-14445)

  201. [-] Descriptions of applications in Plesk were shown in English, even if users selected another language for the Plesk interface. (PPP-14195)

  202. [-] Users could not restore mail data from multivolume backups. (PPP-14197)

  203. [-] Administrators could not limit outgoing mail sent by scripts. (PPP-14433)

  204. [-] PHP warnings "Division by zero; File: /usr/local/psa/admin/application/default/views/scripts/outgoing-mail/messages.phtml" were recorded in /logs/panel.log. (PPP-14418)

  205. [-] Administrators could not use port 587 after running the mchk utility, even if mail submission was disabled in Plesk. (PPP-14342)

  206. [-] Languages on the Plesk login screen were not arranged in alphabetical order. (PPP-14186)

  207. [-] Entries in the list of webspaces were not arranged in alphabetical order. (PPP-13399)

  208. [-] Users could not restore mail from multivolume backups. (PPP-14197, PPPM-2559)

  209. [-] Plesk administrator could not use the certificate CLI utility to set a newly created SSL certificate as the default one. (PPP-14212, PPPM-2600)

  210. [-] Users were unable to open Websites & Domains > Limiting Outgoing Messages if the maximum number of mailboxes for their subscriptions was set to 0. (PPP-13991)

  211. [-] Users could only see up to 25 objects in the classic view. (PPP-12582, PPPM-2184)

  212. [-] Incorrect language titles were used in language selection menus. (PPP-12729, PPPM-2142)

  213. [-] Information about the size of mailboxes was displayed incorrectly in the Dutch locale. (PPP-12251, PPPM-2104)

  214. [-] The specified SSH port in the Migration Manager settings was not saved to be used in the future. (PPP-10743, PPPM-1778)

  215. [-] A WordPress installation became impossible to manage using the WordPress Toolkit as a result of its plugin calling the die() function. (PPP-12221, PPPM-2054)

  216. [-] A WordPress installation broke down when its plugin loaded the wp-config.php or wp-load.php file. (PPP-12719, PPPM-2237)

  217. [-] The mchk utility hung at the step 'Checking for: mail_auth_dump...'. (PPP-12924, PPPM-2281)

  218. [-] After the administrator converted the Plesk server's operating system from CentOS 6 to CloudLinux 6, the component mod_fcgid failed to install. (PPP-13753)

  219. [-] The Classic View mode for the list of domains on a subscription displayed only twenty five domains when a user opened it the first time after logging in. (PPP-13843)

  220. [-] Customers could not register the LiteSpeed SAPI PHP handler with Plesk. (PPP-13609)

  221. [-] Administrators could not apply custom PHP settings to websites by means of command-line tools, if the websites were under a subscription that was synchronized with a service plan. (PPP-13431)

  222. [-] Users could not access the guide on customizing Plesk themes from Tools & Settings > Plesk Branding. (PPP-11306)

  223. [-] If users installed WordPress and created a symbolic link to the installation directory, WordPress Toolkit incorrectly determined the number of WordPress installations. (PPP-13599)

  224. [-] Migration could take a long time because the /var/log/sw-cp-server/sw-engine.log file was not automatically cleaned up. (PPP-13463)

  225. [-] Users could not change the location of the VHOSTS directory by means of the /usr/local/psa/bin/ script. (PPP-13371)

  226. [-] Users could not set up an FTP storage for backups if they preferred SSL/TLS connections. (PPP-13362)

  227. [-] An incorrect warning was shown on attempting to remove a domain alias. (PPP-13330)

  228. [-] Customers attempted to install applications on wildcard subdomains (*, which resulted in errors. Now the option to install applications on wildcard subdomains is no longer available. (PPP-13093)

  229. [-] Administrators could not restore customers' backups by means of the pleskrestore command-line utility. The following error occurred: Source file is not a valid XML file. (PPP-12953)

  230. [-] Users could not upgrade to Plesk 12 if they had switched to the MSMTP client after using a local mail server (for example, Postfix). (PPP-12819)

  231. [-] If source and destination servers hosted a database with the same name which belonged to different domains, then such a database was not transferred during transfer of these domains. (PPP-10524)

  232. [-] After restarting a Virtuozzo container, PostgreSQL service started automatically even if it was switched off. (PPPM-1467)

  233. [-] The administrator could not prohibit the installation of a particular Plesk extension in Plesk on VPS.

  234. [-] Users could not set PHP settings through the Plesk's XML API.

  235. [-] Users could not transfer subscriptions separately from subscription owners.

  236. [-] The link View all webspaces appeared when it was not supposed to appear.

  237. [-] Add-on plans had all default permissions switched on right after their creation.

  238. [-] The directory wp-content was unavailable over FTP.

  239. [-] IP address mapping for subdomains worked incorrectly if the NAT Manager extension was used in Plesk.

  240. [-] WordPress Toolkit security checking did not work in Plesk with PHP-FPM installed and the options Process PHP by nginx and Serve static files directly by nginx switched on.

  241. [-] When users tried to log in to webmail, the connection to the webmail storage server failed.

  242. [-] Wildcard subdomain reconfiguration failed after the upgrade of Plesk from 11.0 to 12.0.

  243. [-] Plesk did not remove files of timed-out PHP sessions from directories containing session files.

  244. [-] Plesk showed an incorrect warning message on the mailbox settings page about the limit on outgoing mail.

  245. [-] Additional users were unable to edit files with HTML editor.

  246. [-] Hiding WordPress version using the WordPress Toolkit could break WordPress layout.

  247. [-] The email messages containing viruses were put into the mail queue but were not sent, causing a lot of notifications.

  248. [-] Email forwarding did not work if there were upper-case characters in the domain name and the outgoing mail control was switched on.

  249. [-] The Atomic ModSecurity rule set for Web Application Firewall failed to install with the error "Syntax error on line 40 of /etc/apache2/modsecurity.d/rules/atomic/modsec/01_asl_domain_blocks.conf".

  250. [-] Plesk did not write the log messages about PHP and Horde errors in /var/log/psa-horde/psa-horde.log.

  251. [-] Scheduled backups to an FTP server could not be completed if an FTP error occurred during the transfer of a backup file. (PPP-12448)

  252. [-] Administrators could not schedule backups that would exclude mail content. (PPP-12495)

  253. [-] Administrators could not schedule multivolume backups if a volume size was set to be more than 2048 megabytes. (PPP-12494)

  254. [-] License keys could not be renewed automatically. (PPP-12471)

  255. [-] When users were notified about the availability of application updates on the Websites & Domains screen, the notification did not provide links for updating applications. (PPP-11184)

  256. [-] Administrators were not notified when additional license keys for Plesk components expired. (PPP-6284)

  257. [-] If there were more than 256 sites hosted on a server, nginx failed with the error "Too many open files". (PPP-4248)

  258. [-] Google Services for Websites access provider program is no longer supported by Plesk. All links related to the program were removed from the Plesk UI. (PPP-3098)

  259. [-] Users were unable to restore modified backup files using the API RPC interface. (PPP-10845)

  260. [-] While setting up a subscription or a customer account, administrators saw empty fields for selecting service plan add-ons. (PPP-12028)

  261. [-] Sorting of APS applications by popularity is no longer supported by Plesk; therefore, the corresponding control was removed from the GUI. (PPP-11290)


Your Comments