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

Upgrade to Plesk 8.4 no longer an option

S

soarchrist

Guest
The other day I noticed there was an upgrade option to 8.4 (I'm using 8.3)... I didn't upgrade because I was in the middle of another big change and didn't want to do an upgrade before doing a thorough backup and so forth.

But today, when I go to Updater, it says everything is up to date. What gives? What happened to 8.4? Did Parallels pull it for more debugging or what?

Thanks

Scott
 
You must log in or register to reply here.

Similar threads

Azurel
Resolved Broken systemd symlinks left behind after PHP version removal/deactivation
Replies
3
Views
4K
Sebahat.hadzhi
Sebahat.hadzhi
E
Resolved Made a mistake, changed server hostname, please advise
Replies
2
Views
2K
elliotpa04
E
Azurel
Resolved ModSecurity shown as "On" in Plesk GUI but runtime is "Disabled" and modsec_audit.log stays empty
Replies
2
Views
2K
Azurel
Azurel
Azurel
Question EULA update after upgrading to 18.0.79 – some questions
Replies
4
Views
7K
Anthony
Anthony
Azurel
Issue GoAccess using significantly more RAM after update to Plesk Obsidian 18.0.79?
Replies
5
Views
3K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top