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

What the Freak'n #$%#$#!!!

L

Lonewolf

Guest
Why the hell is Plesk making a client's name be unique??!!!

And even more so.. does anyone have a crack to fix this ridiculous issue?


(First fumed as to why Plesk would force ftp login names to be unique across the entire domain system instead of using a login/doman name pairing, and now finds that the user's name is also unique. *groans*)
 
FTP users must be unique systemwide - that's not a Plesk "feature"/bug - but a systemrestriction on the OS.
 
Plesk determines what domains a client can access based on the client's login - if this were not forced to be unique for each client, there's no way to keep them seperate.
 
Back
Top