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

  1. N

    Vulnerabilities that does not exist

    I really like the quality and service of Plesk. They focus on useful tools. There are no functions just to be cool or just to have a buzzword in advertisement. The quality is fine so far. But telling it is on purpose to install an update a day later then everyone else really annoys me. It looks...
  2. N

    Vulnerabilities that does not exist

    Exactly the same bug here. Lol no. We disclosed several bugs here the last days and only got shady excuses.
  3. N

    Resolved Update data wrong and late

    I have 3 servers with Plesk and they all did the update to 6.2.2 this night between 2AM and 7AM. Plesk delayed the updates by around 20 hours compared to pages that do not use Plesk.
  4. N

    Resolved Update data wrong and late

    Seems all three issues are even worse than reported in my first post: I have five test pages outside of Plesk with extremely low traffic. All got their automatic updates to 6.2.2. See the screenshot of the mail from 14 hours ago. But all Plesk sites are still on 6.2.1 and Plesk does not even...
  5. N

    Vulnerabilities that does not exist

    https://core.trac.wordpress.org/ticket/57363#comment:4 Now I fond something. The Wordpress Dev says yeah the bug exists but simply use a trusted DNS, send some good hopes with your prayers and maybe nobody will be affected. (Following this logic, no Wordpress page should use HTTPS as Wordpress'...
  6. N

    Vulnerabilities that does not exist

    Sorry after reading again, I am not sure any more. They say: "as they need more time to work on backports." What I read was: The Wordpress Maintainers think the bug is fixed in Wordpress 6 but had to fix Wordpress 5, too. I can't find an official statement from Wordpress or an independent proof...
  7. N

    Vulnerabilities that does not exist

    Plesk is wrong. The vulnerability is fixed in 5.9.3 according to the authors of the bug report. WordPress Core - Unauthenticated Blind SSRF | Sonar I get the message for a not existing WordPress UpdraftPlus PRO, too.
  8. N

    Resolved Update data wrong and late

    Hi! All my Wordpress sites show these warnings at the moment. Sorry I can't switch Plesk to English. There are several issues with this. My sites are in 6.2.1 but the current Core version is 6.2.2, not 6.2.1, Plesk does not provide the update. The bug shown is fixed in 5.9.3 according to the...
See more
Back
Top