Support » Fixing WordPress » The authenticity of wordpress-5.5-no-content.zip could not be verified…

  • I updated three WordPress sites today (to version 5.5), all from the Admin Dashboard (Updates). In each case, the following message was displayed:

    “The authenticity of wordpress-5.5-no-content.zip could not be verified as no signature was found.”

    Should I worry bout this? The websites appear to be working fine so far. But, is there something I should check (or reinstall), just in case?

    TIA.

    • This topic was modified 3 months, 3 weeks ago by Jan Dembowski.
Viewing 15 replies - 1 through 15 (of 24 total)
  • Ditto.

    The same thing happened with me also

    Same here

    I refreshed three WordPress locales today (to adaptation 5.5), all from the Admin Dashboard (Updates)
    For each situation, the accompanying message was shown:

    “The credibility of WordPress-5.5-no-content.zip couldn’t be confirmed as no mark was found.”

    Would it be a good idea for me to stress the session this? The sites give off an impression of being working fine up until now. Be that as it may, is there something I should check (or reinstall), in the event of some unforeseen issue?

    • This reply was modified 3 months, 3 weeks ago by Yui.
    • This reply was modified 3 months, 3 weeks ago by Yui. Reason: link removed

    I’m getting the same error message “The authenticity of wordpress-5.5.zip could not be verified as no signature was found”?

    Anyone any ideas?

    Hello everyone! Thanks for pointing out this message.

    The WordPress team and contributors have been working on a way to cryptographically sign WordPress updates as a way to add an extra level of security when updating (which would verify the update package has not changed in transport from WordPress.org servers to your website’s server).

    This message will show until the approach is finalized and the code that verifies the signature is changed to require the verification to pass. Until then, there’s nothing to worry about! Your site is secure, and any issues that you may be experiencing are not highly likely to be unrelated to that message.

    I am getting the same problem during the update version 5.5 WordPress”The authenticity of WordPress-5.5-no-content.zip could not be verified as no signature was found.
    Unpacking the update… ”
    and also some plugins don’t working after updating WordPress version 5.5.
    Please suggest !!!

    I am getting a similar issue during the update adaptation 5.5 WordPress”The genuineness of WordPress-5.5-no-content.zip couldn’t be confirmed as no mark was found.

    Unloading the update… ” https://korean-drama-list.com/

    and furthermore, some modules don’t work in the wake of refreshing WordPress rendition 5.5.

    If it’s not too much trouble propose !!!

    Any Update regarding this issue “The authenticity of WordPress-5.5-no-content.zip could not be verified as no signature was found.
    Unpacking the update… ”

    While updating the site : Softwareinform.com

    Thank you, Jonathan Desrosiers (@desrosj), for your helpful reply!

    As you likely know, this upgrade messes with many plug-ins. Do you advise the use of the “Enable jQuery Migrate Helper” to try to mitigate that? The following is what I am referring to —

    https://news.thewindowsclub.com/wordpress-5-5-update-breaking-wp-plugins-102282/

    A response from you would be highly appreciated.

    Regards,

    – JC.

    Paging the Happiness Engineers!

    It’s been a week and I’m still getting the failure message. Sounds like 5.5 was released prematurely. Any idea as to when this will be cleared up?

    @thisistrue If you are experiencing the same issue as described above, please read through the discussion as the answers are found further up. If you are experiencing a different issue, please make a separate topic that describes your failure message in detail.

    Thanks, @desrosj, but I did review every post in this thread. Isn’t the very topic of this thread “The authenticity of wordpress-5.5-no-content.zip could not be verified as no signature was found.”? That’s exactly what I’m seeing. If you want the full error message, it is:

    Update WordPress
    Downloading update from https://downloads.wordpress.org/release/wordpress-5.5-no-content.zip…

    The authenticity of wordpress-5.5-no-content.zip could not be verified as no signature was found.

    Unpacking the update…

    Verifying the unpacked files…

    Preparing to install the latest version…

    The update cannot be installed because we will be unable to copy some files. This is usually due to inconsistent file permissions.: wp-includes/SimplePie/XML/Declaration/Parser.php

    Installation Failed

    …which I thought was what this thread was about. This is the only page Startpage can find with the string “The authenticity of wordpress-5.5-no-content.zip could not be verified as no signature was found.”

    I see that SimplePie is an RSS/Atom parser, but have no plugin by that name, and don’t recall ever installing it anywhere. And that said, a root file scan shows there are SimplePie files associated with many of my WP sites. So at this point, not having any idea what its function is in the WP world, I’m at a standstill.

    The update cannot be installed because we will be unable to copy some files. This is usually due to inconsistent file permissions.: wp-includes/SimplePie/XML/Declaration/Parser.php

    This is a separate issue. The SimplePie libary is shipped in WordPress core. The automatic upgrader is unable to replace that file when attempting to update.

    Can you try updating manually?

    What is “manually” in this instance? I’m “manually” clicking the update link in the front end, and am not sure how else to upgrade in place.

    I’ve definitely not done any changes in permissions of those files.

    (And I’d like to say I appreciate your quick and patient replies.)

Viewing 15 replies - 1 through 15 (of 24 total)
  • You must be logged in to reply to this topic.