• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

I need your advices

R

redprive

Guest
Hi,

I have plesk 7.5.4 on FedoraCore3.

I want upgrade twice versions but I don't know how I have to start?

My idea is buy to a new server, then to install FC7 and after to install latest version PLESK.

After runs plesk migration manager on old server to new server and when process has finished then to change IP's on new server to all domains registered continues point to same IP's.

Can you give me a good advices to a correct migration?

Thank you very much
 
I think you're plan sounds great. That's what I would do. :)
 
You must log in or register to reply here.

Similar threads

J
Resolved Cgroups not showing in Services Management
Replies
5
Views
2K
JVG
J
E
Forwarded to devs [Bug] ACME Extension Ignores Updated EAB Credentials – Old Account Remains Cached for Domain
Replies
3
Views
3K
end
E
TorbHo
Question Can TuxCare ELS install older PHP versions on a new Plesk server?
Replies
10
Views
9K
TorbHo
TorbHo
H.W.B
Issue Watchdog down after Plesk update
Replies
7
Views
3K
Sebahat.hadzhi
Sebahat.hadzhi
K
Forwarded to devs Renaming an additional administrator is not reflected in the admin_alias_update event or Action Log: "Login Name" shows the old name as both old and n
Replies
2
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top