Parallels is pleased to introduce the new Micro-Update #9 for the 11.1 version of Parallels Plesk Automation.
The 11.1 MU#9 update is recommended for all Plesk Automation users and includes general functionality fixes that improve the stability, compatibility, and security of your Plesk Automation server.
To ensure optimal server reliability and security, Parallels strongly recommends keeping your operating system and Plesk Automation software up-to-date.
The following new features have been implemented:
[+] Support for new operating systems for deployment of service nodes. CentOS 6.4 and RedHat 6.4 operating systems are now supported.
[+] Changes in a list of operating systems suitable for deployment of management nodes. Operating systems with 32-bit architecture are no longer supported for deployment of management nodes.
[+] Localization of e-mail notices. E-mail notices sent on various system events can now be localized in several languages.
The following features have been improved:
[*] The speed of migrating auxiliary users was improved.
[*] Providers can now specify the location for placing temporary files for migration.
Option names in the WHMCS module were improved.
The following bugs have been fixed:
Addition of a service node could fail at the step of installing additional packages. Restarting the task or attempting to remove the incompletely added node and then add it again resulted in an error.
[-] When Expand's Centralized DNS service acted as a slave DNS server for Plesk sites, after migration from Expand and configuration of DNS forwarding, websites still opened from the source server.
[-] After renaming the main domain of a subscription, all sites under the subscription received an insecure PHP configuration.
[+] - Added
[-] - Fixed
[*] - Improved
[-] Providers who connected remote FTP repositories for storing backups encountered slow performance of operations on backup files.
[-] Opening a list of service nodes in Administration Panel could take too long.
[-] Customers could not use auto-reply messages that contained more than 256 characters. Empty auto-reply messages were sent instead.
After changing a subscription's service plan and then changing mail service settings under that subscription, users received an unintelligible error message.
Customers could create wildcard PTR records in DNS, which made the DNS server unable to start.
[-] If the provider's branding was set up, users were unable to use the icon linking to file management operations in the list of domains (Control Panel > Websites & Domains tab).
[-] Users could not send e-mail through any mail client programs except for webmail, if the mail service for their subscriptions was provided by the Postfix mail server running on a separate node.
[-] Providers were unable to upgrade the webmail software on service nodes running CentOS 6 and RedHat 6.
[-] Users were unable to create mail accounts without mailboxes if their subscriptions were served by the SmarterMail service.
[-] Customers could make DNS server running on CentOS 6 inoperable by creating NS records without corresponding A records.
[-] PPA failed to remove a subscription if the corresponding service node was unavailable or switched off at that time, and there was no way to retry removal later. The corresponding task was listed as Failed in Task Manager. Now it is possible to restart failed removal tasks in Task Manager.
[-] If customers added resource records to DNS zones and some of the records were invalid, then both valid and invalid records were discarded. Now invalid records are ignored and valid records are applied.
[-] Providers were unable to add service nodes running RHEL 5.8 x64 and RHEL 5.9 x64.
[-] Creation of subscriptions could fail if there were several Apache service nodes and at least one of them was down.
[-] After migration, webmail would no longer work if a domain had custom CNAME webmail.<domain name> DNS record pointing to <domain name>.
[-] The set-low-dns-timings command execution could fail on the source server that hosted a great number of websites. For this reason, after migration of websites, it took significant time for new DNS settings to propagate.
[-] After migration from Expand, users who had access to control panel for changing their e-mail settings in Expand's Centralized Mail, will no longer have such access in PPA.
[-] Migration of mail accounts from Expand failed because of conflicts between mail accounts from Plesk and Expand's Centralized Mail.