• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

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