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

Issue Preventing upgrade from Onyx to Obsidian?

BlakelyLondon

New Pleskian
Hy!

How can we stop Plesk Onyx from upgrading to Plesk Obsidian? Onyx won't EOL for the next 14 months so we'd like to take that extra time to plan an scheduled, assisted upgrade immediately after taking a full backup and snapshot. Bear in mind that we don't want to stop updates altogether (like security patches), only release upgrades.

We switched all of our servers' upgrade policy to "Stable" awhile ago, but it looks like Obsidian was recently promoted from GA to Stable so one of our servers self-upgraded yesterday, which led to an unpleasant outage during the Monday morning.

Thanks!
 
And have you tried to uncheck Tools & Settings > Update & Upgrade Settings > Automatically Install * ?
Sorry to address this here, Igor, but we have had at least two servers last year that auto-updated from Onyx to Obsidian although the auto-update options were disabled. I never found out why, because obviously this is difficult to retrace, but it has happened. Luckily we already had several Obsidian installations running, so we knew what we got. But the surprising auto-update was the reason why I then went ahead and ordered the Pro update service to get the rest of the machines updated, too, before there are more surprises.
 
You have chosen a very complicated way of setting up. Take a look at the article, it describes everything in detail and simply.
 
Last edited:
First, we access the client's Plesk panel as administrator and navigate to Tools & Settings. Then on clicking on Updates and Upgrades, it shows option Install or Upgrade Product. Now on this page, we select Plesk Obsidian from the drop-down list and click continue to start the installation.
Talk To Wendys
 
Last edited:
Back
Top