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

Issue Upgrade from 18.0.56 failed

gkar

New Pleskian
Server operating system version
Debian 10
Plesk version and microupdate number
18.0.56.4
Hi everyone,

I've tried for long time to upgrade my VPS from OVH (based on Debian 10) to newer version and it always failed on this error :
Code:
===> Plesk database scheme upgrade has been started.
Applying migrations from: /opt/psa/bootstrapper/pp18.0.61-bootstrapper/migrations/
Migration failed: 18.0.56/2023-09-05-11-50-20_create_domain_keys.php
Duplicate entry '5-default' for key 'PRIMARY'

===> Plesk database scheme was not upgraded completely.

Thanks for your help.
 
Migration failed: 18.0.56/2023-09-05-11-50-20_create_domain_keys.php
Duplicate entry '5-default' for key 'PRIMARY'
This error indicates conflicting Primary Keys in the DomainKeys of the PSA database. I suggest to reach out to out support team for help on this issue, as it's hard to fix without any knowledge on the PSA database. To sign-in to support please go to https://support.plesk.com

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk
 
Back
Top