• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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