• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Recent content by tlacroix

  1. T

    Resolved Weak Algorithm Warning (DSA1024) for Plesk Repositories on Ubuntu 24.04 LTS

    Reenabling the dsa1024 algorithm (workaround 1) is better than nothing (workaround 2 and 3), but there's a reason why they disabled it: it isn't considered secure anymore. So to answer your question: Yes, you probably don't want to keep dsa1024 enabled longer than you need to, and you want to...
  2. T

    Resolved Weak Algorithm Warning (DSA1024) for Plesk Repositories on Ubuntu 24.04 LTS

    For workaround #1, you need to perform the command as root. It will create the file "/etc/apt/apt.conf.d/99weakkey-warning" and write...: APT::Key::Assert-Pubkey-Algo ">=rsa2048,ed25519,ed448,dsa1024"; ... into it. You can do the same with nano or vi or any other editor if you prefer. To...
  3. T

    Resolved Weak Algorithm Warning (DSA1024) for Plesk Repositories on Ubuntu 24.04 LTS

    This is due to an update to the "update-manager" package on 28 May 2025 on Ubuntu 24.04. It's affecting a lot of people, so either the repo owners will fix this quick and/or Ubuntu will roll it back temporarily. If you ask me, their update makes sense security-wise, but not the way they...
  4. T

    Resolved Weak Algorithm Warning (DSA1024) for Plesk Repositories on Ubuntu 24.04 LTS

    This is caused by the update to the Ubuntu package update-manager 1:24.04.12 published on 2025-05-28 23:24:55 UTC. Here are three temporary workarounds for Ubuntu 24.04. All will generate warnings, but no errors. We're using the first one. Workaround 1 (the one I recommend), it reenables...
Back
Top