• Resolved Valber

    (@valberfigueiredo)


    Wordfance does not complete verification. Starts and then for verification!

    https://ibb.co/QFh8Zyv

    I have Start all scans remotely enabled (Try this if your scans aren’t starting and your site is publicly accessible).

    And Wordfance is showing me the following error below:

    wp_remote_post () test back to this server failed! Response was: 403 Forbidden
    This additional info may help you diagnose the issue. The response headers we received were:

    https://ibb.co/MGZzSmJ

    I don’t know if there is a risk to send it here Additional Detail.

    If it is possible to send by email to check.

    Thanks in advance.

Viewing 15 replies - 1 through 15 (of 16 total)
  • Hey @valberfigueiredo,

    You sure can email the Doagnpstocs report over! Please navigate to Wordfence > Tools > Diagnostics. Here you can select SEND REPORT BY EMAIL. Please include your WordPress.org username and update this thread after you’ve sent it.

    Thanks,

    Gerroald

    Thread Starter Valber

    (@valberfigueiredo)

    Hello @WFGerroald thank you so much for trying to help me.

    E-mail Sent with Diagnostic.

    Very effective, easy and fast the procedure mentioned above … Too cool.

    I’m waiting, big hug and thanks for being available to help.

    Hey @valberfigueiredo,

    It looks like you a reCAPTCHA verification is needed to access the site. Can you please disable it and let me know if it helps?

    Please give this a try and let me know how it goes.

    Thanks,

    Gerroald

    Thread Starter Valber

    (@valberfigueiredo)

    I’m sorry for this.

    Please try again!

    Hey @valberfigueiredo,

    Did you have a chance to disable the CAPTCHA on your home page and try another scan?

    Please let me know.

    Thanks,

    Gerroald

    Thread Starter Valber

    (@valberfigueiredo)

    thanks for helping me.

    About doubt: Do you mean reCAPTCHA used for Ninja Forms plugin?

    Or reCAPTCHA configured in Wordfence?

    When in doubt I deactivated the 2 and tested it as you recommended and it still didn’t work … Couldn’t finish analysis. It started and already stopped informing the same warning message sent above.

    I noticed only now that when activating reCAPTCHA in Wordfence system, it warns me that the function is not compatible with the Woocommerce login page, so from now on I will have to leave it disabled 🙁

    Hey @valberfigueiredo,

    Looking at the source code I believe it’s the CAPTCHA created by Cloudflare that needs verification to even access the site. It’s possible you’re whitelisted and not seeing it, so I’m sharing a screenshot of what I’m seeing.

    Cloudflare CAPTCHA

    Can you take a look at your Cloudflare configuration and disable the CAPTCHA protection to see if it helps.

    https://support.cloudflare.com/hc/en-us/articles/200170136-Understanding-Cloudflare-Captcha

    Please let me know how it goes.

    Thanks,

    Gerroald

    • This reply was modified 4 years, 2 months ago by WFGerroald.
    Thread Starter Valber

    (@valberfigueiredo)

    It doesn’t really appear on this CAPTCHA page for me.

    And now I also disabled the option in cloudflare:

    Security level

    Adjust the security level of your site to determine which visitors will receive a challenge page.

    This is now disabled.

    But it still may not be enough.

    Could you pass me on in practice methods to give freedom of Wordfence to work without restriction.

    That is, IPs to add white list, or any other specific method for the wordfence work without risk of being restricted for some reason.

    Pass me and I will do it here … Because this looks like some cloudflare restriction.

    But on cloudflare I have now disabled everything.

    But even so, I want to prevent and avoid blockages in the future with wordfence.

    Hey @valberfigueiredo,

    I wish there was an all-in-one list I could share with you. But we don’t have one. Each site is different, there are many different services out there, and not all have static IPs.

    With that said, are you still getting the error?

    Thanks,

    Gerroald

    Thread Starter Valber

    (@valberfigueiredo)

    Yes … I’m still getting an error.

    Everything follows the same thing … Wordfence still can’t analyze website.

    I don’t know how to fix this … I’ll give up I think.

    If you want a Store Admin I will generate it for you and send it to you.

    I even send Cloudflare access if you want.

    In order to check everything in a more practical and easy way.

    Just send me private private email and I will pass on data to you.

    And thanks for the support.

    Thread Starter Valber

    (@valberfigueiredo)

    I noticed something now looking calmly.

    That warning I had before the image of the beginning of this topic in the forum

    The red one is gone and now at least it has normalized.

    Here image:

    From before:

    https://ibb.co/MGZzSmJ

    From now:

    https://ibb.co/9G7BbHB

    But for me, wordfence still can’t verify website.

    Hey @valberfigueiredo,

    Thanks for the update. This is definitely progress.

    Can you please screenshots of what you’re seeing now? You might try clearing all cache in case the previous error was cached.

    Can you also share an updated Diagnostic report? Please update this thread once you’ve as you did before.

    Thanks,

    Gerroald

    Thread Starter Valber

    (@valberfigueiredo)

    It practically follows the same thing.

    Just notice that it was this before:

    Here image:

    From before:

    https://ibb.co/MGZzSmJ

    From now:

    https://ibb.co/9G7BbHB

    At least this has normalized.
    But wordfence still fails to verify.

    And follow this same warning when checking:

    https://ibb.co/QFh8Zyv

    I always clear the server level cache via SSH.

    I also clear the cache on Cloudflare and the WPRocket plugin.

    This the second time it happened. First time I just activated:

    – Start all scans remotely (Try this if your scans aren’t starting and your site is publicly accessible).

    And normalized.

    But this time nothing I do seems to be of no use.

    Thread Starter Valber

    (@valberfigueiredo)

    And now this other warning appears:

    https://ibb.co/D7t9FdK

    Hey @valberfigueiredo,

    I know it may not seem like it, but this is still progress.

    Can you try deleting the rules.php file in wp-content/wflogs?

    Let Wordfence automatically regenerate the file (usually within 30 minutes) and see if the issue is resolved.

    Please let me know how it goes.

    Thanks,

    Gerroald

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘About connectivity Ability to connect to Wordfence servers and your own website.’ is closed to new replies.