• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 TPlibraryWebmaster

  1. T

    Issue fail2ban.ipdns warning

    I apologize, I did not do a good job of explaining the issue. Fail2ban is working correctly with Modsecurity, exactly as you have described above. Additionally, that IP is correctly being caught and blocked, so it doesn't need to be whitelisted. I am specifically concerned about the...
  2. T

    Issue fail2ban.ipdns warning

    After updating from Onyx on two separate servers I'm receiving the following message in my fail2ban logs: 2020-02-25 09:32:00,864 fail2ban.filter [9022]: INFO [plesk-modsecurity] Found 107.77.207.56 - 2020-02-25 09:32:00 2020-02-25 11:20:40,767 fail2ban.ipdns [9022]: WARNING Unable...
Back
Top