Ike.ninja

The following new features have been implemented:

[+]  Webmail server nodes. Webmail server nodes are now supported. By default, webmail services are provided by the management node. To reduce the load on the management node, administrators can add a webmail server node to the system.
[+]  Support for external mail servers. Administrators can add any external mail server to the PPA infrastructure. This may be useful, for example, when you need to use an MTA which is not supported by PPA’s standard mail node roles. The connection with such servers is performed by means of special APS apps, so-called connectors. Such a connector should be developed and registered in PPA before adding an external mail server node.
[+]  Login page branding. Administrators and resellers can adjust the appearance of the login page.
[+]  Easy changing of the management node’s IP address. Administrators can seamlessly move the management node to another IP address using the /usr/local/ppa/bin/ppa_ipaddress utility.
[+]  Support for SNI on branding subscriptions. Administrators and resellers can use unique SSL certificates for brands on shared IP addresses.
[+]  Forced retrieval of PPA license keys. Administrators can update the information about their PPA license keys at any time in License & Security > License Manager.

The following functionality have been improved:

[*]  Automatic updating of license keys was improved.
[*]  Now administrators can limit the number of subdomains on subscriptions.
[*]  Administrators can now connect service nodes with CentOS 6.x or RedHat Linux 6.x without needing to preliminarily configure YUM on them.
[*]  The migration process was improved: now it is faster and it takes less disk space.

The following bugs have been fixed:

[-]  Administrators failed to properly complete the installation of PPA on CentOS 5.8. On attempting to log in to PPA through a web browser, they encountered the “500 Internal Server Error”.
[-]  Administrators sometimes failed to connect a service node if (1) they selected two different IP addresses in the node connection settings: one as the backnet IP address (used for communications between service nodes and the management node) and another as the IP address for hosting; and (2) if both IP addresses were from the same subnet range. They encountered the following error in Task Manager: “Can not configure agent on host ‘IP address’, reason: ‘Stopping pleskd: [ OK ].”
[-]  Administrators could not create branded subscriptions on dedicated IP addresses. The subscriptions were always created on shared IP addresses.
[-]  Administrators could make management nodes inoperable after installing the Apache services. For this reason, PPA no longer allows installing Apache, Postfix and MySQL on management nodes.
[-]  Auto-reply messages could not be shown by mail clients due to incorrectly specified MIME type.
[-]  Users were unable to host different web content on domains and subdomains that were hosted on the same dedicated IP address.
[-]  Users could not calculate the size of a directory in Content Manager. They encountered the following error: “Unable to get size for . System error 13: Permission denied.”
[-]  AWStats did not calculate website visits statistics properly.
[-]  Administrators failed to create subscriptions with mail services if the mail service was provided by Postfix installed on the management node. They encountered the following error: “Unable to receive setting ‘plesk_mail_service_node_key’.”
[-]  License key expiration warnings shown in the Hosting Panel led to a wrong page.
[-]  Administrators failed to migrate hosting subscriptions from Plesk for Linux to PPA if at least one SmarterMail service node was connected to PPA.
[-]  During migration from Plesk 11.x, the passwords of resellers and customers for access to the Hosting Panel were reset.
[-]  Users were unable to switch off mail services for their subscriptions if the services were provided by SmarterMail. The Hosting Panel raised the following error: “Unable to load object of type DSMail with id=127: Mail_Facade->turnOffDomain() failed: Turning domain off is not supported.”
[-]  Administrators failed to create subscriptions with Apache and MySQL hosting on a dedicated IP address. They encountered the following error: Error: Database server mysql :3306 does not exist.
[-]  The handling of custom ftp.. and www. DNS records was improved.
[-]  Migration from Plesk for Linux to PPA could stall due to an internal error.
[-]  After migration from Plesk 8 for Linux, applications installed on websites no longer worked because their databases were not migrated.
[-] If CBM was switched on, and a new auxiliary user account with the Accountant role was partially created in the Hosting Panel (the task failed in the process), then after removing that account from the Administration Panel, users will not be able to create an account with the same username again.
[-]  During migration from Plesk for Linux 8.6, domains for which hosting was not configured and the Tomcat service was switched off could not be migrated.
[-]  MySQL service nodes could not be added if “sa” was used as the database administrator’s username.
[-]  Administrators could not migrate domain administrator accounts from Plesk 8.6 if the account information contained non-Latin characters.