• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Updating to 12.5

QWeb Ric

Regular Pleskian
We're currently running Plesk 11.5.30 Update #55 on CentOS 6.8, and some time ago we upgraded MySQL via, I think, this process:

wget -q -O - http://www.atomicorp.com/installers/atomic | sh
yum upgrade mysql

I believe this also caused PHP to upgrade. We're currently running PHP 5.4.45 and MySQL 5.5.51.

Recently we've noticed a number of nginx gateway timeouts, and whenever this happens dmesg always shows a PHP segfault, so we believe that PHP 5.4.45 is to blame and are now looking at update options.

If we choose to upgrade Plesk to 12.5, could we please get confirmation that our above Atomic repo use isn't going to complicate anything? What versions of PHP/MySQL will the new Plesk bring in? Unfortunately the "see what's new" link from within Plesk results in a 404 error =(.

Should we remove (if so, how?) the Atomic repo before upgrading Plesk? There was a reason for updating MySQL at the time, I think because a version above 5.4 was needed, but this was so very long ago now that I'm not really sure to be frank. This was our only reason for using that repo though.

Any advice would be much appreciated. These are production servers so I'm of course very cautious about any major version bumps.
 
Hi QWeb Ric,

pls. use the URL: => https://docs.plesk.com/release-notes/12.5/whats-new/
and consider to read the official Plesk documents, if you would like to know, what Plesk ships as own components: => https://docs.plesk.com/release-notes/12.5/software-requirements/#s4-1-1 ( pls. read for example: "Plesk 12.5 for Linux distribution packages include the following components: ..." )


Instead of BELIEVING, you should consider to INVESTIGATE issues on your server, to get to the root cause of each issue. ;)


Sometimes, it is as well a good idea to change the log - level, to get more informations in psa - log - files:

 
Thanks for the links. This answers my versioning concerns.

I'm still not sure however, if I need to remove the Atomic repo first? Also I see that 12.5 comes with Fail2ban now, which is something we installed manually on these servers. Again, would this conflict with what Plesk tries to bring in?
 
Hi QWeb Ric,

consider to disable ALL non-standard repositories before you upgrade, to avoid conflicting package - installations and try to remove the Fail2Ban package ( after you made a backup and moved the folder to "etc/fail2ban.backup", so you are able to use own jails or unique Fail2Ban configurations ).
 
Back
Top