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

Question dist-upgrade HOWTO "2. Remote management module must be installed on the server": What RMM?

Hi @fuzzy, the documentation does not seem to be very clear in this point. We mean that in case the SSH daemon does not start you should have a way to access your server anyway. Normally this can be achieved by a KVM console that can be connected to your server by your data center, so that you can work on the server without the need to login through SSH.
 
Okay thank you. The support of netclusive doesn't provide such remote access to the vmware esxi instance of my virtual root server. They proposed web based solution as cockpit, but I wasn't convinced. So I started the upgrade anyway. I had success with some minor flaws, but thankfully not with remote access. The mariadb part and udev was tricky, and lxd and tetex resulted in a broken ackage system, but remove them and reinstall them later did the trick.

My main issue as a new user was, not to understand in which way plesk is build into the system. I don't know how it is aware of the state o the system when manually do the dist-upgrade, that I'm familiar with, due to experience with ubuntu and debian.
 
Back
Top