• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

chroot SSH no longer works after psarestore

A

acidbox

Guest
We had a server outage the other day and restored our Plesk 7.5.4 server via the psarestore dump. Everything seemed to go fine, all sites are up, e-mail is running, Plesk works fine, however for some reason no chrooted SSH accounts work at all.

By default, when I try to log in as a chrooted user (or su to that user), it does nothing. It just goes goes to a blank command line with no message.

If I try to edit that user's physical hosting setup and move them to forbidden and back to chrooted SSH again, I get this error when trying to login as that user or su to that user:

mkdtemp() failed
system error: No such file or directory

I've run an strace on this but the text is too big to paste in this post. Does anyone have a clue as to why this is happening, or how to get it back to normal?

Thanks.
 
Recently had this same issue when I upgraded my sarge plesk box to etch.

Did you ever find a resolution?
 
Back
Top