WordPress Toolkit scan fails with the error: Task is not responding: id=2133, pid=11088, type=ext-wp-toolkit-task\manage

Follow

Comments

7 comments

  • Avatar
    Liam Coyle

    Thanks for finding the bug and I hope the fix is available soon

    We are also moving accounts from this server to another plesk server to balance the load better

    0
    Comment actions Permalink
  • Avatar
    Tobias Steiner

    Dear Plesk team,

    just wanted to ask if there's a projected date for this bugfix available?

    thanks in advance, and all best!

    0
    Comment actions Permalink
  • Avatar
    Taras Ermoshin

    Hello Tobias Steiner!

    There is no ETA for bugfix available at the moment. Considering that the issue described in this article is quite rare, so could you please double-check that the issue you are facing is the same as described in the symptoms?

    If there are some additional symptoms, please search the knowledge base for similar articles and consider submitting a ticket to us.

    0
    Comment actions Permalink
  • Avatar
    Dharmadhar Behera

    after Domains > example.com > WordPress > Scan i am also getting same error.

     

    please help

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Dharmadhar Behera,

    In your case, there may be a different cause.

    I would suggest the following:

    1. Enable Plesk debug.

    2. Check Plesk panel log for more specific messages which may be searched in our knowledge base.

    In case this would not help, consider submitting a support request.

    0
    Comment actions Permalink
  • Avatar
    Glenn

    I'm getting this error just trying to clone a live site to staging on server with about 110 domains, lots of RAM and SSDs. It copied the files and failed at database copy stage. wp-config.php wasn't created on staging.

    0
    Comment actions Permalink
  • Avatar
    Alexey Lapshin

    Hello, @Glenn.
    I have to inform you that the issue with database copying during the site cloning is not related to the issue described here. I suggest you to submit a ticket in our system https://www.plesk.com/contact-us/ that we will be able to check the issue in place.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request