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

Resolved Several errors after failed update 17.8.11 Update #94

webwolf

New Pleskian
hi there,

I had a failed update #95 on my Plesk Onyx 17.8.11... I do not understand why. It was running smoothly for years.
I already had to add some tables to my PSA database (Card, dom_level_usrs) because web configuration files were not being generated correctly.
Fortunately I could copy thyem from another Plesk.
But now I want to migrate a domain and I get this error.

Failed to connect to target Plesk server by Plesk API: Plesk error [1002]: DB query failed: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'redirect' in 'where clause', query was: SELECT COUNT(*) FROM `mail` WHERE (redirect = 'true')

I can see this column is not available in the PSA.mail database.
Obviously this has also to do with the failed update.

How can I resolve these errors properly?

Hope to hear a solution, because I am worried.

Best,

Wiebe de Wolf
 
If the update went through otherwise from that one error, the cause is that the upgrade of the database was not performed successfully. You can try

# plesk installer update --repatch
and afterwards
# plesk repair db -y

It would be good to have a backup in place, e.g. a full dump of your psa database, before you try this.

For more details, check this article section "Resolution". It applies to a slightly different case, but it's likely very similar to yours:
 
Thank you, Peter.
It worked like a charm!
You are definitely a Plesk Guru - and you saved my Saturday evening.

keep safe and healthy
 
Back
Top