Facebook
Twitter-
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.
Resolved Zend_Exception No entry is registered for key 'translate'
- Thread starter bonar
- Start date
The most likely cause for this error is a corrupted psa database. I suggest to restore the latest psa database backup. Either - if your psa dump is current - by using the latest nightly dump:
# cd /var/lib/psa/dumps
# cat mysql.daily.dump.1.gz | sed -n '/-- Current Database: `psa`/,/-- Current Database:*/p' | MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -uadmin
or using a previous dump from /var/lib/psa/dumps (you can see them ordered by date). Here is another way to do it:
You should also run
# plesk repair db
after the restore to make sure that the database is consistent.
# cd /var/lib/psa/dumps
# cat mysql.daily.dump.1.gz | sed -n '/-- Current Database: `psa`/,/-- Current Database:*/p' | MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -uadmin
or using a previous dump from /var/lib/psa/dumps (you can see them ordered by date). Here is another way to do it:
You should also run
# plesk repair db
after the restore to make sure that the database is consistent.
