Fatal Error From Wordfence

  • Resolved denmBK

    (@denmbk)


    5 years, 4 months ago

    Started receiving the error below. Tried reinstalling a fresh copy but same issue.
    Any thoughts?

    Fatal error: Uncaught JsonException: Malformed UTF-8 characters, possibly incorrectly encoded in /usr/share/apm/src/Collector/Query.php:77 Stack trace: #0 /usr/share/apm/src/Collector/Query.php(77): json_encode(Array, 4194304) #1 /www/…………../public/wp-includes/wp-db.php(1949): Kinsta\ElasticAPM\Collector\Query->collect(‘SELECT * FROM ...') #2 /www/........../public/wp-includes/wp-db.php(2622): wpdb->query('SELECT * FROM…’) #3 /www/……/public/wp-content/plugins/wordfence/models/block/wfBlock.php(979): wpdb->get_row(‘SELECT * FROM `…’, ‘ARRAY_A’) #4 /www/……/public/wp-content/plugins/wordfence/lib/wordfenceClass.php(1199): wfBlock::lockoutForIP(‘66.108.8.205’) #5 /www/………/public/wp-content/plugins/wordfence/wordfence.php(95): wordfence::install_actions() #6 /www/………../public/wp-admin/includes/plugin.php(2299): include(‘/www/trendandch…’) #7 /www/…………/public/wp-admin/plugins.php(191): plugin_sandbox_scrape(‘word in /usr/share/apm/src/Collector/Query.php on line 77

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support WFAdam

    (@wfadam)

    5 years, 4 months ago

    Hello @denmbk and thanks for reaching out to us!

    It looks like you might be using a tool that records SQL queries, and it’s not handling binary characters that we use in the query (representing an IP). They should be valid in the query itself.
    ​
    I suspect it’s this: https://kinsta.com/apm-tool/ based on ElasticAPM in the error message. If it stops occurring when you turn that off, you will want to ask the host about it.
    It might not be related to updating to WP 5.6, but rather to a specific IP being in the block list. (If its binary representation looks like UTF-8 but it’s an invalid character, it may cause an error like that).

    Reach out to them to see what might be causing this issue.

    Thanks!

    Thread Starter denmBK

    (@denmbk)

    5 years, 4 months ago

    You were correct about the Kinsta APM tool. Our site went down so we enabled that to try to get some info. After restarting PHP we still had that activated and Wordfence is not compatible so the site crashed. We turned of APM and re-enabled Wordfence and now it is working fine again.

    Thanks for your assistance.

    Plugin Support WFAdam

    (@wfadam)

    5 years, 4 months ago

    Thanks for the update @denmbk

    Hope they can resolve that soon as we have had quite a few people reach out about that.

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

The topic ‘Fatal Error From Wordfence’ is closed to new replies.