Hi @samtech456, thanks for reaching out.
The site scan and rules updates will be two separate processes although both are likely be affected by any connectivity issues you’re seeing. The 403 response certainly does seem like the request is blocked before any site content is served. It’s worth checking all IPs associated with your server are correct in Cloudflare’s whitelist (Check Wordfence > Tools > Diagnostics > IP(s) used by this server)
Also take note of your IP – (note that this detection can sometimes not be 100% accurate on cellular phone network connections): https://www.whatsmyip.org
Head over 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.”
When you added your server IP to Cloudflare, was it through the Cloudflare control panel like this?
- Login to Cloudflare
- Go to “Firewall”
- Click the “Firewall Rules” tab
- Click “Create a Firewall rule”
- Name the rule under “Rule Name”
- Set the “Field” under “When incoming requests match…” to “IP Source Address”
- Enter your site’s IP address under “Value”
- At the bottom, under “Then…Choose an action” change “Block” to “Allow”
- Click “Deploy
If so, sometimes adding our IPs here too can help. For your convenience, all of our IPs can be found here: https://www.wordfence.com/help/advanced/#servers-and-ip-range
Let me know how you get on,
Peter.
