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

  1. R

    Resolved Innodb corrupt after Plesk update

    Can you explain why Plesk actually did the MariaDB upgrade, even when system updates are deactivated? Does Plesk ignore these settings for some mandatory packages?
  2. R

    Resolved Innodb corrupt after Plesk update

    Autoinstaller did indeed the upgrade, despite auto updates are off (see attached image). Why is that? [2019-11-06 03:06:24.080488] Following bootstrapper packages will be installed: (empty) [2019-11-06 03:06:24.080506] ---------------- [2019-11-06 03:06:24.080519] Getting packages to...
  3. R

    Resolved Innodb corrupt after Plesk update

    How to prevent Plesk from doing this upgrade? We have this in our config, this does not prevent Plesk from updating MariaDB this night on several nodes: [updates] systemUpdatesTool = on
  4. R

    WordPress Toolkit update disaster

    The problem reappeared this night. How to fix that?
  5. R

    WordPress Toolkit update disaster

    Plesk or the WP Toolkit created these files exactly at 0:00 and did not remove them afterwards, so this seems to be Plesk update issue.
  6. R

    Resolved Error 503 on all site

    See Issue - WordPress Toolkit update disaster - you have to delete the .maintenance file and it should work again.
  7. R

    WordPress Toolkit update disaster

    We had the same issue on some of our servers. You have to delete the file named ".maintenance" in the webroot to resolve this. Plesk should look into this asap, this is a very important issue as it breaks customers websites.
  8. R

    Important Advisor Extension

    Yes, would be very good to have an option to disable this (for us) useless tool! Thanks!
  9. R

    Issue plesk-php-cleanuper does ignore session.gc_maxlifetime settings from Plesk own versions

    IMHO this is definitly not a feauture, but a serious bug in one of your scripts. Please consider to open a bug report for this.
  10. R

    Issue plesk-php-cleanuper does ignore session.gc_maxlifetime settings from Plesk own versions

    --------------------------------------------------------------- PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE - Plesk Onyx, CentOS 7, 64 Bit PROBLEM DESCRIPTION - The cron /etc/cron.hourly/plesk-php-cleanuper script does not respect session.gc_maxlifetime settings from Plesk PHP versions in...
  11. R

    Resolved plesk is not compatible with libopendkim update

    You're welcome! Good news ;-)
  12. R

    Resolved plesk is not compatible with libopendkim update

    Ok, added - please contact me directly to get the servers IP. Don't want to post it on this public forums. Thanks.
  13. R

    Resolved plesk is not compatible with libopendkim update

    No problem, please send us your SSH PubKey to support {at} robhost.de
  14. R

    Resolved plesk is not compatible with libopendkim update

    Any ETA for the next MU #14 with the fix included, finally?
  15. R

    Issue Plesk 12.5.30 to Onyx upgrade problem

    Problem still exists in repo. Why does this fix take so long? It prevents whole system from updating, which is a major security issue. Does Plesk QA not test against EPEL (which is a standard repo for RHEL and CentOS imho).
See more
Back
Top