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

Question on WHMCS and Plesk

hostking

Regular Pleskian
Seems when we create a second hosting plan for a client they cannot login with the second hosting package username and password.

They need to use the first plesk account username and password they purchased?

Any reason why? or did we do something wrong?
 
Seems when we create a second hosting plan for a client they cannot login with the second hosting package username and password.

They need to use the first plesk account username and password they purchased?

Any reason why? or did we do something wrong?
I think this is normal Plesk behaviour. At least the same thing happens with OBAS. I assume he can select both subscriptions, right? If so, it's perfectly normal behaviour and the second user/pass combination is for FTP access to the specified domain.
 
Its not ideal though as the customer cannot give plesk username and password to someone else to manage only one account.

But guess we have to live with it.
 
Its not ideal though as the customer cannot give plesk username and password to someone else to manage only one account.

But guess we have to live with it.
Can you try testing the following: https://domain.tld:8443 with username: the main website/FTP access username and password: that username's password? It should work, though I'm not really sure as I don't have WHMCS installed.
 
Back
Top