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

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