• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Plesk updated to 8.6 but updater still showing 8.4 not updated

X

Xsigns

Guest
Hello!

After a automatic install of Plesk 8.6 via updater failed, we manually updated from 8.4 to 8.6. This seems to work fine now. But updater is still showing 8.4 as installed and 8.6 for update. How can I correct this?

The server is the 1st server (see sig). Attached a picture of updater status.

Please help. Thank you in advance,
Andre
 

Attachments

  • versions.jpg
    versions.jpg
    49.6 KB · Views: 40
  • updater_details.gif
    updater_details.gif
    78.1 KB · Views: 38
You must log in or register to reply here.

Similar threads

weareimpulse
Resolved Multiple PHP versions have appeared in PLESK that shouldn't be installed
Replies
6
Views
3K
weareimpulse
weareimpulse
Azurel
Question Is there any way to get notified about important security updates?
Replies
5
Views
2K
Azurel
Azurel
K
Question Update Information to Plesk 18.0.79
Replies
1
Views
2K
Sofiia Kulish
Sofiia Kulish
Azurel
Resolved AlmaLinux 9.8: yum update blocked by Plesk PHP 8.4/8.5 GD dependencies on libavif.so.15?
Replies
6
Views
2K
Binesh S
B
T
Question Plesk Update Notification Without Local Email Service
Replies
4
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top