-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update from 18.0.41 #94
Comments
Why not upgrade your CentOS 7 to Plesk 18.0.52 ? |
The upgrade to 18.0.52 fails on my server. I was getting the error noted here when I wanted to upgrade to 18.0.50 some weeks ago: https://support.plesk.com/hc/en-us/articles/12376925810455 and the suggested fix is an upgrade for the OS and so I landed on this script to do it. |
I believe the upgrade to version 18.0.43 can be accessed by using the 'plesk installer --all-versions' command. At least, I was able to upgrade from version 18.0.45 to 18.0.46 using this method. |
Hmm, you got the "( 'CentOS' 'Linux' '8.2.2004' 'x86_64' ) available" error on the plesk update? Maybe installer somehow recognize your OS wrong (CentOS 8 instead of CentOS 7) 🤔 |
I'm on CentOS 7 for sure. This was the last bit of the error I got last time I've tried to upgrade:
I've cleaned up |
Uh, I see. It seems that you are using python36u-pip from the IUS repository, which conflicts with python3-pip from the EPEL repository A similar issue was described here. |
Regarding the topic at hand. There is a leapfrog with repositries between 18.0.42 and 18.0.43. So, supporting versions below 18.0.43 may take some time. |
Thanks! I've removed the |
I want to use this script but I've noticed My Plesk Version is 18.0.41 and the minimal version to run this script is 18.0.43. The only available update from my Plesk is 18.0.52 and to get this update I need this script so I can migrate from CentOS 7 to AlmaLinux 8.
I'm willing to try if this script will also work with Plesk 18.0.41 but otherwise is there a way to perform a upgrade to 18.0.43?
Thanks!
The text was updated successfully, but these errors were encountered: