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

plesk 11.5.30 Update #40

Status
Not open for further replies.

Graphrix

Basic Pleskian
I have a Centos 6.5 machine running the latest version of Plesk.

Logged in and then updated on the weekend from #39 to #40 successfully. Now I go to click on the business management stuff I am faced with a new login screen that I don't have the username or password for. I get the following response.

"Credentials for application's account are required."​

Could only find the problem associated with 10.** on http://kb.parallels.com/en/9509

Gave that a go and wouldn't recognise anything after step 4.

Now I can no longer log into the admin panel and I get this error message:

Error: Unable to log you on. An internal error occurred in the Single Sign-on authorization engine. Please try to log in later, and contact your hosting service provider if the problem persists.​

Can I get some solutions for this please?
 
Got access back into the admin panel by running this command:

/usr/local/psa/bin/sso -d

Still have issues with the #40 update and still receive the error

Credentials for application's account are required."
 
Have you tried repair sso and billing integration with

# /usr/share/plesk-billing/integration --command=repair-all

Also check that SSO server url from output of command

# /usr/local/psa/bin/sso -g

is resolvable and accessible.
 
Did the job :)

Have you tried repair sso and billing integration with

# /usr/share/plesk-billing/integration --command=repair-all

Also check that SSO server url from output of command

# /usr/local/psa/bin/sso -g

is resolvable and accessible.

That fixed it, thank you :)
 
Status
Not open for further replies.
Back
Top