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

    Resolved Default Website Showing Despite Repair Attempts

    I am running Plesk Onyx 17.8.11 on CentOS 7.6.1810 I had a website that had been deactivated and today I reactivated it in an attempt to test software updates on it. When it was restored it was on a shared IP address. I moved it to a dedicated IP address so I could directly access it by IP...
  2. D

    Resolved Inbound Mail Stays in Queue

    This is a new problem for me. This is a new server running Plesk (not my first Plesk system) and I have a problem where inbound mail stays in queue. I've attempted to flush the queue and no luck. I've done the mailbox repair command from the command line with no luck. I've checked DNS...
  3. D

    Fail2Ban Keeps Turning Off

    I seem to be having an issue on a server with Fail2Ban (ip_ban) turning off. I will occasionally log in to the admin panel in Plesk and I will find IP Address Banning turned off. I will enabled it again and things will be fine for a while but then once again it will turn off. Any idea what...
  4. D

    Resolved How to fix Dirty Cow vulnerability in Plesk?

    I ran a test and discovered my Plesk system is vulnerable to Dirty Cow. What is the proper procedure to update Plesk to fix this issue? I have web admin and command line (root) access. The server runs CentOS 7 and Plesk 12.5 Thanks in advance.
Back
Top