• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. J

    Unable to obtain secret key for passwords encryption.

    I resolved the error by correcting the file ownership in /etc/psa/: chown -R psaadm:root /etc/psa/private/ chown psaadm:psaadm /etc/psa/private/.psa.shadow
  2. J

    Unable to obtain secret key for passwords encryption.

    The permissions of /etc/shadow and /etc/passwd match those of the respective files on my reference machine: -rw-r--r-- 1 root root 3.9K Sep 18 04:09 passwd -rw-r----- 1 root shadow 5.4K Sep 26 17:44 shadow I ran: /usr/local/psa/bootstrapper/pp11.0.9-bootstrapper/bootstrapper.sh...
  3. J

    Unable to obtain secret key for passwords encryption.

    Yesterday I accidentally run "chown -R root:root /" on the SSH console of my virtual server. I canceled the running command as soon as I noticed my stupid mistake and started to recover the original file ownerships using a second, similar virtual server instance as a reference. Everything...
Back
Top