• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

How do I - Roll back to an older version?

V

Vengent

Guest
Just did the upgrade from 7.1.6 to 7.5 and can see now that it was a poor decision. Is it possible to roll back without losing all the configurations?
 
You should be able to by uninstalling plesk and reinstalling it again from RPMs.

I haven't tested this so I don't know if there will be any side effects.

Just out of curiosity.... Why was upgrading to 7.5 a poor decision? I'm using Plesk 7.5 and I don't have any problems.
 
That probably won't work as 7.5.0 has a different DB structure to 7.1.x
 
The best and simplest way I can suggest would be to (assuming you read the instructions properly beforehand and did exactly as it and the website suggest... run a full backup before upgrading):
Uninstall Plesk 7.5
Reinstall 7.1.6 from the RPMs
Restore Plesk backup from the backups you ran prior to the upgrade
 
psarestore is very slow at restoring server dumps so I would only recommend you do that if you *absolutely* cannot live with Plesk 7.5.0 - if you're having problems with it then (imho) the best solution would be to either report the bugs to SWsoft and await a fix or look for external help.
 
You must log in or register to reply here.

Similar threads

N
Input Plesk 18.0.80 panel.ini nofun=true
Replies
16
Views
6K
nmdpa3
N
TorbHo
Resolved PHP TuxCare System Updates: ALT-PHP packages held back due to PHP-FPM dependency conflicts
Replies
9
Views
2K
TorbHo
TorbHo
Azurel
Question EULA update after upgrading to 18.0.79 – some questions
Replies
4
Views
7K
Anthony
Anthony
danami
Resolved Plesk PHP packages built with older libavif which breaks yum updates
Replies
2
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
S
Question Possible to do a reverse email migration using Plesk migration tool?
Replies
2
Views
3K
sagelike
S
Back
Top