• 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 Why is `plesk-ssh-terminal` running?

klodoma

New Pleskian
From the CSF/LDF Firewall I start getting these notifications:
Time: Mon Sep 20 13:00:26 2021 +0200 Account: plesk-ssh-terminal Resource: Process Time Exceeded: 109277 > 1800 (seconds) Executable: /opt/psa/admin/plib/modules/ssh-terminal/libexec/plesk-ssh-terminal Command Line: /usr/local/psa/admin/plib/modules/ssh-terminal/libexec/plesk-ssh-terminal --listen /run/plesk-ssh-terminal/backend.sock --connect-to *:5022 PID: 3093395 (Parent PID:3093395) Killed: No

Afaik, I didn't enabled the plesk-ssh-terminal.

So, why is this running?
 
In our case this "auto-install" did on top lead to a broken SSH chrooted environment for our clients on a Debian 9 server. Override the passwords + update_chroot.sh did not help. As a quick-fix we did uninstall the extension to fix the issue. Not sure if we will make a bug report because we will not use the extension.
 
Back
Top