• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

lient Id is undefined error msg (I think I found a new BUG in Plesk 7.5.6)

igoldman

Regular Pleskian
Hello to all members,
as you already know , I feel 100% like the Q&A worker of SW SOFT.

I think I found a new BUG in Plesk CP for windows version 7.5.6

when a client account login to Plesk CP and after several things that he makes then suddenly he get the following error msg :

Client Id is undefined. 0: C:\Program Files\SWsoft\Plesk\admin\auto_prepend\auth.php3:283 psaerror(string "Client Id is undefined.")

Hey developers of Plesk CP , Please pay attension to this thread.
 
It seems that some row was missed from Plesk's database.
 
I have one client who is experiencing this problem, but other clients who were also added after our upgrade to 7.5.6 aren't having the problem.

I've browsed through the psa database looking for any obvious differences between the clients who are/aren't having the problem but I can't see anything of note.
 
Hello,

I got an answer from SW SOFT .
They wrote me the following :


We have documented this bug: # 76805, however it is designated as a floating bug since we can't repeat or recreate it every time :( - We are working on this bug
 
Just for future reference, I've just found that our Plesk gives this error when the disk is full. Cleaning the disk (in this case it was 21gigs of log files on a 30gig drive) fixed the problems immediately.

--
edwin
 
Back
Top