• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Failed to repair SSO: Failed to get SSO accounts info: (HTTP code: )

EduardoG

Basic Pleskian
Plesk 10.1 on latest Centos 64 showing "SSO status: Error Repair SSO", even when showing all sync statistics right ("0 Sync errors")
I click on "Repair SSO" and get:
Error: The following errors occurred when repairing the SSO:
Failed to repair SSO: Failed to get SSO accounts info: (HTTP code: )
Please resolve the problems manually and retry to sync again.

I run it from console and get an unknown error:
/usr/share/plesk-billing/sso --command=repair-accounts
The '/usr/share/plesk-billing/sso' command was filed with unknown error. All details of the problem has been stored into the 'sso.crash.log' file.

I've enabled ALLOW_DEBUG_LOGGING to get a detailed sso.crash.log file but can see no errors in that file, neither have a working log to comparte.

Once again, I have nowhere to look for answer, no docs, no KB...
Please, help.
 
Sure! that page is in my bookmarks. But see what happened:
# /usr/share/plesk-billing/sso --command=detach --app-type=admin
The '/usr/share/plesk-billing/sso' command was filed with unknown error. All details of the problem has been stored into the 'sso.crash.log' file.

I have that sso.crash.log, with sensible information, but don't know what to look for.

Now SSO is completelly failed :-(
 
I had this same problem when I initially installed v10 (as well as MANY more)... and once again when I updated to 10.1. Hopefully this isn't going to be a continued issue with each update.
 
is the (HTTP code: ) issue fixed?

I'm running PLesk 10.0.1 on Centos 5.6, and installing SSO give me the same problems of the other guys.
the sqlite db is completely emtpy.

Then when running the attach I always get the following error:
[root@centosplesk ~]# /usr/share/plesk-billing/sso --command=attach --app-type=admin --idp-url=https://centosplesk:11443
(HTTP code: )

sso.log nor error_log are actually logging anything.

What is the error?
 
Back
Top