• 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.

Update 11.5.30 to 12.0.18

szisti

New Pleskian
Has anyone done this?
I'm running a server with 11.5.30 Update #47 and have the pending update to the new version
I'm running the new on a smaller server and love it, but am paranoid about updating

What issues should I expect?
 
Recently upgraded 2 production servers from 11.5 to 12. Both on CentOS 6.5 very latest updates.

Went quite well with only 2 minor issues after the upgrade.

Did read a lot on the forum to prepare. Backup of servers essential - just in case. Certificates have caused issues, make sure yours are ok. Packages of other repos apparenty caused the odd issue. Don't use other repos ourself but would advise to temporarily disable them, than re-enabe after upgrade.

Upgrade itself went very well.

Quick systems check after the upgrade showed that the clients websites weren't displayed. Logged into server console and
# /usr/local/psa/admin/bin/httpdmng --reconfigure-all
sorted it. [Had the same issue when upgrading from Plesk 11.0 to 11.5 a long while back]

Second issue was discovered a little while later. Compression of log files wasn't working as expected. As it doesn't really affect clients it was tackled the day after.

All-in-all quite smooth. Thanks to Plesk team for doing a very good job on the upgrade path! :)
 
Back
Top