frankie9724
Forum Replies Created
-
To answer that last question I missed…
So what you did to fix it essentially was switch the setting to something different and then set it back?
I had this set to the top recommended setting and not cloudflare. You had me set it to cloudflare, but the scan report said it was misconfigured. It allowed me to select the recommended value. When I did this I noticed “Use the X-Real-IP HTTP header. Only use if you have a front-end proxy or spoofing may result” had been selected.
Everything looks good. Live traffic never stopped working. Those hundreds of bots from Singapore never seem to stop. I have been blocking them manually. At what point do I decide it is time for premium? How many bots are too many?
The IP is the one you gave me 162.241.252.164 IP. I have made sure it is allowed in rules by Cloudflare.
I have noticed since I selected “Use recommended value” To remedy the result (How does Wordfence get IP’s is misconfigured. TYPe: IP Detection. That under Wordfence options Cloudflare ClF Connecting IP is not longer selected.
Now this one is selected under Wordfence options ..Use the X-Real-IP HTTP header. Only use if you have a front-end proxy or spoofing may result. Is this one okay?
I will reach out to Bluehost on my correct IP.
To rememdy the result (How does Wordfence get IP’s is misconfigured. TYPe: IP Detection.
) I selected….Use recommended value which may have already corrected this.Can I enable Automatic scans for wordfence?
Can I turn back on WP Supercache and Smush plugins or atleast try?Almost there. Many Many Thanks for your Excellent Support. This was a tough one.
I have done what you asked with CF-Connecting IP. When I did this I receieved this message below.
Detected IP(s): 173.245.52.158
Your IP with this setting: 173.245.52.158Now the scanner DOES appear to be working with lots of pauses and in the scan results I see this…
How does Wordfence get IP’s is misconfigured. TYPe: IP Detection.
• Details: A test request to this website was detected on a different value for this setting. IP blocking and live traffic information may not be accurate. Get More Information This site appears to be behind a front-end proxy, so using the X-Real-IP HTTP header will resolve to the correct IPs.Do I need to go back to Cloudflare and add a third IP as 173.245.52.158? Can I remove the other IP’s that I allowed.
That is not the IP I added. At Bluehost it said 151.203.78.251, I just added 162.241.252.164 and it is still not working.
Enabled start scans remotely earlier.
I have deleted Wordfence entirely and reloaded as well.
Earlier in the month I was working on the site speed with Bluehost. We enabled Smush and WP Supercache which I have already disabled. I believe they optimized the database. They had me clear the cache in Cloudflare as well.
I do see a yellow triangle and ! next to the word Server when I start the scan.
I did add the site’s IP to the IP’s whitelist in Cloudflare and did not have any luck. This scanner has been down since 9/11 and I am concerned.
Much appreciate you help…