• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Search results

  1. P

    Resolved Server Error 500 Plesk\Lock\Exception

    You can not run this command from a rescue system. When you start the rescue system your server will not be booted regularly. It is just another OS where your filesystem is mounted under /repair. So you can change files in the file system, but you cannot run commands in your system.
  2. P

    Resolved Server Error 500 Plesk\Lock\Exception

    I had the same problem with no SSH access. I booted a rescue system and did the following things. Fix Plesk Edit the file /repair/etc/crontab and add the following line at the end. @Reboot root chown root:lock-manager /run/lock/lmlib && chmod -R 0770 /run/lock/lmlib Fix SSH Edit the file...
  3. P

    Resolved Server Error 500 Plesk\Lock\Exception

    Do you have any information, what your VPS did to make ssh work again? I am stucked with the same problems. I was able to solve the issue with Plesk with the described workaround: Plesk is not accessible: Can't open or create shared memory by shm.name But I had to do it via rescue system...
Back
Top