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

Bug in Update Module

devCUSoft

New Pleskian
After upgrading to 11.09, my Plesk panel still shows that there is an upgrade to #36 available for the prior 10.4.4 version.
 

Attachments

  • pleskbug36.PNG
    pleskbug36.PNG
    19.8 KB · Views: 24
I think that upgrade was not correctly completed there. I suggest you try bootstrapper repair for completing upgrade procedure.
 
Also problem may be in that information of available updates has not been purged from the database during upgrade procedure. Nest running of DailyMaintenance script should fix this issue. Or you can clean it manually in psa database with

DELETE FROM smb_productUpgrades
DELETE FROM smb_componentUpdates

I have reported this issue to developers. They will fix it.
 
The install went perfectly actually for a change, not one error or problem.

# /usr/local/psa/bootstrapper/pp11.0.9-bootstrapper/bootstrapper.sh repair

Doesnt fix the issue. Will go into the database and clean it up.
 
Hi dev,

Thanks for the update. Let us know exactly what DB changes you had to make, if you don't mind. Would be helpful to future users that may run into the issue.
 
Fix for this problem is available in MU2.

You may install it using autoinstaller (file PSA_11.0.9/microupdates/MU2/common/_usr_local_psa_var_upgrade-complete should be downloaded).

File downloading PSA_11.0.9/microupdates/MU2/common/_usr_local_psa_var_upgrade-complete: 100% was finished.
...
Patching file /usr/local/psa/var/upgrade-complete
Executing /usr/local/psa/var/upgrade-complete
 
Back
Top