• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Search results

  1. G

    Resolved Plesk migration error

    Dear @Sebahat.hadzhi, Thanks a lot for your support. This problem has been solved. The problem was with the private key described in the link below...
  2. G

    Resolved Plesk migration error

    Dear @Sebahat.hadzhi, I changed the /etc/ssh/sshd_config file (PubkeyAuthentication yes) and restarted the service (sudo service ssh restart), but the issue is still exist. Please also check the detailed debug log in attachment.
  3. G

    Resolved Plesk migration error

    Also, I can't figure out why I see -i and the location of the private key in the error logs if I chose to connect via user/password.
  4. G

    Resolved Plesk migration error

    Dear colleagues! Could you please help me fix the problem. During the migration preparation phase, the error message shown below is displayed. Just for information, SSH connection is possible from the new Plesk server to the old one. Failed to fetch basic information about resellers, clients...
  5. G

    Issue Plesk Version 12.5.30 upgrade to 17.8.11 failed

    Dear Peter, Seems like we have only one way - buy subscription for support directly from Plesk?
  6. G

    Issue Plesk Version 12.5.30 upgrade to 17.8.11 failed

    I can't address it to Plesk support, because my license was purchased not directly from Plesk (you can see this message on the screenshot below). Do you have other ideas how I can fix this issue? Thank you in advance!
  7. G

    Issue Plesk Version 12.5.30 upgrade to 17.8.11 failed

    Hello there! Several days ago I've run upgrade of Plesk from version 12.5.30 to 17.8.11 via GUI interface. This upgrade was failed, because we haven't free space (I found this issue later - my mistake). After space clean (now we have 17GB free space) I am trying to run upgrade once again, but...
Back
Top