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

Plesk Diagnostics Plesk is not allowed

D

danbell

Guest
I have a Plesk 8.6 for Linux (CentOS release 5.2) server running under a Virtuozzo 4.0 which occasionally has a problem when logging into the Plesk admin site as the admin user (and only the admin user). When you login to https://myserver:8443 as admin, the server logs you in fine and it takes you to Virtuozzo tab and show Container Information listed as "Container mydns.name.com" and shows the green running symbol and also says "The Container is running at the moment.". If you try to click on any menu option on the left you get Plesk Diagnostics reporting that "Plesk is not allowed". The sites on the box seem to be working as well as all other services. If you login as a user then things work fine. I can not seem to find anything like this in the forums or anywhere else. The closest reported issue is an offline management issue, but this container is running. This has happened five times now and the previous "fix" was to restart the container. However, this is not really an acceptable solution. Any ideas?
 
Back
Top