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

/bin/bash (chrooted) stopped working

ospito

New Pleskian
Hi all,
After upgrading from 8.4 to 8.6 chrooted bash doesn't work anymore.
This is the login procedure from the SFTP cliënt:

Finding Host customerdomain.com ...
Connecting to XX.XX.XX.XX:22
Connected to XX.XX.XX.XX:22 in 0.015625 seconds, Waiting for Server
Response
Server Welcome: SSH-2.0-OpenSSH_4.3
Client Version: SSH-2.0-WS_FTP-9.01-2006.07.25
DSS Signature Verified
Session Keys Created
Ciphers Created
New Client->Server ciphers in place.
New Client->Server ciphers in place.
Completed SSH Key Exchange. New Keys in place.
User Authenticated OK!
Completed SSH User Authentication.
Started subsystem "sftp" on channel 0760a2ce
Received channel close/eof(0x60) message for channel 0760a2ce
Error 842c0000 receiving sftp packet
error 842c0000 initializing sftp protocol
Sending channel close message for channel 0760a2ce
SSH Transport closed.

This user has /bin/bash (chrooted) as the login shell (/usr/local/psa/bin/chrootsh). A user with /bin/bash as login shell everything works fine. When I run /usr/local/psa/bin/chrootsh at command line this is the result:
# /usr/local/psa/bin/chrootsh
mkdtemp() failed
system error: No such file or directory

Anyone a suggestion? I'm stuck. Thanks in advance.
 
try running

sh -x /usr/local/psa/bin/chrootsh

to get more details on this error.

also check to what package this file belongs:
rpm -qf /usr/local/psa/bin/chrootsh

and check consistency of resulting package:
rpm -V package_name
 
Back
Top