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

Search results

  1. R

    Resolved Migration from 12.5.30 to AWS Plesk Onyx error

    Changed to bash on source and boom! You are awesome Alina! Thank you!
  2. R

    Resolved Migration from 12.5.30 to AWS Plesk Onyx error

    Hi Igor, Command /bin/grep -m1 -E '^\s*PRODUCT_ROOT_D' /etc/psa/psa.conf runs perfectly on source as well as ssh -p 54322 root@SOURCE_IP -a "/bin/grep -m1 -E '^\s*PRODUCT_ROOT_D' /etc/psa/psa.conf" on target locale on both servers returns the same as on your server When I execute migration...
  3. R

    Resolved Migration from 12.5.30 to AWS Plesk Onyx error

    I wonder why nobody has an answer.
  4. R

    Resolved Migration from 12.5.30 to AWS Plesk Onyx error

    Hi Community, I stuck with Migration Manager error on my t2.micro instance. I'm using trial Plesk Onyx license for it. The goal is evaluate migration process from dedicated server to Amazon EC2 Migration fails with following error =========================== Failed to perform action: Check...
Back
Top