• 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 Inconsistent Plesk Versions Causing Confusion 18.0.30 released after 18.0.31

K

karam

Basic Pleskian
What is going on Plesk developers ?
18.0.30 Update 3 is released after 18.0.31 Update 1
My Server is confused, I stopped auto updates before it makes a huge mistake, as it updated to 18.0.30 Update 3, and it is requesting me to update to the 18.0.31 Update which was released earlier
Any clarifications of what's happening and what should we do ?

Thank you
Whatthe.PNG
 
Indeed, the 18.0.30 Update 3 release led to problems with the upgrade to 18.0.31 (users didn't see the release). At the moment the problem has been fixed on autoinstall and autoinstall-win, and bug report PAUX-2811 has been created. In general, even if the releases are mixed up, you will not be able to upgrade from 18.0.31 to 18.0.30.
 
IgorG said:
Indeed, the 18.0.30 Update 3 release led to problems with the upgrade to 18.0.31 (users didn't see the release). At the moment the problem has been fixed on autoinstall and autoinstall-win, and bug report PAUX-2811 has been created. In general, even if the releases are mixed up, you will not be able to upgrade from 18.0.31 to 18.0.30.
Click to expand...
I see, how about my specific case ? I was in an older version, (older than 18.0.30 and 18.0.31) and my Plesk automatically updated it self to 18.0.30 Update 3.
And It is now asking to update to 18.0.31 , I didn't let it to do so
Can I safely do that ? as 18.0.30 update 3 is released after 18.0.31 .. am afraid it breaks something
Please check the image attached.

Thank you
 

Attachments

  • safe.PNG
    safe.PNG
    31.9 KB · Views: 9
You can safely upgrade to 18.0.30 update 3 and then to 18.0.31
 
You must log in or register to reply here.

Similar threads

R
Resolved WP Toolkit/Wordpress Toolkit - older version screenshot issue
Replies
4
Views
525
rhall
R
R
Issue UFW turned off and Fail2Ban suddenly completely missing from Plesk Panel -- Very Concerning
Replies
4
Views
2K
regenix
R
learning_curve
Issue Plesk Related Issues Arising After Upgrading Ubuntu Server OS (22.04 LTS to 24.04 LTS)
Replies
6
Views
2K
learning_curve
learning_curve
futureweb
Resolved Older Plesk Versions + Let's Encrypt Asynchronous Order Finalization
Replies
6
Views
2K
futureweb
futureweb
B
Issue High latency, unreliable performance & 522 errors on a Plesk server that ran fine for 6+ months
Replies
8
Views
2K
HHawk
HHawk
Back
Top