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

    Resolved Remove Wordpress Toolkit

    CentOS 6.9 (Final)‬ Plesk Onyx Version 17.5.3 Update #7, last updated on May 29, 2017 02:56 PM Is it possible to completely remove the Plesk Wordpress Toolkit ? I have asked many questions regarding this feature and several are still not solved after many weeks, perhaps even months I would...
  2. J

    Resolved Failed to update the ModSecurity rule set

    Plesk still complaining in control panel Centos 6.9 I don't know if this is related, but SSH & sFTP connections are VERY slow to connect Please advise
  3. J

    Resolved Failed to update the ModSecurity rule set

    This is the error i received when logging into Plesk today... Error: Failed to update the ModSecurity rule set: modsecurity_ctl failed: gpg: key 4520AFA9: "Atomicorp (Atomicorp Official Signing Key) <support@atomicorp.com>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 gpg...
  4. J

    Issue Plugin updates via Wordpress Toolkit show as successful but are not when checked in domain

    PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: Onyx 17.5.3 CentOS 6.9, 64-Bit Multisite PROBLEM DESCRIPTION: Plesk Wordpress Toolkit correctly identified a plugin required an update. That update was selected and applied via Toolkit, supposedly successfully On checking domains the update...
  5. J

    Issue Wordpress Toolkit incorrectly declaring an update required

    The Toolkit has many problems It also lists themes and plugins as inactive when they are active And it often does not pick up on required Theme updates, today being the latest example
  6. J

    Issue Wordpress Toolkit incorrectly declaring an update required

    Hello Aleksander WPMU DEV Dashboard plugin is installed WPMU DEV membership is currently active
  7. J

    Issue Wordpress Toolkit incorrectly declaring an update required

    Plesk Onyx Version 17.0.17 Update #20 CentOS 6.8 (Final)‬ Wordpress 4.7.3 Multisite: Wordpress Toolkit claims the plugin Membership 2 Pro 1.0.3.3 requires an update and links to the Wordpress plugin repository for the free version Membership 2 (4.0.1.2) This is not the same as the Pro version...
  8. J

    Issue Plesk Onyx Wordpress wrongly shows all plugins as inactive

    That is now 2 months and still no Toolkit that works properly Please advise
  9. J

    Issue Plesk Onyx Wordpress wrongly shows all plugins as inactive

    Thank you for your reply, I believe I covered all of the steps in your bug report template in my first post in this thread
  10. J

    Issue Plesk Onyx Wordpress wrongly shows all plugins as inactive

    Despite a small update to the Wordpress Toolkit this issue remain unresolved Is this the correct place to be asking about these problems or is there another platform to make Plesk Devs aware of problems with Plesk?
  11. J

    Issue Plesk Onyx Wordpress wrongly shows all plugins as inactive

    Thank you for confirming the issue Janko1000
  12. J

    Issue Plesk Onyx Wordpress wrongly shows all plugins as inactive

    It seems as if Plesk only recognises the status of Wordpress plugins if Wordpress is installed via the Plesk interface. The Synchronize facility makes no difference to a manually installed Wordpress instance.
  13. J

    Issue Plesk 12.5.30 to Onyx upgrade problem

    MU#13 has not resolved the problem
  14. J

    Issue Plesk 12.5.30 to Onyx upgrade problem

    Thank you for your reply Igor Can you perhaps tell me what other issues will be fixed in #13 as I have an outstanding issue with Plesk Wordpress Toolkit
  15. J

    Issue Plesk 12.5.30 to Onyx upgrade problem

    Thank you for the reply Jasper I perhaps did not explain myself very well I know how to exclude the epel repo and therefore the libopendkim update as it does not seem to be available from another repo I also know how to exclude only libopendkim The central problem is when will Plesk get...
  16. J

    Issue Plesk Onyx Wordpress wrongly shows all plugins as inactive

    Plesk Onyx Version 17.0.17 Update #12 CentOS 6.8 (Final)‬ Wordpress 4.71 Multisite: Plesk Wordpress manager shows all Wordpress plugins as inactive, but they are of course active and working. Is this a known issue?
  17. J

    Issue Plesk 12.5.30 to Onyx upgrade problem

    Unfortunately this is not an effective workaround I disabled the epel repo, ran yum check-update, and the update for libopendkim was not presented by any of the other repos
  18. J

    Issue Plesk 12.5.30 to Onyx upgrade problem

    Thank you for your reply Igor. It would be helpful to know the release date for MU#13
  19. J

    Resolved plesk is not compatible with libopendkim update

    I have the same error and unsure what steps to take to fix
  20. J

    Error when changing from 'no hosting' to 'Website hosting Plesk 12

    Simplest solution for me, although not the best one as it does not fix the core problem but at least gets the domains onlie and active - as they had no hosting I simply deleted them from plesk and re-added with hosting which seems to have solved the problem in the short term. I would still...
Back
Top