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

Linux Plesk 8.3 to Linux Plesk 10.x

S

SukuJG

Guest
Server A:
========
OS : CentOS 5.4
Plesk Version : 8.3


Server B:
========
OS : CentOS Latest
Plesk : 10.x (latest)

I have plesk backup of client on Server A. If any one knows the procedures and the things needed to take in consideration while migrating, please help me.

Server A is not online. Server B is online. I have plesk backup file of Serve A in Server B.
 
You must log in or register to reply here.

Similar threads

AlbertoPizzarelli
Resolved Plesk update fails on CentOS 7 + TuxCare ELS: missing trousers dependency (gnutls requires trousers >= 0.3.11.2)
Replies
4
Views
3K
D4NY
D4NY
C
Issue Plesk Migrator Error(Failed to connect to target Plesk server by Plesk API: Plesk error [1005]: Protocol version '1.6.8.0' is not supported. Current
Replies
2
Views
7K
coffee34
C
T
Question Need clarification on quota management in service plan
Replies
6
Views
3K
Kaspar
K
S
Question Upgrade MariaDB from 10.x to 11.x via Plesk?
Replies
2
Views
4K
SDGPete
S
T
Resolved FTPS remote backups fail after upgrade to Plesk 18.0.80 due to TLS session not being resumed on the FTP data connection (pmm-ras regression)
2
Replies
21
Views
30K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top