The post Are you an expert yet? Take the New Plesk Onyx Quiz | 5 Minutes appeared first on Plesk.
The post These 9 Web Hosting Trends could be impacting your business appeared first on Plesk.
Following our last WordPress Toolkit update, we’re sharing how this complete solution helps the business of developers and hosters. WordPress beginner or pro, your life’s about to become easier.
The post Four ways the updated WordPress Toolkit helps your business appeared first on Plesk.
Parallels is pleased to introduce the update #20 for the version 12.0.18 of Parallels Plesk.
The 12.0.18 update #20 is recommended for all Plesk users. It includes resolution of the issues related to the stability, compatibility, and security of your server.
To ensure optimal server reliability and security, Parallels strongly recommends keeping your operating system and Plesk software up-to-date.
The following issues were resolved:
[-] (Windows) Plesk reconfigurator could not find the utilities for repairing Plesk services on 64-bit Windows installations. (PPPM-2146)
[-] (Windows) Incorrect ASP.NET version was shown to Plesk users who did not have privileges to manage hosting settings. (PPPM-2153)
[-] (Windows) Applications that required ASP.NET could not be installed if the ASP.NET version supported by a hosting account did not satisfy the application’s requirements. (PPPM-2154)
Legend:
[+] – Added
[-] – Issue resolved
[*] – Improved
A CVE-2014-3566 vulnerability in SSLv3 protocol was identified by the Google security team. There is an additional whitepaper available from OpenSSL that also describes this vulnerability.
You can check if your are vulnerable using the following script as an
{!{code}!}czoxODc6XCIjIHdnZXQgaHR0cDovL2tiLnNwLnBhcmFsbGVscy5jb20vQXR0YWNobWVudHMva2NzLTQwMDA3L3Bvb2RsZS5zaAojIGN7WyYqJl19aG1vZCAreCBwb29kbGUuc2gKIyBmb3IgaSBpbiBgZWNobyAyMSA1ODcgNDQzIDQ2NSA3MDgxIDg0NDMgOTkzIDk5NSBgOyBkbyAvYntbJiomXX1pbi9zaCAvcm9vdC9wb29kbGUuc2ggJmx0O0lQJmd0OyAkaTsgZG9uZQpcIjt7WyYqJl19{!{/code}!}
The attack described above requires an SSL 3.0 connection to be established, so disabling the SSL 3.0 protocol in the client or in the server (or both) will deflect a potential attack.
You may use special scripts below to disable SSLv3 for all the services:
See instructions below to disable SSLv3 per service.
If you’re running Apache, include the following line in your configuration file /etc/httpd/conf/httpd.conf among the other SSL directives:
{!{code}!}czozMDpcIlNTTFByb3RvY29sIEFsbCAtU1NMdjIgLVNTTHYzClwiO3tbJiomXX0={!{/code}!}
And restart the server, e.g.
{!{code}!}czoyOTpcInN1ZG8gc2VydmljZSBhcGFjaGUyIHJlc3RhcnQKXCI7e1smKiZdfQ=={!{/code}!}
Nginx server
If you’re running Nginx, just include the following line in your configuration among the other SSL directives:
{!{code}!}czozNzpcInNzbF9wcm90b2NvbHMgVExTdjEgVExTdjEuMSBUTFN2MS4yOwpcIjt7WyYqJl19{!{/code}!}
additionally for all the sites in Plesk 11.5 for Linux:
{!{code}!}czo0NTQ6XCIjIHNlZCAtaSBcJ3Mvc3NsX3Byb3RvY29scyBTU0x2MiBTU0x2MyBUTFN2MTsvc3NsX3Byb3RvY29scyBUTFN2MSBUTFN2e1smKiZdfTEuMSBUTFN2MS4yOy9nXCcgL3Vzci9sb2NhbC9wc2EvYWRtaW4vY29uZi90ZW1wbGF0ZXMvZGVmYXVsdC9uZ2lueFdlYm1haWxQYXJ0e1smKiZdfWlhbC5waHAKIyBzZWQgLWkgXCdzL3NzbF9wcm90b2NvbHMgU1NMdjIgU1NMdjMgVExTdjE7L3NzbF9wcm90b2NvbHMgVExTdjEgVExTe1smKiZdfXYxLjEgVExTdjEuMjsvZ1wnIC91c3IvbG9jYWwvcHNhL2FkbWluL2NvbmYvdGVtcGxhdGVzL2RlZmF1bHQvbmdpbnhEb21haW5WaXJ0e1smKiZdfXVhbEhvc3QucGhwCiMgc2VkIC1pIFwncy9zc2xfcHJvdG9jb2xzIFNTTHYyIFNTTHYzIFRMU3YxOy9zc2xfcHJvdG9jb2xzIFRMU3Yxe1smKiZdfSBUTFN2MS4xIFRMU3YxLjI7L2dcJyAvdXNyL2xvY2FsL3BzYS9hZG1pbi9jb25mL3RlbXBsYXRlcy9kZWZhdWx0L25naW54Vmhvc3Rze1smKiZdfS5waHAKXCI7e1smKiZdfQ=={!{/code}!}
and sites in Plesk 12.0 for Linux:
{!{code}!}czo0Njg6XCIjIHNlZCAtaSBcJ3Mvc3NsX3Byb3RvY29scyBTU0x2MiBTU0x2MyBUTFN2MTsvc3NsX3Byb3RvY29scyBUTFN2MSBUTFN2e1smKiZdfTEuMSBUTFN2MS4yOy9nXCcgL3Vzci9sb2NhbC9wc2EvYWRtaW4vY29uZi90ZW1wbGF0ZXMvZGVmYXVsdC9uZ2lueFdlYm1haWxQYXJ0e1smKiZdfWlhbC5waHAKIyBzZWQgLWkgXCdzL3NzbF9wcm90b2NvbHMgU1NMdjIgU1NMdjMgVExTdjE7L3NzbF9wcm90b2NvbHMgVExTdjEgVExTe1smKiZdfXYxLjEgVExTdjEuMjsvZ1wnIC91c3IvbG9jYWwvcHNhL2FkbWluL2NvbmYvdGVtcGxhdGVzL2RlZmF1bHQvZG9tYWluL25naW54RG9te1smKiZdfWFpblZpcnR1YWxIb3N0LnBocAojIHNlZCAtaSBcJ3Mvc3NsX3Byb3RvY29scyBTU0x2MiBTU0x2MyBUTFN2MTsvc3NsX3Byb3RvY29se1smKiZdfXMgVExTdjEgVExTdjEuMSBUTFN2MS4yOy9nXCcgL3Vzci9sb2NhbC9wc2EvYWRtaW4vY29uZi90ZW1wbGF0ZXMvZGVmYXVsdC9zZXJ2e1smKiZdfWVyL25naW54Vmhvc3RzLnBocApcIjt7WyYqJl19{!{/code}!}
And reconfigure Apache:
{!{code}!}czo1NDpcIiMgL3Vzci9sb2NhbC9wc2EvYWRtaW4vYmluL2h0dHBkbW5nIC0tcmVjb25maWd1cmUtYWxsClwiO3tbJiomXX0={!{/code}!}
for all the sites in Plesk 10.4, 11.0.9 for Linux add to the Apache configuration file /etc/httpd/conf/httpd.conf the following string:
{!{code}!}czozMDpcIlNTTFByb3RvY29sIEFsbCAtU1NMdjIgLVNTTHYzClwiO3tbJiomXX0={!{/code}!}
and restart Apache:
{!{code}!}czoyNzpcIiMgL2V0Yy9pbml0LmQvaHR0cGQgcmVzdGFyClwiO3tbJiomXX0={!{/code}!}
Reference: Nginx documentation
Include the following line in /etc/dovecot/dovecot.conf
{!{code}!}czozMDpcInNzbF9wcm90b2NvbHMgPSAhU1NMdjIgIVNTTHYzClwiO3tbJiomXX0={!{/code}!}
Restart service:
{!{code}!}czoyOTpcInN1ZG8gc2VydmljZSBkb3ZlY290IHJlc3RhcnQKXCI7e1smKiZdfQ=={!{/code}!}
Edit the following files:
/etc/courier-imap/pop3d-ssl
/etc/courier-imap/imapd-ssl
Add the following string:
{!{code}!}czo3NTpcIlRMU19DSVBIRVJfTElTVD1cIkFMTDohU1NMdjI6IVNTTHYzOiFBREg6IU5VTEw6IUVYUE9SVDohREVTOiFMT1c6QFNUUkVOe1smKiZdfUdUSFwiClwiO3tbJiomXX0={!{/code}!}
Or just modify existing one and add !SSLv3 into cipher list.
Restart services:
{!{code}!}czo3MTpcIiBzdWRvIHNlcnZpY2UgY291cmllci1pbWFwcyByZXN0YXJ0IHN1ZG8gc2VydmljZSBjb3VyaWVyLXBvcDNzIHJlc3RhcnR7WyYqJl19ClwiO3tbJiomXX0={!{/code}!}
For ‘opportunistic SSL’ (encryption policy not enforced and plain is acceptable too), you don’t need to change anything. Even SSLv2 is better than plain, so if you need to secure your server you should be using ‘mandatory SSL’ mode anyway.
For ‘mandatory SSL’ mode being configured already, just add/change the smtpd_tls_mandatory_protocols setting. Add the following string to the /etc/postfix/main.cf file:
{!{code}!}czo0NDpcInNtdHBkX3Rsc19tYW5kYXRvcnlfcHJvdG9jb2xzPSFTU0x2MiwhU1NMdjMKXCI7e1smKiZdfQ=={!{/code}!}
and restart Postfix:
{!{code}!}czoyOTpcInN1ZG8gc2VydmljZSBwb3N0Zml4IHJlc3RhcnQKXCI7e1smKiZdfQ=={!{/code}!}
You can verify if SSLv3 is disabled by using the following command:
{!{code}!}czo0NjpcIm9wZW5zc2wgc19jbGllbnQgLWNvbm5lY3QgbG9jYWxob3N0OjQ2NSAtc3NsMwpcIjt7WyYqJl19{!{/code}!}
If you are not vulnerable (SSLv3 disabled), your output should look something like this:
{!{code}!}czoyNDE6XCJDT05ORUNURUQoMDAwMDAwMDMpCjEzOTgwODYwNjEwNzQ2NDplcnJvcjoxNDA5NDQxMDpTU0wgcm91dGluZXM6U1NMM197WyYqJl19UkVBRF9CWVRFUzpzc2x2MyBhbGVydCBoYW5kc2hha2UgZmFpbHVyZTpzM19wa3QuYzoxMjU3OlNTTCBhbGVydCBudW1iZXIgNDAKMXtbJiomXX0zOTgwODYwNjEwNzQ2NDplcnJvcjoxNDA5RTBFNTpTU0wgcm91dGluZXM6U1NMM19XUklURV9CWVRFUzpzc2wgaGFuZHNoYWtlIGZhe1smKiZdfWlsdXJlOnMzX3BrdC5jOjU5NjoKXCI7e1smKiZdfQ=={!{/code}!}
If you are vulnerable, you should see normal connection output, including the line:
{!{code}!}czo2MDpcIkNPTk5FQ1RFRCgwMDAwMDAwMykKMjIwIG1haWwuZXhhbXBsZS5jb20gRVNNVFAgUG9zdGZpeApET05FClwiO3tbJiomXX0={!{/code}!}
Official Microsoft knowledge base article about disabling particular protocol in IIS:
How to disable PCT 1.0, SSL 2.0, SSL 3.0, or TLS 1.0 in Internet Information Services
Microsoft Windows Server stores information about different security-enhanced channel protocols that Windows Server supports. This information is stored in the registry key.
Click Start, click Run, type regedt32 or type regedit, and then click OK.
In Registry Editor, locate the following registry key:
{!{code}!}czoxMDQ6XCJIS0VZX0xPQ0FMX01BQ0hJTkVcXFN5c3RlbVxcQ3VycmVudENvbnRyb2xTZXRcXENvbnRyb2xcXFNlY3VyaXR5UHJvdmlkZXJze1smKiZdfVxcU0NIQU5ORUxcXFByb3RvY29sc1xcU1NMIDMuMFxcU2VydmVyClwiO3tbJiomXX0={!{/code}!}On the Edit menu, click Add Value.
In the Data Type list, click DWORD.
In the Value Name box, type Enabled, and then click OK.
Note: If this value is present, double-click the value to edit its current value.
Type 00000000 in Binary Editor to set the value of the new key equal to “0”.
As Plesk is using the same SSL engine, sw-cp-server service should be also configured to protect from SSL vulnerability.
Edit ‘/etc/sw-cp-server/config’, add
{!{code}!}czozODpcIiBzc2xfcHJvdG9jb2xzIFRMU3YxIFRMU3YxLjEgVExTdjEuMjsKXCI7e1smKiZdfQ=={!{/code}!}
Restart:
{!{code}!}czozNTpcIiBzdWRvIHNlcnZpY2Ugc3ctY3Atc2VydmVyIHJlc3RhcnQKXCI7e1smKiZdfQ=={!{/code}!}
Edit /usr/local/psa/admin/conf/ssl-conf.sh, add the echo 'ssl.use-sslv3 = "disable"' after the echo 'ssl.use-sslv2 = "disable"' directive, so it should looks alike:
{!{code}!}czo5NzpcIiBlY2hvIFwnc3NsLmVuZ2luZSA9IFwiZW5hYmxlXCJcJyBlY2hvIFwnc3NsLnVzZS1zc2x2MiA9IFwiZGlzYWJsZVwiXCdgIGVjaG8gXCd7WyYqJl19c3NsLnVzZS1zc2x2MyA9IFwiZGlzYWJsZVwiXCcKXCI7e1smKiZdfQ=={!{/code}!}
Restart:
{!{code}!}czozNTpcIiBzdWRvIHNlcnZpY2Ugc3ctY3Atc2VydmVyIHJlc3RhcnQKXCI7e1smKiZdfQ=={!{/code}!}
A CVE-2014-3566 vulnerability in SSLv3 protocol was identified by the Google security team. There is an additional whitepaper available from OpenSSL that also describes this vulnerability.
You can check if your website is vulnerable with curl:
{!{code}!}czo0MTpcImN1cmwgLXYzIC1YIEhFQUQgaHR0cHM6Ly93d3cuZXhhbXBsZS5jb20KXCI7e1smKiZdfQ=={!{/code}!}
If you are NOT vulnerable, your output should look something like this:
{!{code}!}czoyOTpcImN1cmw6ICgzNSkgU1NMIGNvbm5lY3QgZXJyb3IKXCI7e1smKiZdfQ=={!{/code}!}
If you ARE vulnerable, you will see normal connection outputs, potentially including the line:
{!{code}!}czoyOTpcIlNTTCAzLjAgY29ubmVjdGlvbiB1c2luZyAuLi4KXCI7e1smKiZdfQ=={!{/code}!}
Although the possibility to exploit this vulnerability is quite low, the simplest way is to disable SSL 3.0 – this obsoleted protocol version is being used for compatibility needs and is not required for Parallels products.
For specific Parallels products, here is the list of articles which you may refer to:
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)
What’s Changed
[*] PPA now calculates disk usage for SmarterMail domains and mailboxes.
[*] The checker of service nodes for compatibility with Plesk Automation (check_service_node) was significantly improved.
[*] Before a PPA upgrade/update, the following conditions are checked: YUM is installed and properly configured, YUM repositories are accessible on the management and service nodes.
[-] Users could not search by Active at the Service Templates screen. A system error occurred. (PPA-1521)
[-] Mailboxes with names in mixed case stopped working after upgrade from PPA 11.1 to 11.5. (PPA-1232)
[-] Users could not switch on auto-reply for mailboxes on domains that had domain aliases. (PPA-1313)
[-] Administrators could not create a subscription with support for mail services if the webmail node was uninstalled. (PPA-1346)
[-] After upgrading or updating to PPA 11.5.*, the default Plesk license appeared in the License Manager. (PPA-1428)
[-] After updating to PPA 11.5.5, administrators could not set the ‘Allow overuse of disk space and traffic’ activation parameter for a subscription. The parameter did not appear in the list of the subscription’s resources. (PPA-1456)
[-] DNS PTR records for a subscription were not removed on the subscription removal. (PPA-1476)
[-] Users could not use the webmail service if they were subscribed to Roundcube webmail. (PPA-1497)
[-] When users modified a DNS zone and removed both A and NS records, the DNS zone synchronization failed. The following error occurred: NS record “<domain>. NS ns.<domain>.” has no address records (A or AAAA). (PPA-1560)
[-] Users could see uninformative error messages while managing domain aliases. (PPA-168)
[-] Administrators could not remove subscriptions with support for database services if the database service node was registered with a backnet IP address. (PPA-533)
[-] Update from PPA 11.5.1 was taking too much time. (PPA-653)
[-] Administrators could not install a node with the mixed ‘Apache + Postfix + MySQL + PostgreSQL’ role, if a hyphen was used in the PostgreSQL administrator’s username. They were not informed that the hyphen cannot be used for the PostgreSQL administrator’s username either. (PPA-695)
[-] Updates could fail and administrators had to restart the update because of slow restart. (PPA-725)
[-] Administrators could not add a server with already installed MSSQL as a new MSSQL service node. The error message did not explain how to register an existing database server in the system. (PPA-773)
[-] Administrators could not change the host name of a service node based on Windows Server 2012 R2. The following error occurred: Failed to retrieve the host name of the node: ERROR: Cannot open control pipe – NT_STATUS_INVALID_PARAMETER. (PPA-923)
[-] Restoration of a backup and migration failed if there were system users with the same name on different nodes. The following error occurred: System user <username> doesn’t belong to domain being restored. (PPA-1032)
[-] Administrators could not create a subscription if the SSL certificate for the domain was modified. The following error occurred: SSLCACertificateFile: file ‘/usr/local/psa/var/certificates/<cert-name>’ does not exist or is empty. (PPA-1042)
[-] Customers could see the ‘Access to subscriptions’ permission instead of ‘Access to webspaces’ in the Hosting Panel > Users > a user’s settings. (PPA-1118)
[-] A domain’s webmail configuration file /etc/httpd/conf/plesk.conf.d/webmails/<lwebmail>/<domain>_webmail.conf was not removed on the subscription removal if webmail was hosted on a service node. (PPA-1143)
[-] Administrators received the error message about the main PPA licence expiration when the PPA license was valid, but the POA license was uploaded separately and expired. (PPA-1152)
[-] Users with the Application user role and a mail account could access the Mail tab in the Hosting Panel even when the webspace was disabled and the redirection loop occurred on this tab. (PPA-1165)
[-] Customers could not recalculate actual disk space used by mailboxes through the Hosting Panel > Mail > Refresh Usage Stats. The zero usage for all mailboxes on the domain was shown. (PPA-1196)
[-] When administrators added an MSSQL service node, the Customer Data folder remained empty and was not used as the data directory for MSSQL node. (PPA-1225)
[-] The limit on the number of connections per IP in Courier IMAP server configuration was reset to default after upgrade from PPA 11.1 to 11.5. (PPA-1231)
[-] Administrators received an unclear error message when they tried to install a new Linux node and there was a duplicate host name record in /etc/hosts. (PPA-1576)
[-] When administrators changed the host name of a service node with the ppa.hostname utility, several occurrences of the old host name remained in the ‘plesk’ database. (PPA-1067)
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 functionality was improved:
[*]Security improvements (http://kb.parallels.com/en/122245)
Important: Regular updates of Parallels Plesk Panel and third-party components guarantee that your server stays secure against malicious attacks.
The following functionality was improved:
[*]Security improvements (http://kb.parallels.com/en/122245)
Important: Regular updates of Parallels Plesk Panel and third-party components guarantee that your server stays secure against malicious attacks.
To provide users with an interface for managing NAT, a new extension, called NAT Manager, was created by means of Plesk Extensions SDK.
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)
We’ve always strived to keep Plesk visually modern and pleasant for users, so we have created a new additional skin for Plesk 12. We would love to hear your opinion on this skin, as we’re evaluating it as a possible replacement for current default Plesk skin.
Please go to this page and participate in our survey – http://surveymonkey.com/s/Plesk12-new-skin
Thank you for cooperation!
Dear Plesk users! If you run Plesk on PVC/PCS – make sure you have it upgraded to the latest version, see corresponding KB articles:
The following issue was resolved:
[-] Users created in WHMCS could not log in to Plesk. (PPP-9934, PPPM-1698)
Global IPv6 traffic has grown more than 500% since World IPv6 Launch on June 6, 2012. This year – the 2nd “Launchiversary” – marks the fourth straight year IPv6 use has doubled, according to the Internet Society who organized the effort and reports on IPv6 deployment. According to their findings, if current trends continue, more than half of all internet users will be IPv6-connected in less than four years.
Since early 2011, Parallels Plesk has provided full IPv6 support. We understood what was coming and worked diligently to ensure Plesk would continue to be at the forefront in providing what you need to serve customers. We’ve got you covered.
Let’s review where we are, and what got us here…
The following issues have been resolved:
[-] Plesk Updates are not installed automatically if debug option was enabled in panel.ini (PPPM-1667)
[-] Mail notifications about resource overuse did not show a list of overused resources. (PPPM-869)
[-] (Windows) Older database backups were transferred to the destination server instead of the actual database. ( PPPM-1593)
[-] (Windows) Mail content was not migrated from Plesk and SmarterMail 7.6.
[-] (Windows) SMTP traffic was incorrectly calculated on installations with SmarterMail. (PPPM-1624)
[-] (Windows) Upgrade from older Plesk fails if mysql option innodb_log_file_size was changed in my.cnf for admin MySQL server. (PPPM-1646)
[-] (Linux) The repair utility failed to restore vhost permissions when it was executed with the –restore-vhosts-permissions option (/usr/local/psa/bin/repair –restore-vhosts-permissions). (PPPM-1399)
[-] (Linux) Watchdog 2.03 could not start after a server was restarted. (PPPM-1311)
[-] (Linux) A number of files were missing in Update 26 for CloudLinux 5/6 x32/x64.
The following improvements have been made:
[*] Security improvements. (PPPM-1636)
[*] Ukrainian locale was updated.
The following issues have been resolved:
[-] The SuspendHandlerRunner.php script did not suspend domains.
[-] Wrong dates were set in email messages after migration or restoration of backups on servers with SmarterMail. (PPPM-1189)
[-] (Linux) Mailbox quota was periodically reset to unlimited. (PPPM-1603)
[-] (Linux) Disk usage statistics for primary domains showed zeroes if there were addon domains. (PPPM-1493)
[-] (Windows) Unable to migrate mail messages from Plesk 8.x to Plesk 11.5. (PPPM-1643)
[-] (Windows) Daily registry backup was not in Windows Registry format.
[-] (Windows) Users were unable to remove mailboxes if a local MySQL server was added by IP address, not by localhost. (PPPM-988)
The following issue was resolved:
[-] Potential minor security vulnerability was eliminated. Refer to the following KB articles for more information: http://kb.parallels.com/121310 (PPPM-1609)
[-] Potential minor security vulnerability was eliminated. Refer to the following KB articles for more information: http://kb.parallels.com/121310 (PPPM-1608)
[-] (Linux) Backups on FTP repositories were created in the wrong format after administrators installed update #39. (PPPM-1570)
[-] (Linux) Migration manager failed to select domains by ‘displayName’. (PPPM-83)
[-] Administrators could not restore Microsoft SQL Server databases. (PPPM-1572)
[-] Administrators could not create subdomains on IDN domains via API-RPC. (PPPM-823)
[*] Security improvements (PPPM-1562)
The following issues were resolved:
[-] (Linux) Backup files rotation did not work for subscription backups. (PPPM-1556)
[-] API did not return the correct information about traffic usage by customers. (PPPM-308)
[-] (Windows) The “Support” link in Tools & Settings did not work properly. (PPPM-1558)
[-] (Windows) Administrators could not migrate IDN domains. (PPPM-83). To resolve this, Migration Manager and Migration Agent should be updated on the source server.
The following issue was resolved:
[-] Integration with Key Administrator Partner Central did not work in Plesk 11.5. (PPPM-1552)
Multiple Parallels products are potentially affected by the ‘Heartbleed Bug’ because they are based or installed on operating systems impacted by the OpenSSL CVE-2014-0160 vulnerabilities.
The OpenSSL group has published a solution at http://heartbleed.com/.
Additionally, please review and take action outlined in these Knowledgebase articles:
================================================================
Yesterday a new vulnerability was announced in OpenSSL 1.0.1 that allows an attacker to reveal up to 64kb of memory to a connected server. Parallels is working to assess any product specific issues as a result of this OpenSSL vulnerability. We encourage everyone running a server that uses OpenSSL to upgrade to version 1.0.1g to be protected. For previous versions of OpenSSL, re-compiling with the OPENSSL_NO_HEARTBEATS flag enabled will protect against this vulnerability. We will provide any product-specific updates as they become available.
The following component was updated:
[+]Upgrade phpMyAdmin to version 4.1.12
The following issues were resolved:
[-] (Linux) Mail list creation failed if qmail is used after Microupdate #38 (PPPM-1542)
[-] (Windows) Panel sends notifications even if updates were not installed (PPPM-837)
[-] (Linux) phpMyAdmin redirects redirects browser to https://:8443/ after changing settings
What’s Changed
[+] Service nodes can be deployed on CloudLinux.
[+] A new utility, called sync_resource_usage, is available for synchronizing information about resource usage between the Server Administration Panel and Hosting Panel.
[+] The hostname utility can update the host names of service nodes in PPA.
[+] During migration from Plesk or Plesk Expand to PPA 11.5, providers can keep their existing SmarterMail servers and connect them to PPA as service nodes.
[*] Migration of a large number of sites now takes less time.
[*] The stability of the migration tool was improved.
[*] The algorithm of service node selection for hosting Microsoft SQL Server databases was improved.
[*] Localization was updated for the following languages: German, Spanish, French, Japanese, Italian, Russian, Chinese simplified, and Chinese traditional.
[*] The calculation of hosted domains for licensing purposes was improved: now only physically hosted sites are counted.
[-] In some cases, the screens of Hosting Panel were not shown in full in Internet Explorer. (PPA-159)
[-] Dr.Web license keys could not be renewed automatically. (PPA-474)
[-] Users could not back up their subscriptions. Scheduled backups also did not work. (PPA-753)
[-] The daily maintenance task stalled during the calculation of disk space usage statistics. (PPA-805)
[-] Migration from Plesk 8 to PPA failed with the error “Error: Table ‘psa.horde.turba_objects’ doesn’t exist”. (PPA-822)
[-] Changing resource limits on a subscription could cause undesirable changes to website hosting settings. (PPA-13)
[-] FTP users could not be restored from backups created on IIS service nodes. (PPA-36)
[-] Users could not see log files for add-on domains in the Hosting Panel. (PPA-501)
[-] Administrators could not manage Microsoft SQL Server databases through Infrastructure > Database Servers > DB Webadmin. Wrong database administration tool was opened.(PPA-594)
[-] Domain forwarding configured by customers on webspaces could be reset to web hosting service after administrators or resellers changed the resource limits in the corresponding service template. (PPA-636)
[-] After upgrading from PPA 11.1 to 11.5, custom ProFTPD configurations were discarded and the operation of FTP server was disrupted. (PPA-646)
[-] Terminated license keys for Dr.Web could not be unassigned from service nodes. (PPA-724)
[-] Enabling of Apache service on PPA backup nodes could disrupt the operation of ProFTPD. (PPA-795)
[-] Webspace provisioning failed on Windows nodes with the error “SIDClient error: Unable to release input thread stack”. (PPA-853)
[-] Migration from H-Sphere could fail if the migration tool was run with the “set-dns-forwarding” option. (PPA-790)
[-] Migration from H-Sphere could fail if the SSH key access was used and the H-Sphere node was missing from the list of known hosts. (PPA-777)
[-] Users could not migrate from Plesk for Windows to PPA 11.5 if the destination service node in PPA was running Windows 2012 R2 with German locale. (PPA-751)
[-] Users could not migrate to PPA 11.5 if PPA used an external Microsoft SQL Server (which was added through Infrastructure > Database Servers). (PPA-771)
[-] Users could not transfer the contents of databases from H-Sphere to PPA if the administrator’s password for the destination MySQL server contained a bracket symbol ({). (PPA-774)
[-] Users could not upgrade the migration tool by using the command installer.sh –upgrade. (PPA-749)
[-] During migration from H-Sphere, user names were incorrectly transferred to PPA. (PPA-814)
[-] The migration tool showed error messages while migrating suspended subscriptions in multiple-webspace mode (“transfer-domains-to-subscription: same” in config.ini). (PPA-779)
[-] Migration from Expand installations with centralized mail could produce warning messages about duplicate domain administrator roles. (PPA-848)
53 queries. 10 mb Memory usage. 1.160 seconds.