• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Migration from cpanel to plesk 11

Gabrielpasv

New Pleskian
After successfully setup plesk on ec2 instance on amazon I am now ready to move from cpanel to Plesk 11

As I have never done this before I wanted to ask you about some tips. I already google it but I couldn't find too much information.

Anything in particular you suggest me ? Is there a good tutorial that I did not find online ?

Please help me.

Thank You
 
Install Migration & Transfer Manager on the destination server. You can do this in one of the following ways:

  • Login Server Administration Panel.
  • To install it through the Server Administration Panel, go to Tools & Settings > Updates and Upgrades. The Parallels Installer web interface will open in a new window or tab. In the Installer window, click Add Components, select the checkbox corresponding to the Migration & Transfer Manager component, and click Continue.
 
Thanks for the help. That was what I need however still does not work.

When I tried to open Updates and Upgrades it opens to another browser window and never load the site.

I found some docs stating about port 8447 being used by another program. I killed that was running on 8447 and Still same issue.
After I killed there's nothing running on that port anymore.

Here is the URL it tried to open
https://<my_ip>:8447/?secret=&locale=en-US

It looks like it's getting timed out.
 
Nevermind... I am using a ec2 instance on amazon. All I had to do is add tcp port 8447 to the inbound security group :)

Thanks
 
Darn it,

issues never ends. :)

Now I was able to see the login page but I cannot login. I do not have root password as I use other user with a private key to login. What do you suggest ?

I think root password is disable in ssh by default. Maybe should I try enable it and setup a password ?

Let me know Thanks
 
Back
Top