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

Recent content by ThomasCB

  1. T

    chroot option disappeared on Plesk 11 / CentOS server

    Bump, any update on this? chroot is still broken on our server.
  2. T

    chroot option disappeared on Plesk 11 / CentOS server

    I made a bit of progress here. I ran repair: /usr/local/psa/bootstrapper/pp11.0.9-bootstrapper/bootstrapper.sh repair and /bin/bash(chrooted) now shows up in Plesk, BUT I still can't login vis SSH / SFTP using an acct set to use it.
  3. T

    chroot option disappeared on Plesk 11 / CentOS server

    Sorry I wasn't very thorough - This is an existing Plesk 11.0.9. I did not attempt to upgrade, all though I did apply Update #55 after this happened to see if maybe that would fix it. That went smoothly but did not fix it. The only thing I remember is I was modifying some vhost permissions...
  4. T

    chroot option disappeared on Plesk 11 / CentOS server

    On our CentOS 6 / Plesk 11 server, suddenly bin/bash (chroot) option is no longer available. When I try to SSH in with a user who (had) chroot , I get: execv("/bin/bash") failed system error: Permission denied Help?
  5. T

    Will restricting Plesk port 8443 with hardware firewall cause issues?

    Hey there, we have a hardware firewall and would like to restrict Plesk port 8443 to only certain IPs. Will this affect any Plesk services? Of course, we could use the inbuilt Plesk 11 feature "Restrict Administrative Access" but I'd prefer to do it at the hardware level if it doesn't cause...
See more
Back
Top