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

Search results

  1. M

    Issue Error Upgrading MariaDB on CentOS 7

    Got it. Thanks for all the information.
  2. M

    Issue Error Upgrading MariaDB on CentOS 7

    One question though: should I try to upgrade to AlmaLinux instead? I guess that would make things... easier?
  3. M

    Issue Error Upgrading MariaDB on CentOS 7

    @Bitpalast well, that's exactly what I was trying to avoid: a manual update. I guess I'll have to give that try then.
  4. M

    Issue Error Upgrading MariaDB on CentOS 7

    I have just one: mariadb.repo
  5. M

    Issue Error Upgrading MariaDB on CentOS 7

    While trying to upgrade MariaDB 5.5.68 the process stops at the "Updating the server configuration" step with this error message:
  6. M

    Resolved Hostname Plesk proxied cloudflare

    Thank you @alapshin - that did the trick!
  7. M

    Resolved Cloudflare DNS not listing all domains despite Plesk article

    Well, then extend my gratitude to theme...
  8. M

    Resolved Cloudflare DNS not listing all domains despite Plesk article

    YES! That did the trick! Thank you Peter!
  9. M

    Resolved Cloudflare DNS not listing all domains despite Plesk article

    No it doesn't. Not even the section [ext-cloudflaredns] exists. Should I create it?
  10. M

    Resolved Cloudflare DNS not listing all domains despite Plesk article

    Yes. The domains exist in both Plesk as well as Cloudfare. This (awful) screenshot should give you an idea of the problem...
  11. M

    Resolved Cloudflare DNS not listing all domains despite Plesk article

    Yes, I did create the domains in Cloudfare... still, they don't show up in the extension so there's no way to "import" anything.
  12. M

    Resolved Cloudflare DNS not listing all domains despite Plesk article

    I have the same problem. There are several domains that do not show up under the Cloudfare DNS extension.
  13. M

    Resolved Client denied by server configuration

    I'm having the same issue as @Maarten. After upgrading to Plesk 18.0.52 it is not possible to access static content (.html, .txt for example) as it always returns 403 (forbidden). This error shows as "client denied by server configuration" entry in the error_log file. Note that this behavior...
Back
Top