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

Issue SFTP login failed for webspace users after AlmaLinux 8 to 9 upgrade

Azurel

Silver Pleskian
Server operating system version
AlmaLinux 9.8
Plesk version and microupdate number
18.0.80#1
After upgrading my server from AlmaLinux 8 to AlmaLinux 9, non-root users could no longer log in via WinSCP (SFTP). Root login via SSH and SFTP continued to work fine. The error in WinSCP was:"Cannot initialize SFTP protocol. Is the host running an SFTP server?" During the upgrade, Leapp added this line to the top of /etc/ssh/ sshd_config:

in "/etc/ssh/ sshd_config" leapp added:
# Added by leapp during upgrade from RHEL8 to RHEL9
Include /etc/ssh/ sshd_config.d/*.conf

I created a new override file "/etc/ssh/ sshd_config.d/00-plesk-sftp.conf" containing:
Subsystem sftp internal-sftp
After executing "systemctl restart sshd", SFTP logins for domain users started working again.

My questions:
1. Is creating this custom config file the correct/recommended solution on AlmaLinux 9 with Plesk, or is there a official Plesk-native way to fix this?
2. Should the Include /etc/ssh/ sshd_config.d/*.conf line added by Leapp remain in sshd_config permanently?

@Sebahat.hadzhi its here not allowed to write here the text "/etc/ssh/ sshd_config" without space? "I get Failed to load resource: the server responded with a status of 403 ()" with reason:
This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data.
 
Back
Top