wp_remote_post() test back to this server failed, 400 Bad Request

  • Resolved abhaymorey

    (@abhaymorey)


    3 years, 2 months ago

    Hello Team,

    Recently we have changed hosting provider and migrated site. But after migration, Wordfence Scan is not working and we see below issue in diagnostic tab.

    HTTP/1.1 400 Bad Request
Connection: close
x-powered-by: PHP/7.4.11
content-type: text/html; charset=UTF-8
x-robots-tag: noindex
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
referrer-policy: strict-origin-when-cross-origin
x-litespeed-tag: 2ff_HTTP.400
expires: Wed, 11 Jan 1984 05:00:00 GMT
cache-control: no-cache, must-revalidate, max-age=0
x-litespeed-cache-control: no-cache
content-length: 5
content-encoding: br
vary: Accept-Encoding
date: Fri, 03 Sep 2021 05:32:14 GMT
server: LiteSpeed
content-security-policy: upgrade-insecure-requests
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"

    Please note that no issue with ajax files etc.
    Any assistance is appreciated.

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

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

    (@wfadam)

    Hello @abhaymorey and thanks for reaching out to us!

    It looks like its reporting an issue with connecting to the server. This could be with connecting to your server or connecting to our server.

    Make sure nothing is blocking these IPs on the host level:
    44.239.130.172
    44.238.191.15
    35.155.126.231

    Also, can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    Thanks again!

    Thread Starter abhaymorey

    (@abhaymorey)

    @wfadam Thanks, after adding above mentioned IPs, Scan is working fine now.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘wp_remote_post() test back to this server failed, 400 Bad Request’ is closed to new replies.