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

Resolved 'CP User Login Attempt via API Failed' ('Login Name': '<invalid>' => '')

Lexz

Basic Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
Version 18.0.63 Update #2,
Good afternoon,
We have several Plesk servers and we use our own control panel. Since we installed a new Plesk server we see the following error in the action log:
'CP User Login Attempt via API Failed' ('Login Name': '<invalid>' => '')
All the others servers are working fine and we already recreated the API keys. Any ideas?

Thank you very much!

OS
AlmaLinux 8.10 (Cerulean Leopard)
Product
Plesk Obsidian
Version 18.0.63 Update #2, last updated on Aug 21, 2024 11:11 AM
 
Small detail, admin actions do work. Only actions as the users don;t work anymore
 
<?xml version="1.0"?>
<packet version="1.6.9.1">
<system>
<status>error</status>
<errcode>11003</errcode>
<errtext>PleskAPIInvalidSecretKeyException : key is not found</errtext>
</system> </packet>
 
Back
Top