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

Issue Loggining in into Plesk 8.1 - error - "component_name__ws (not configured)"

E

Elena Powe

Guest
Hello.

I have installed a new SQL server - MySQL 5.1.32.
I have successfully rebooted my server.
Plesk has initially worked.
Then suddenly I can't login into Plesk anymore.
Get the following message:

"Selecting Default Components
component_name__ws
(not configured)
* Required fields"

Please help me with thorough instructions on what to do.

Many thanks!
 

Attachments

  • 2009-03-08_141500.jpg
    2009-03-08_141500.jpg
    32.3 KB · Views: 3
You must log in or register to reply here.

Similar threads

M
Issue PHP Cronjob in Plesk -- Lack of documentation. Lack of structure. Multiple Issues.
Replies
4
Views
3K
MHC_1
M
Harun
Issue recurring issue notice automatic updating system packages
Replies
5
Views
1K
Harun
Harun
I
Question Plesk firewall and preventing clashes with firewalld
Replies
5
Views
2K
iainh
I
J
Question Plesk itself&also it's components (eg. Immunify360) uses my (personal,external) mail address with faked SMTP
Replies
7
Views
2K
jmar83
J
Matt N
Issue Maria DB 10.11 > 11.4 upgrade results in issues with Plesk Repair Tool - reports innodb corruption in ibdata1
2
Replies
27
Views
16K
Azurel
Azurel
Back
Top