Plugin Update not working

  • Resolved attilla0815

    (@attilla0815)


    3 months ago

    we all know the api got hacked
    but still the new update works well

    i cant refresh the accountdata or even the cron cant be run

    i use php8.3-fpm and debian with apache

    [30-Dec-2025 07:07:42 UTC] PHP Warning: gzuncompress(): data error in /var/www/*/wp-content/plugins/mycryptocheckout/vendor/mycryptocheckout/api/src/v2/Account.php on line 53

    [30-Dec-2025 07:07:42 UTC] PHP Warning: Undefined property: stdClass::$currency_data in /var/www/*/wp-content/plugins/mycryptocheckout/vendor/mycryptocheckout/api/src/v2/Account.php on line 76

    [30-Dec-2025 07:07:42 UTC] PHP Warning: foreach() argument must be of type array|object, null given in /var/www/*/wp-content/plugins/mycryptocheckout/src/currencies_trait.php on line 48

    please help me .. or us..



Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author edward_plainview

    (@edward_plainview)

    3 months ago

    The official API was not hacked. Hackers recently targeted some sites that connect to our API, by sending “fake payloads” or spoofing connection data. V2.152 or greater implemented strict API IP Verification.

    The gzuncompress error is usually from not having any account data to refresh.

    If you are on the latest version of the plugin (2.154) and the refresh button doesn’t work, try the following:

    • Visit Admin > Settings > MyCryptocheckout
    • Global Settings tab
    • Enable debug mode
    • Visit the Account tab
    • Press the “delete account data” button
    • Refresh the account
    • You should now see your account data again
    • Disable debug mode

    If that doesn’t work, then go ahead and email us the domain of your webshop so we can check the API server logs to see what is going on.

    defythegrid

    (@defythegrid)

    3 months ago

    If you want to play the game of carefully worded denials – the end result was the same as a hack. We lost big money because your code wasn’t patched or you didn’t hire a pen tester to find these vulnerabilities. Though I knew after the fact that customer payments went to hackers accounts, I still fulfilled my customers orders. I think it’s time for you to take responsibility for your mistakes.

    Plugin Author edward_plainview

    (@edward_plainview)

    3 months ago

    The cause was apparently http / https problems with the webshop.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.