• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Exception error when logging in to Plesk (permission denied)

regisg

Regular Pleskian
Hello,

After a stupid CHMOD -R apache:apache on my server (...), I had to reinstall Plesk (12.5.30) with "plesk repair installation".
That was successfull except Restoring SELinux contexts => Starting kavehost : Failed

Unfortunately, i am now unable to loggin in Plesk :

Internal error: Lock Manager error: 'Permission denied'.
Message Lock Manager error: 'Permission denied'.
File Hierarchical.php
Line 120
Type Plesk\Lock\Exception

Then, i tried a lot of solutions :
https://kb.odin.com/en/127101
https://kb.odin.com/en/122077
https://talk.plesk.com/threads/help-needed-permission-denied-after-upgrade-11-to-12.336131/
... no success :-(

I noticed that : http://screenpresso.com/=p42ig ... I wonder if it's OK with regards to permissions ?

Thanks a lot for your help.
 
Make sure that you have correct permission for /var/lock:

# stat /var/lock
File: `/var/lock'
Size: 4096 Blocks: 8 IO Block: 4096 directory
Device: 3c90b621h/1016116769d Inode: 393263 Links: 7
Access: (0775/drwxrwxr-x) Uid: ( 0/ root) Gid: ( 54/ lock)

and as result of wrong permissions lockmamanger will not be able to operate required directory `/var/lock/lmlib/container_locks`

Following KB article may be useful for you - https://kb.odin.com/en/122288
 
Back
Top