The following improvement has been made:
[*] Administrators can now set a server-wide limit on the number of scheduled backups that can be stored in one repository. The limits of all subscriptions and accounts are reduced to the server-wide value, if such a value is specified. The newly created subscriptions and accounts will have the specified limit by default. Users cannot set a greater limit than the server-wide one. (PPP-10831)
The following issues have been resolved:
[-] If users logged in using rsession, the Plesk interface language was English, even if these users previously selected another language in Interface Settings. (PPP-11069)
[-] (Linux) In Plesk 12.0, temporary backup files were stored in /tmp by default. This could cause the server not to respond if the size of backup files was bigger than the size of the directory. Temporary backup files are now stored in /usr/local/psa/PMM/tmp. (PPP-11008)
[-] (Linux) After the user had enabled the Atomic rule set for ModSecurity (web application firewall), ModSecurity (web application firewall) stopped working. (PPP-11007)
[-] Users could not restore the default DNS zone settings for domain aliases. The Restore the DNS Zone form did not appear. (PPP-10974)
[-] (Linux) Plesk installed on OpenVZ containers could not be configured after the upgrade to 12.0 because of the missing directory /dev/shm. (PPP-10830, PPPM-1655)
[-] (Linux) The Awstats statistics of the last day of the month was calculated incorrectly. (PPP-8850, PPPM-1486)
Posts Tagged PPP
The following issues have been resolved:
[-] Users could not access the website folder for managing files of the website if Classic List was selected in Websites & Domains > Domains List Settings. The following error occurred: “Invalid URL was requested”. (PPP-10818)
[-] (Linux) Administrators could not create a backup of the server. The error message about the wrong format of the backup file appeared. (PPP-10804)
[-] The administrator’s interface language switched back to default (English) after visiting the Tools & Settings > Backup Manager > Scheduled Backup Setting screen. (PPP-10784, PPPM-1738)
[-] If users customized their domain PHP settings and then the administrator modified other settings on their subscription, the domain PHP setting changed back to default. (PPP-10744, PPPM-1779)
[-] (Linux) Administrators could not migrate reseller’s subscriptions without migrating the reseller. (PPP-10691, PPPM-1754)
[-] (Windows) On Windows 2012 x64, Plesk administrators could not install a Plesk license key on Plesk inside a Hyper-V virtual machine. The error saying that the license key is invalid occurred.
[-] (Windows) Administrators could not migrate domains with a remote MSSQL database if the MSSQL server was running on any port other than default 1433. (PPP-10800, PPPM-1802)
The following issues have been resolved:
[-] If Plesk was installed without a DNS service, administrators could not create subscriptions. The following error occurred: “Call to a member function isNeedUpdate() on a non-object in /opt/psa/admin/plib/PhDomain.php”. (PPP-10817)
[-] (Linux) Administrators could not upgrade the Plesk server to the version 12.0 from an earlier version if they had the mod_security package installed on the server. The following error occurred: “You have already installed the mod_security package which is not from Panel distribution. You should deinstall the mod_security package before the ‘modsecurity’ component installation, otherwise your Apache web-server will be broken”. (PPP-10791, PPPM-1798)
[-] Users could not access the File Manager if Classic List was selected in Websites & Domains > Domains List Settings. The following error occurred: “Invalid URL was requested”. (PPP-10783, PPPM-1795)
[-] Users could not see status messages for extensions. (PPP-10776)
[-] Users could not restore from an FTP repository any backup created on the same Plesk server unless they selected the option Restore the backup file despite a corrupted signature. The Restore button was inactive. (PPP-10767)
[-] (Linux) On openSuSE 13.1 x32, after a server restart, the FTP service stopped working. (PPP-10750)
[-] (Linux) Temporary files of messages were not removed from the /usr/local/psa/handlers/spool/ directory if greylisting spam protection was switched on. This might cause a lack of disk space. (PPP-10705, PPPM-1766)
[-] Users could not see some form validation messages when Japanese was selected as Plesk interface language. (PPP-10702, PPPM-1763)
[-] Users could not change hosting settings for the main domain on their subscription if there were a lot of additional domains, subdomains, and/or domain aliases. The following error message was shown: “This operation is taking too long. Check the results in a few minutes”. (PPP-10698, PPPM-1762)
[-] (Windows) Administrators could not restore file permissions in the webspace with the repair.exe utility. It repaired only folder permissions. (PPP-10729, PPPM-1745)
The following improvements have been made:
[*] Security improvements.
[*] (Windows) PHP version was updated to 5.4.30 and 5.5.14.
[*] PHPMyAdmin was updated to version 4.2.5.
The following issues have been resolved:
[-] (Windows) Users encountered errors during migration from Plesk 8.6 installations that used an external MS SQL database server. (PPPM-1772)
[-] (Windows) Users whose service plan did not allow creating MySQL databases, could not create Microsoft SQL Server databases. (PPPM-1759)
[-] (Windows) Users could not fully restore or migrate data if they contained files larger than 4 gigabytes. (PPPM-1753)
[-] (Linux) Users could not back up data on 32-bit OpenSUSE 13.1 Linux installations. (PPP-10701)
[-] (Linux) Users could not back up data to FTP repositories on 64-bit OpenSUSE 13.1 Linux installations. (PPP-10692)
[-] (Linux) During migration from Plesk 11.0 to Plesk 12, mailing list administrators received notifications about the creation of a mailing list. (PPPM-1691)
[-] After editing WordPress configuration file and specifying an incorrect WordPress version number in it, users could no longer manage WordPress installations. (PPPM-1752)
[-] In some cases, administrators could not remove databases from Tools & Settings > Database Servers > Local MySQL Server > Databases. (PPP-10659)
[-] (Linux) Plesk was inaccessible after it was installed by means of Parallels Installer with the option –install-everything. (PPPM-1749)
[-] Outgoing mail control showed incorrect information about exceeded mail limits. (PPPM-1747)
[-] After migration from Plesk 9.5 to Plesk 11.5, if the transition scheme “convert customers to resellers” was used, domains could be associated with a reseller’s customer instead of the newly converted reseller. (PPPM-1675)
[-] If resources were overused by a Plesk customer, numerous mail notifications were sent to the customer’s reseller and the server administrator. (PPPM-1489)
The following issues have been resolved:
[-] (Linux) Administrators could not back up server settings if external webmail was registered in Plesk. (PPP-10629)
[-] (Linux) Users could not install Plesk using One-Click Installer. (PPP-10624)
[-] (Linux) Watchdog could not start Fail2Ban on Debian/Ubuntu operating systems. (PPP-10610)
[-] (Linux) Scheduled backup could fail with the “File exists” error. (PPP-10601)
[-] The OK and Cancel buttons were not shown when users tried to create a domain in Power User view while DNS service was switched off. (PPPM-1742)
[-] (Linux) Operations on domains with stopped BIND service could corrupt Plesk database on SuSE Linux 13.1. (PPP-10594)
[-] (Linux) On CentOS 5, customers could not send email messages via Roundcube webmail if outgoing mail control was switched on. (PPP-10593)
[-] Plesk database became inconsistent after users created a domain via API RPC by using protocol version 1.6.2.0 and earlier. (PPP-10582)
[-] (Linux) After upgrading Plesk, users could not log in to it. The following error occurred: “Internal error: Permission denied”. (PPP-10574)
[-] Administrators could not reconfigure the Manage Domain Names button in Tools & Settings > External Services. (PPPM-1734)
[-] (Linux) Files owned by Apache could not be backed up by the pleskbackup command-line tool. (PPP-10543)
[-] (Linux) Roundcube could not connect to the database on Plesk installations cloned with the option “-prepare-public-image”. (PPP-10539)
[-] (Linux) Plesk upgrade via old versionless templates (psa-kav8 depends: psa-kav8-multiarch) failed on Ubuntu 12.04. (PPP-10516)
[-] Search and sorting of applications by category did not work in the applications catalog. (PPPM-1728)
[-] (Linux) On Ubuntu 14.04 with enabled Watchdog, MySQL service failed to start after a server was restarted. (PPP-10488)
[-] (Linux) On 32-bit Ubuntu 14.04, administrators could not use Plesk health monitor. The following error occurred: “This RRD was created on another architecture”. (PPP-10486)
[-] (Linux) Even if greylisting was switched off for a domain, it remained switched on for a domain alias. (PPP-10465, PPPM-759)
[-] (Linux) After migrating from Plesk 11.0 to Plesk 12, mailing list administrators received a notification with a wrong password. (PPP-10375, PPPM-1691)
[-] Resellers could not set up web hosting for domains if they were not granted the “Common PHP settings management” permission. (PPPM-794)
[-] (Windows) Scheduled backup could fail with the “File exists” error. (PPP-10601)
[-] (Windows) Microsoft SQL Server database tables with varchar/nvarchar/varbinary(MAX) columns could not be migrated from Plesk 8.6. (PPPM-1744)
[-] (Windows) The reconfigurator utility crashed while repairing the security settings of virtual hosts. (PPP-10592)
[-] (Windows) Users could not create sites with Presence Builder if only PHP 5.5 was installed on the server. (PPP-10489)
[-] (Windows) License keys on Plesk for Windows had the Fail2Ban component switched on, although ModSecurity and Fail2Ban are not available on Plesk for Windows installations. (PPPM-1721)
The following issue was resolved:
[-] Users created in WHMCS could not log in to Plesk. (PPP-9934, PPPM-1698)
Debian: 2590-1: wireshark: Multiple vulnerabilities
(Dec 26) Bjorn Mork and Laurent Butti discovered crashes in the PPP and RTPS2 dissectors, which could potentially result in the execution of arbitrary code. [More…]