• Resolved joshmacd

    (@joshmacd)


    Steps Taken:

    1. Basic Network Connectivity and DNS: Confirmed general internet connectivity through successful pings. Verified DNS resolution for both domain names and IP addresses.
    2. Firewall Check (iptables): Checked iptables and confirmed that the firewall rules are permissive (all policies set to ACCEPT).
    3. Traceroute Analysis: Conducted traceroute tests to external IP addresses (8.8.8.8 and 44.239.130.172) to ensure a successful network path.
    4. Diagnostics for Specific Services (Wordfence): Checked Wordfence settings in the WordPress admin dashboard. Ensured that PHP configuration allows outbound connections.

    Observations:

    1. Connection to Specified IP Addresses: Attempts to connect to the specified Wordfence scanning server IP addresses (44.239.130.172, 44.238.191.15, 35.155.126.231, 54.68.32.247, 44.235.211.232, 54.71.203.174) were unsuccessful. Both via “ping” and “telnet”.

    Next Steps (Based on Wordfence Documentation):

    1. Start Scans Remotely: Attempt to start scans remotely by enabling the option “Start all scans remotely” in the “Debugging Options” on the Wordfence “Diagnostics” tab.
    2. Check Plugins: Ensure that no “Under Construction” plugin is blocking access to the WordPress AJAX handler.
    3. Check wp-admin Password Protection: Confirm that there is no secondary password protecting access to the “wp-admin” directory.
    4. Check Server IP Blocking: Investigate why connections to Wordfence scanning server IP addresses are not successful. Again, telnet and ping doesn’t work specifically on WordFence IP addresses, but traceroute does.
    5. Check Database Tables: Check for table corruption in the database, especially tables ending in “wfstatus.” Repair any crashed tables.
    6. Check WordPress AJAX Handler: Verify that the WordPress AJAX handler is working by accessing example.com/wp-admin/admin-ajax.php. Ensure it returns a blank page with a “0” in the top left corner.

    Problem:

    Despite successful network connectivity and permissive firewall rules, attempts to connect to Wordfence scanning server IP addresses are failing. This is impeding the initiation of Wordfence scans.

    Please advise next steps.

    • This topic was modified 1 year, 4 months ago by joshmacd.
Viewing 1 replies (of 1 total)
  • Plugin Support wfmark

    (@wfmark)

    Hello @joshmacd, thanks for reaching out and sharing the troubleshooting steps you have taken so far.

    If you could please do the following steps for me:

    • Go to the Wordfence > Tools > Diagnostics page
    • In the “Debugging Options” section check the circle “Enable debugging mode” 
    • Click to “Save Changes”.
    • CANCEL any current scan and start a NEW scan
    • Copy the last 20 lines from the Log (click the “Show Log” link) or so of the activity log once the scan finishes and paste them in this post.

    Wordfence > Tools > Diagnostic > Debugging Screenshot

    This will help me see exactly what is happening when the scan fails.

    Additionally, can you please 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.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks,

    Mark.

Viewing 1 replies (of 1 total)
  • The topic ‘Unable to Connect to Wordfence Scanning Servers’ is closed to new replies.