plugin Update/install Failed: http 500 plugin authenticity not verified

  • audioscavenger

    (@audioscavenger)


    4 years, 9 months ago

    hi

    Ever since I updated to WP 5.2.2, I get HTTP 500 whenever I install or update a plugin, even though the plugin updates/installs correctly! This happens on 2 different sites with and without Cloudflare.

    Version: 5.2.2
    Configuration:

    Memory: 8 of 128 MB (6%) | WP LIMIT: 40 MB | IP x.x.x.x (hostname) | PHP 7.2.19-1+ubuntu16.04.1+deb.sury.org+1 @64BitOS

    server: nginx + fastcgi
    PHP: zend op-cache activated
    memcached: no
    redis: no
    cloudflare: yes/no

    I activated debug mode and on the admin gui, i get this red debug message when I hit update a plugin:
    Update Failed: {"success":true,"data":{"update":"plugin","slug":"wp-statistics","oldVersion":"Version 12.6.5","newVersion":"Version 12.6.7","plugin":"wp-statistics\/wp-statistics.php","pluginName":"WP Statistics","debug":["Enabling Maintenance mode…","Downloading update from https:\/\/downloads.wordpress.org\/plugin\/wp-statistics.12.6.7.zip…","The authenticity of wp-statistics.12.6.7.zip could not be verified as no signature was found.","Unpacking the update…","Installing the latest version…","Removing the old version of the plugin…","Plugin updated successfully.","Disabling Maintenance mode…"]}}

    nginx log with http 500:
    www.domain.com - - username [08/Jul/2019:19:38:28 -0400] "POST /wp-admin/admin-ajax.php HTTP/2.0" 500 1047 1056 "https://www.domain.com/wp-admin/plugins.php" "user agent"

    I also installed health check as recommended and do not have this error when I update a plugin in troubleshooting mode.

    I also applied other recommendations such as re-apply permalink settings, purging op-cache/fastcgi/browser cache,etc, no luck

    what bothers me is the message

    “The authenticity of whateverplugin.zip could not be verified as no signature was found.”

    , I thought this was corrected in WP 5.2a1 ticket 46615?

    thanks for any idea, I spent quite some time without being able to figure out what the issue is

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Adrianna

    (@adriannagr)

    4 years, 9 months ago

    Hi,

    Such a message may indicate errors in the plugin. You can report the problem to the author of the plugin.

    choas

    (@choas)

    4 years, 9 months ago

    I have the same problem. WP Statistics plugin causes HTTP ERROR 500 in my WordPress control panel, especially in posting and plugins section.

    Thread Starter audioscavenger

    (@audioscavenger)

    4 years, 7 months ago

    hi all

    this error is still a thing. and yes i am up to date.
    Since WP version 5, I have this http POST 500 for every plugin update, even though update works fine every time.
    This creates a message under the plugin line, and interrupts updating of all plugins with a click. Example:
    Update Failed: {"success":true,"data":{"update":"plugin","slug":"advanced-iframe","oldVersion":"Version 3.0","newVersion":"Version 2019.7","plugin":"advanced-iframe\/advanced-iframe.php","pluginName":"Advanced iframe"}}

    I don’t understand the cause of this error 500 other than it’s linked to WP version 5 and beyond. My folders ACLs are correct as I use WP all in one security to check it.

    Absolutely everything else works. Just plugin update handled by wp-admin/admin-ajax.php returns error 500. All the response headers are returned correctly, and the JSON response returns true as you can see.

    Maybe one of the core php class has not updated correctly? Where should I look? Frontend is nginx and I never changed the website definition. I have a staging site with exactly the same issue.

    any idea is welcome 🙂

    Thread Starter audioscavenger

    (@audioscavenger)

    4 years, 6 months ago

    There are no issue updating plugins when I enable Troubleshooting mode from Site Health.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘plugin Update/install Failed: http 500 plugin authenticity not verified’ is closed to new replies.

Tags