• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Recent content by pluempyx

  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...
See more
Back
Top