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

Note'd issues with migration manager 7.5.4 + freebsd 5.3

E

etan

Guest
I thought i would write some notes on my experience for others to look out for, also to recieve feedback from others.


My Situation

I have a plesk 7.1.7 server running freebsd 4.10 ( my how stable this has been !! )

Im migrating to a brand new fresh install 7.5.4 server on freebsd 5.3.

1. Migration manager does not like odd characters in clients mailinglists ( this will fail, but only after its transferred everything to your new server , sigh )

2. MIgration of alias emails addresses only on some accounts did not migrate, this has caused some fairly major issues as you could imagine.

3. All my existing subdomains for all clients have had the standard plesk holding page index.html inserted into there home directory, causing all subdomains to stop working, unless you had an index.html in there originally.


Note : If you are running freebsd and trying to get Broadcom gigbit eithernet drivers installed on freebsd 5.3, you can rip the source from a 5.4 install of freebsd and recompile the kernel with the newly added drivers between the version changes.


I will update this as i find more bugs if any "fingers crossed"
 
Originally posted by etan
I thought i would write some notes on my experience for others to look out for, also to recieve feedback from others.

May be you also should contact the support? When I had the similar issues I said them, and Plesk developers investigated the problems and fixed them in the next version.
 
Back
Top