Issue Why does Plesk randomly decide to forbid SSH access on some accounts?

[MHC_1]

Server operating system version

Alma Linux 9.7

Plesk version and microupdate number

Obsidian 18.0.76#3

We have SSH Keys and connection set up on all accounts on Plesk.

Since the update to 18.0.76#3 Plesk now on some days turns some accounts to "Forbidden" rather than the designated SSH Connection, inside the "Hosting" GUI on the account. Why?

We can't see a cause of what makes this change happen, some accounts run fine, and then booom, the SSH no longer works.

Please fix this

 

[Sebahat.hadzhi]

Hi, @MHC_1 . Could you please check the status of Service Plans > Service Plan Name > Permissions > "Management of access to the server over SSH" for the service plan assigned to the subscriptions the issue occurs for?

 

[MHC_1]

Hi, @MHC_1 . Could you please check the status of Service Plans > Service Plan Name > Permissions > "Management of access to the server over SSH" for the service plan assigned to the subscriptions the issue occurs for?

Hello

The result is "Can allow access only to a chrooted environment" .

The accounts are always SSH "bin/bash (chrooted)" choice in the "hosting" area of the account.

This happens to multiple accounts, and happens after the account has successfully accepted data upload. This has happened just now while with a Client at the office and looking at their site, we needed to exit PhpStorm IDE and restart the PHPStorm and go onto Plesk and Change the SSH access again from Forbidden to "bin/bash (chrooted)" literally seconds after successfully uploading using this method.