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

Which ports need to be opened for migration process

N

nandar

Guest
Hi,

Plesk documentation didn't mention which ports I should open on source server for migration process.

Source server : plesk 8.1 for Linux
Destination server : plesk 8.2 for Linux

Please help. Thanks.
 
The Migration Manager uses SSH, so you need port 22 open for the server you're migrating from.
 
changing ssh port?

What if I don't have SSH running on a standard port? Is there a configuration I can adjust to change the SSH port that plesk migration manager connects to?
 
I don't believe so. I think you'll have to temporarily change the port back to 22 for the migration.
 
You must log in or register to reply here.

Similar threads

S
Question Possible to do a reverse email migration using Plesk migration tool?
Replies
2
Views
3K
sagelike
S
GSMPRO
Resolved Migretor from Azure VM
Replies
4
Views
2K
GSMPRO
GSMPRO
J
Question goAccess in 18.0.77
2
Replies
27
Views
15K
Bitpalast
Bitpalast
Hangover2
Question [Important] Plesk Security Advisory: Patch Arriving on 27th August 2026
Replies
11
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
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
9K
coffee34
C
Back
Top