• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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