• Resolved Sha’ves

    (@shaves23)


    I moved from old hosting : 35.213.169.38 to a new hosting which has a different IP. All scans has been failing. Upon further checking, I found that under Tools >> Diagnostics >> Connectivity section was showing the following error:

    wp_remote_post() test back to this server failed! Response was: 400 Bad Request
    IP(s) used by this server : 35.213.169.38,127.0.0.1 (this is the old hosting IP address.)

    I’ve tried :
    1) Removing and reseting Wordfence (Delete Wordfence tables and data on deactivation) and retried, same old IP used.
    2) Removing and reseting Wordfence manually and retried, same old IP used.
    3) Wordfence Assistant : Remove all Wordfence Data in the Database and elsewhere and retried, same old IP used.

    As we were using CloudFlare, bypass CF by DNS Only option so request hits directly to the origin, repeat step 1,2 & 3 and retried, same old IP used.

    What am I missing? I would really appreciate if you could point me in the right direction.
    Thank you.

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

    (@wfadam)

    Hello @shaves23 and thanks for reaching out to us!

    To double-check your IP detection is correct, first, check the following site and take note of your IP: https://www.whatsmyip.org

    Then, head over to your site and go to Wordfence > All Options > General Wordfence Options > How does Wordfence get IPs and reference the area under that section that says Detected IPs and Your IP with this setting. Start from the top and check to see if any of the settings show that both of those show the same IP as the site above does.

    If you’re using Clourflare, you will most likely need to select “Use the Cloudflare “CF-Connecting-IP” HTTP header to get a visitor IP. Only use if you’re using Cloudflare.”.

    If this doesnt work, then reset Wordfence completely by:

    • Log in to your site via FTP/SSH or any file browser your web host may be providing.
    • Locate the folder “wordfence” in /wp-content/plugins
    • Delete the /wordfence/ folder
    • Go to WordPress Plugins page and install Wordfence. Activate (the new) Wordfence.

    This should retain your settings as well but you can also export your settings just in case.

    https://www.wordfence.com/help/advanced/remove-or-reset/#remove-or-reset is a great reference for resetting or removing Wordfence.

    Let me know if this helps!

    Thanks!

    Thread Starter Sha’ves

    (@shaves23)

    The issue was with SiteGround having two A records with different IP addresses (old and new) pointing to my domain. They were giving me a run around for 4 days by saying I need to get a developer’s assistance as this was an plugin issue and then another support guy said its CloudFront’s problem.

    So I disabled CF totally, pointed name servers back to SiteGround directly. The problem was obvious now, as the old site was loading because my domain was always pointing to the old IP.

    I highlighted this to Siteground and they had to delete the A record with old IP, as I couldn’t see it my CPanel’s DNS Zone Editor. After propagation my site was loading fine. Miraculously, Siteground staff apologized for their mistake.

    Wordfence scan works now as expected. Under diagnotics >> Connectivity >> Connecting back to the site says “Ok – with the correct IP address”.

    But, IP(s) used by this server was only refreshed to actual IP after a couple of days.

    Plugin Support WFAdam

    (@wfadam)

    Hello, again @shaves23 and thanks for responding back with the good news!

    For IP detections:
    To double-check your IP detection is correct, first, check the following site and take note of your IP: https://www.whatsmyip.org

    Then, head over to your site and go to Wordfence > All Options > General Wordfence Options > How does Wordfence get IPs and reference the area under that section that says Detected IPs and Your IP with this setting. Start from the top and check to see if any of the settings show that both of those show the same IP as the site above does.

    If you’re using Cloudflare, you will most likely need to select “Use the Cloudflare “CF-Connecting-IP” HTTP header to get a visitor IP. Only use if you’re using Cloudflare.”.

    Is this what you were looking for? Let us know if you run into any more issues!

    Thanks!

    Thread Starter Sha’ves

    (@shaves23)

    Hi Adam,

    I wasn’t encountering any issues with Client IP. This is going to return my IP: https://www.whatsmyip.org, not the server’s IP. The issue was all along with wrong SERVER IP detected by Wordfence, because of SiteGround misconfiguration.

    Refer to : https://imgur.com/DfOBk4N
    (The IPs are not actual IPs, it was generated using random IP generator and for illustration purpose only.)

    The red box is not a valid IP (the old IP). The green box is correct IP which got listed only after the wrong A record was removed. So now, how can this invalid IP be removed?

    Really appreciate your perseverance in assisting me in solving this issue.
    Thank you.

    • This reply was modified 5 years, 9 months ago by Sha'ves.
Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Wrong IP in Diagnostics >> Connectivity’ is closed to new replies.