• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Recent upgrade from 9 to 10, causing lots of problems

S

saulpage

Guest
Hi there,

I've recently upgraded from an old server to a new one.

I used the migration manager to migrate from 9 to 10. I imported all settings, domains using "migrate whole server".

Ok so now, I am experiencing quite a few problems with this and the host has advised a rebuild, although I feel going down this path may be unnecessary and will repeat the downtime that I have experienced. There was a few issues with DNS settings but these have now been resolved. It has taken me a long time to get this up and running so are considering my options.

The errors I am encountering, are - I can't change the root password to the new server and when I try to access a folder on a doman, notably the admin section it is saying "Server Connection Not Possible". This was also happening with some other domains, but it seems the host resolved this. What is causing this issues?

The host's support have commented with

"The Password display commands for both plesk 9 and 10 showed a password

293 /usr/local/psa/bin/admin --show-password
294 cd /etc/psa
295 nano .psa.shadow

.psashadow should not exist on Plesk 10


Advised to customer that it would be better to cut his losses now and rebuild than to rebuild later- something went seriously wrong with the migration"

So, what would be the best possible option? Has the migration corrupted files? Will it likely cause more errors in the future if the current one is resolved?

Thanks
 
Back
Top