• Resolved suslik495

    (@suslik495)


    Good days, a couple of days ago there was a problem that everything that uses the REST API does not work correctly. When opening the media library, they are not displayed, when trying to add a new media file, an error occurs. AIOSEO also displays the REST API error. The site’s health page shows an error The REST API was unable to correctly process the context request parameter. At the same time, if you disable the Wordfence plugin, everything starts working correctly and without any problems. I added the site’s ip to Allowlisted IP addresses that bypass all rules, but that didn’t solve the problem. Also the Query monitor plugin displays an error: inet_pton(): Unrecognized address in wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/utils.php:28. Help with advice, please.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter suslik495

    (@suslik495)

    So far, Google has given me the only answer: in a related problem, it helped to set Use the Cloudflare “CF-Connecting-IP” HTTP header to get a visitor IP. Only use if you’re using Cloudflare. I set this to All Options – How does Wordfence get IPs since I use CloudFlare. Not sure if this is the right solution, but the rest api call error is gone.

    I’d just like to add, that this started happening recently for us too. We use CF and the “CF-Connecting-IP” is set. In the All options page, Wordfence seems to get the IP just fine, but on the frontend Query Monitor reports a

    Warning: inet_pton(): Unrecognized address
    in: wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/utils.php:28
    component: Plugin: query-monitor

    WF version: 7.5.7
    QM version: 3.8.2
    WP version: 5.5.8

    Plugin Support wfphil

    (@wfphil)

    Hi @suslik495

    Thank you for the update that it is resolved.

    @glash – As per forum guidelines below can you open your own topic please:

    “Unless users have the exact same version of WordPress on the same physical server hosted by the same hosts with the same plugins, theme, and configurations, then the odds are the solution for one user will not be the same for another. For this reason, we recommend people start their own topics.”
    six

    @wfphil Sure, will do 🙂

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

The topic ‘Wordfence blocking Rest API’ is closed to new replies.