• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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