Resolved Plesk Onyx Preview and FeedBack

Status
Not open for further replies.

custer

Administrator
Staff member
Hi everyone,

Previews of the next version of Plesk are now available for everyone and we'd love to hear your thoughts on the new Plesk version coming out later this year.

With Plesk Onyx we are putting web developers in the spotlight. We understand the many requirements of modern web development, and come to the rescue with RubyOnRails support, Git integration, and the ability to quickly deploy specific services required by your latest project in the form of Docker containers. Of course, we are not forgetting about traditional hosters as well, who will be pleased with our System Updates functionality, new PHP-related functionality, improved SSL management, and many other upcoming features.

NEW: Visit Plesk Onyx page at https://www.plesk.com/onyx/ to learn more about Plesk Onyx and provide your feedback!

We need your feedback to make sure we're going the right way and addressing the actual needs of you and your customers. Please don't hesitate and let us know what you think -- whether it's something new you like or something missing that you really need.

How to Install Plesk Preview on Linux

Log in as root and run the following command:
Code:
sh <(curl http://autoinstall.plesk.com/one-click-installer || wget -O - http://autoinstall.plesk.com/one-click-installer) --tier testing

How to Install Plesk Preview on Windows
  1. Download http://autoinstall-win.pp.parallels.com/plesk-installer.exe
  2. Run plesk-installer.exe --all-versions
After that, select the new preview version of Plesk and proceed with the installation as usual.

To view the release notes for Plesk preview, go here:
http://docs.plesk.com/release-notes/17.0/whats-new/

Follow us on Twitter to get the latest information on Plesk previews and other cool stuff: https://twitter.com/pleskofficial
 
Last edited:
Hey everyone,

We've released a new preview build this week - lots of changes this time. Release notes are available at http://docs.plesk.com/release-notes/17.0/change-log/, as usual. We'd love to hear your feedback!

Here's the changelog:
  • CGI support, Perl support, and Python support are disabled in all Plesk service plans by default.
  • A connection string for Docker is now added to the psa.conf file allowing Plesk to communicate with the Docker service.
  • It is possible to use Docker installed on a remote machine (learn more).
  • Git management permission can be set in service plans (learn more).
  • Additional deployment actions can be used in Git (learn more).
  • Administrator can start, stop, or restart Docker from the Services Management page (learn more).
  • A number of improvements for managing Docker images and containers have been introduced (learn more).
  • Administrator can perform a number of new operations on a Docker container, in particular, recreate, commit, download snapshot, or remove a container (learn more).
  • Auto-reply messages were not sent when SpamAssassin detected spam messages. (PPP-20562)
  • XML API request for generating self-signed SSL certificate with wildcard resulted with an error. (PPP-20781)
  • After saving a DNS record of the SRV type its value was displayed incorrectly. (PPP-21078)
  • A server backup could not be restored if additional services were configured for service plans. (PPP-20711)
  • Creation of a reseller’s subscription failed if an administrator added PHP directives to the reseller’s service plan. (PPP-20205)
  • An invalid response was received for an XML API request getting aliases of a non-existing domain. (PPP-21209)
  • A response for an XML API request getting information about webspaces contained no information about webspaces of reseller’s customers. (PPP-19986)
  • In a response for an XML API request getting information about webspaces, the real_size node did not include size of additional domains. (PPP-21329)
  • In case of many custom directories in the /var/lib/psa/dumps directory, the consuming disk space in /usr/local/psa/PMM/logs was growing every day after runnung the daily maintenance script. (PPP-19833)
  • In some cases the default Plesk page could not be opened. (PPP-17514)
  • Service plan without hosting could not be created via XML API. (PPP-21334)
  • If RSS feed was enabled in Plesk without specifying URL, Plesk pages in Power User View could not be opened. (PPP-21267)
  • In some cases backup was blocked due to incorrect free disk space calculation. (PPP-21344, PPP-20730)
  • In some cases subdomain name validation failed because the name of the subdomain was overlapped by DNS zone of the domain. (PPP-21071)
  • Database user password could not be changed if a remote MySQL 5.7 database server was used. (PPP-20792)
  • A subdomain could not be created if a DNS template contained two records with the same host and record type. (PPP-21332)
  • When Postfix mail server was used, emails could not be forwarded from dedicated IP. (PPP-21360)
  • It was impossible to install new license after Plesk had removed a terminated license key. (PPP-20837)
  • If full server backup completed with warning, the Backup Manager screen displayed two items. (PPP-18070)
Linux
  • Nginx version was updated to 1.9.12.
  • CentOS 5, RedHat Enterprise Linux 5, and CloudLinux 5 are no longer supported.
  • The list of patterns for black/white list mail addresses could not be retrieved via the grey_listing command line utility. (PPP-21006)
  • Dr.Web keys were not updated during the daily maintenance task run. (PPP-20585)
  • Wrong PHP version was displayed for a web page if PHP was run as FPM application served by nginx. (PPP-20336)
  • Synchronizing DNS zones information using the “plesk repair –dns” command failed when the /var/named/chroot/etc/named.conf file was absent. (PPP-20965)
  • On CentOS 7x64 Watchdog reported that Apache 2.4 was out of date. (PPP-17755)
  • MySQL database dump could not be imported if a database contained a trigger. (PPP-20972)
  • The dist-upgrade from Debian 7 x64 to Debian 8 failed. (PPP-19430)
  • When a subscription was backed up on Plesk with nginx and then restored to Plesk without nginx, the restoration failed. (PPP-21090)
  • Using short mail account names became unavailable after upgrade from Plesk 12.0 to Plesk 12.5. (PPP-20913)
  • In some cases, the ‘Internal error: Permission denied’ error occured after Plesk cloning in Virtual Environment. (PPP-18646)
  • When Apache graceful restart was enabled in Plesk, a domain could not be reconfigured. (PPP-19527)
  • Java Applications were available in Plesk Web Admin edition though it does not include Developer Pack. (PPP-21075)
  • Plesk configuration was broken if Atomic ModSecurity installation failed. (PPP-18732)
  • If MySQL was restarted during full server backup, the backup failed with multiple warnings. (PPP-20248)
  • Rewrite rules from the .htaccess file do not work when PHP support is enabled with PHP-FPM handler. (PPP-19965)
  • The psa-firewall service failed to load after server restart.(PPP-20899)
  • If Plesk was installed on Amazon AWS or any other VM behind NAT with set public IP, FTP connection did not work. (PPP-17545)
  • A backup could not be restored if a custom password was specified in the backup security settings. (PPP-21372)
  • Extracting files from an archive via File Manager did not replace already existing files. (PPP-21450)
  • Plesk mail user could not switch on mail forwarding. (PPP-21481)
  • In some cases Plesk Migrator did not work because it failed to connect to the source server via SSH. (PPP-18722)
  • A backup created by the pleskbackup utility with the –backup-password option could not be decrypted. (PPP-21484)
  • When trying to update WordPress, the /httpdocs directory was removed with all the data. (PPP-20510)
  • Free memory check before Plesk upgrade worked incorrectly. (PPP-17281)
  • IP address of the domain hosting was changed to outgoing mail IP address after server restoration from a backup. (PPP-20738)
Windows
  • Shared SSL is no longer supported.
  • Microsoft ASP.NET 1.1 version is no longer supported.
  • Backup download is now performed without using temporary files.
  • SmarterMail versions 6.x, 7.x, 8.x, 9.x are no longer supported.
  • If a backup to FTP is performed with an error, all temporary files are removed.
  • Mailbox quota could not be updated via XML API for a domain using MailEnable mail server. (PPP-21161)
  • Installation of WordPress failed on a disabled web site or subscription. (PPP-20840)
  • Updating administrator’s email failed with an error. (PPP-21261)
  • If and APS package with colon in name was uploaded to the server, the server backup was marked as invalid and could not be restored. (PPP-21145)
  • The value of the max_input_time parameter in PHP settings could not be customized and was always equal to the value from the server’s php.ini file. (PPP-20214)
  • WordPress could not be installed for the domain with PHP version 5.3 under a subscription with PHP version 5.2.17.(PPP-19624)
  • If SmarterMail was used as a mail server, the mailing list could not be created. (PPP-20204)
  • Free disk space on destination location was not verified before changing virtual hosts directory. (PPP-21111)
 
Hey Tsuru,

It's not available yet, but we're planning to add this functionality.
 
Our plan is to update the list of supported components closer to RTM. Consider this: if we work on supporting 9.5.2.1 right now, it will be, say, 9.5.5 by the time RTM rolls out, and we'll have to do an extra amount of work to support 9.5.5 (or whatever the latest version will be), at least in terms of QA. So, in general, it's more efficient for us to support latest versions of all 3rd parties late in the development cycle to avoid overhead.

Of course, if a third party update is big and it looks like it will make a big splash (sidenote: "splash" is "plesk" in Russian, hehe), we'll try to check it ASAP, but with minor versions it's better to wait a bit until we're closer to release.
 
Hi everyone,

Another preview build is available this week. Release notes are available at http://docs.plesk.com/release-notes/17.0/change-log/. The biggest change in this preview is that Docker and Git features are now Plesk extensions - and a lot of new functionality was added to Plesk SDK. Let us know what you think!

Here's the changelog:
  • The support for HTTP/2 was added to Plesk.
  • The ability to use Active List components was added to the Plesk SDK.
  • The ability to embed 3rd-party PHP libraries using Composer was added to the Plesk SDK.
  • The ability to use custom PHP namespaces was added to the Plesk SDK.
  • The ability to execute long task and display their progress in the Plesk GUI was added to the Plesk SDK.
  • The ability to use the Plesk GUI navigation tools was added to the Plesk SDK.
  • The ability to add custom content to Plesk forms was added to the Plesk SDK.
  • The “Docker Manager” Plesk extension was published. The extension is available here.
  • The “Git Manager” Plesk extension was published. The extension is available here.
  • The custom buttons functionality of the Plesk SDK was improved.
  • The stability of the Plesk backup process when backing up to FTP was improved.
  • Operations in the File Manager could result in an error if the Plesk interface was open in two or more browser tabs. (PPP-21812)
  • Users could not log in to WordPress using the “admin” user credentials, even if administrative access was granted to the user during installation. (PPP-22068)
  • Tab titles in WordPress Toolkit were not translated in the Korean locale. (PPP-21902)
  • The ability to suspend a domain via the Plesk API was missing, and the status of suspended domains was returned incorrectly when queried via an API call. (PPP-21948)
  • Users could not set specific limits when using the Plesk SDK. (PPP-22093)
  • An incorrect event was being generated when a subdomain was created via the Plesk API. (PPP-22160)
Linux
  • The ability to register services was added to the Plesk SDK.
  • Enabling the SPF spam protection on the server resulted in unclear delivery failure notifications when mail was rejected. (PPP-19877)
  • Enabling the greylisting spam protection on the server resulted in all mail from Office365 being deferred. (PPP-22018)
  • phpMyAdmin configuration storage could not be configured for remote MySQL servers. (PPP-21824)
Windows
  • The ability to execute binary tools with elevated privileges was added to the Plesk SDK.
  • The support for wildcard subdomains was added to Plesk (this feature is only available on Windows Server 2016 or later).
  • On Windows 2012 x64 servers, the creation of multi-volume backups failed if the customer data included one or more files of the size greater than the specified volume size. (PPP-21911)
  • Users could not create or upload Microsoft SQL Server dumps if the passwords of one or more database users contained the “;” symbol. (PPP-22161)
  • Users could not manage error documents for virtual directories whose physical path was mapped to the document root. (PPP-21343)
  • Plesk upgrade attempts failed if the Plesk Installer could not find the .msi file for one or more currently installed packages. (PPP-18418)
  • After removing and re-installing Horde via the Plesk interface, the Horde application pool was not re-created. (PPP-21036)
 
Status
Not open for further replies.
Back
Top