Plesk panel broken after upgrade

[Association_Ouain]

Hi all,

Following the update from 11 to Plesk 12 (and installing latest Ubuntu fixes), the Plesk panel access is broken. Welcome page says:
Can not load key: key is empty.

And of course, no way to login the mgt interface. All services appear up, so this is only affecting the panel web service.

Fishing out the panel.log, it appears to be at a lower level than I initially thought (see below):

Has anyone experienced similar issues after updating from 11 to 12 on Ubuntu (12)?

Any ideas are welcome, thanks for your help.

Nick,

<log>

[18-May-2015 19:46:34 Europe/Berlin] PHP Warning: file_get_contents(/opt/psa/var/sso.sp.pem): failed to open stream: No such file or directory; File: /opt/psa/admin/externals/xmlseclibs.php, Line: 285

[18-May-2015 19:46:34 Europe/Berlin] Exception: PHP Warning: file_get_contents(/opt/psa/var/sso.sp.pem): failed to open stream: No such file or directory; File: /opt/psa/admin/externals/xmlseclibs.php, Line: 285

file: /opt/psa/admin/plib/Smb/Exception/Syntax.php
line: 56
code: 0
trace: #0 [internal function]: Smb_Exception_Syntax::handleError(2, 'file_get_conten...', '/opt/psa/admin/...', 285, Array)
#1 /opt/psa/admin/externals/xmlseclibs.php(285): file_get_contents('/opt/psa/var/ss...')
#2 /opt/psa/admin/plib/sso/SAMLToken.php(485): XMLSecurityKey->loadKey('/opt/psa/var/ss...', true, false)
#3 /opt/psa/admin/plib/sso/SAMLToken.php(342): getXMLSecurityKey('/opt/psa/var/ss...', 'private')
#4 /opt/psa/admin/plib/sso/SAMLToken.php(314): SamlTokenGenerator::sign('<samlp:AuthnReq...')
#5 /opt/psa/admin/htdocs/login_up.php3(218): SamlTokenGenerator::AuthnRequest('https://host...', 'https://host...', 'mz3nfqll...hash...', '', false, false, 'https://host...', NULL)
#6 {main}

[2015-05-18 19:46:35] ERR [panel] Can not load key: key is empty.:
0: xmlseclibs.php:290
XMLSecurityKey->loadKey(string '/opt/psa/var/sso.sp.pem', boolean true, boolean false)
1: SAMLToken.php:485
getXMLSecurityKey(string '/opt/psa/var/sso.sp.pem', string 'private')
2: SAMLToken.php:342
SamlTokenGenerator::sign(string '<samlp:AuthnRequest
xmlns:samlp="urnasis:names:tc:SAML:2.0rotocol"
xmlns:ext="urnasis:names:tc:SAML:2.0:metadata"
xmlns:saml="urnasis:names:tc:SAML:2.0:assertion"
ID="e995a8c04e40c0b8272c8f04ec030d1f7b514128f6"
Version="2.0"
IssueInstant="2015-05-18T17:46:34Z"
Destination="https://hostname:8443/relay"
AssertionConsumerServiceURL="https://hostname:8443/login_up.php3...rl=https:/%@Fhostname3A8443/&amp;return_host="

>
<saml:Issuer>mz3nfqll...hash...pi26yqc</saml:Issuer>
<samlp:Extensions>
<ext:Referer>
<ext:RefererScheme>https</ext:RefererScheme>
<ext:RefererHost>hostname</ext:RefererHost>
<ext:RefererPort>8443</ext:RefererPort>
</ext:Referer>
<ext:UI><ext:URL>https://hostname:8443/sso/ui</ext:URL></ext:UI>
</samlp:Extensions>
</samlp:AuthnRequest>')
3: SAMLToken.php:314
SamlTokenGenerator::AuthnRequest(string 'https://hostname:8443/relay', string 'https://hostname:8443/login_up.php3?window_id=&requested_url=https://hostname:8443/&return_host=', string 'mz3nfqll...hash...pi26yqc', string '', boolean false, boolean false, string 'https://hostname:8443/sso/ui', NULL null)
4: login_up.php3:218
[18-May-2015 19:46:35 Europe/Berlin] Exception: Can not load key: key is empty.
file: /opt/psa/admin/externals/xmlseclibs.php
line: 290
code: 0
trace: #0 /opt/psa/admin/plib/sso/SAMLToken.php(485): XMLSecurityKey->loadKey('/opt/psa/var/ss...', true, false)
#1 /opt/psa/admin/plib/sso/SAMLToken.php(342): getXMLSecurityKey('/opt/psa/var/ss...', 'private')
#2 /opt/psa/admin/plib/sso/SAMLToken.php(314): SamlTokenGenerator::sign('<samlp:AuthnReq...')
#3 /opt/psa/admin/htdocs/login_up.php3(218): SamlTokenGenerator::AuthnRequest('https://host...', 'https://host...', 'mz3nfqll...hash...', '', false, false, 'https://host...', NULL)
#4 {main}
</log>

 

[UFHH01]

Hi Association_Ouain,

you could try "bootstrapper" repair in the first place, which solves quite a lot of failures/issues:

/usr/local/psa/bootstrapper/pp12.0.18-bootstrapper/bootstrapper.sh repair​

 

[Association_Ouain]

Hello UFHH01,

Thanks for taking the time to answer. Much appreciated.

Tried this, does raise some warnings, but apparently nothing I can understand as linked to the Panel itself.

Cheers, Nick.

 

[UFHH01]

Hi Association_Ouain,

if you would like some more help with your investigations and suggestions to solve your issue, it is necessary, that you include log-files and/or corresponding configuration files. For each bootstrapper repair, you will get a new log-file. The path is shown at the very end of each repair procedure.

 

[Association_Ouain]

Hello,

I've shared these:
http://loplop.net/forums/odin/0001/

I'm not seeing anything I believe relevant to the workings of the panel web server in the bootstrapped repair output. And all other hosted services are running without any major glitch. I've put the full Plesk12 upgrade log also, I'm guessing the key is of the issue is hidden somewhere in it.

Thanks, Nick.

 

[Association_Ouain]

Solved!
-> We've solved it finally. A new pair of eyes, always helpful...
Plesk-billing component was installed in our Plesk 11 (thus unused). For some odd reason when updating to 12, it switched to SSO mode (hence the SAML related log indications). Switched SSO off, and a way we go.

Thanks for your help, Nick.