[BUG] Checking WordPress updates fails: task is not responding: id=XX, pid=XXX, type=ext-wp-toolkit-mass-check-updates

Follow

Comments

9 comments

  • Avatar
    CharlieMPK

    Was trying to clone an old development site (created back in 2016) over to it's production domain. I was running into a similar issue. The Copying Files step would not complete. After resetting the administrator's credentials the migration completed!

    --

    CharlieMPK - Systems Administrator

    MPK Network Services

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello CharlieMPK

    Glad to hear this helped.

    0
    Comment actions Permalink
  • Avatar
    Tech01

    Also for anyone finding this to be a challenge and wanting a quick way to resolve. We detached all of our wordpress instances and scanned for them again (took a few tries) then highlighted them all since it also scanned for updates and did an update opposed to scan for updates which it's now working on. :) ENJOY

     

    0
    Comment actions Permalink
  • Avatar
    Tech01

    Sorry, one last note: The updates were successful however the wordpress instance is not showing the correct version of wordpress installed in the wordpress toolkit. It might show for some but a good handful of the sites are showing 5.1 even though they are updated to the latest version available. We can check that by logging into any individual site to see the current version is actually 5.3.2 but reported in toolkit as 5.1

    0
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy

    Hi Tech01, thanks for sharing that workaround. Could you open a support ticket with us in order to troubleshoot that issue with Wordpress version?

    0
    Comment actions Permalink
  • Avatar
    Tech01

    Submitted ticket, however we were eventually referred back to this original article for support. ..... 

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Tech01

    In such cases feel free to reopen support tickets.

    The ticket was reopened from our side.

    0
    Comment actions Permalink
  • Avatar
    Tech01

    The problem is that it is a known issue. The known issue thread told me to open a ticket. I opened ticket, some changes were made but we still have the same issue as the article here where we cannot mass update all the wordpress instances. This is a HUGE security risk that needs to be patched. We have a number of Wordpress instances that are likely out of date and need to be updated. Updating them individually would take way too long so we kindly request this issue be given the highest priority for resolution in the next plesk update.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Tech01

    Thank you for the clarification and feedback.

    Plesk Development team is collecting the information about reoccurring issues.

    However, the precise ETA is to be available later. 

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request