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

Migration from a rescue system using /mnt/ instead of /

Chupa

New Pleskian
Hi

I have a brand new server running Plesk 12.5.30.

On my old server I have Plesk 11.5.30 running. The server is not able to boot in normal mode anymore so I used my server host's rescue system (after doing some manual mounting). I can access the Plesk panel with my web browser. I also have access to all files via my SFTP client.

My idea was not to repair the old sever but just to migrate the old data to the new server using Plesk's Migration Manager.

But as it seems, the paths on the old server in rescue mode are not what the Migration Manager expects while searching the files for migration; probably because i.e. /var/ now is /mnt/var/ on the old server. While I can execute "chroot /mnt" in the console and then access paths as usual, this won't work when using SFTP.

Does anyone know how to tell Plesk to look for folders in /mnt/ instead of / or how to set up the old server so it will set the Migration Manager to the right location or anyone has another idea how to solve this easily?

Regards

Chupa
 
Back
Top