Error: Unable to accurately detect IPs

Same issue here. All sites on single server.

I have two anomalies on ALL my WP websites (all with WF installed) :

1. “[Dec 02 14:09:36] Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 7417692 bytes) in ****wp-content/plugins/wordfence/lib/wfConfig.php on line 442”

2. “Unable to accurately detect IPs”

They can’t ALL have suddenly run out of memory or IP clarity just like that…?

Stevo

• This reply was modified 7 years, 11 months ago by Stevo.
• This reply was modified 7 years, 11 months ago by Stevo.

(both directly after auto-update)

Same on my 20 websites…
Wordfecne Team: please answer us…
Thanks

Not sure about the IP issue.

But you can increase your PHP Memory limit by adding this line to your wp-config.php file right under the WP_DEBUG line:

define('WP_MEMORY_LIMIT', '512M');

That will at least let your scan complete on the site.

Thanks prd689,

But I have 25 sites on different servers – all showing BOTH issues!

I think this is a pure WF resolve.
S

@prd689
Already done since a long time ??

But now diagnostics said:

–Starting test–
Current maximum memory configured in php.ini: 512M
Current memory usage: 62.00M
Setting max memory to 90M.
Starting memory benchmark. Seeing an error after this line is not unusual. Read the error carefully
to determine how much memory your host allows. We have requested 90 megabytes.
<br />
<b>Fatal error</b>: Allowed memory size of 94371840 bytes exhausted (tried to allocate 33554440 bytes) in <b>/home/XXXXXXX/public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php</b> on line <b>4034</b>

It’s only occur on Wordfence 6.2.7, I have 15 others website with older version that works like a charm..

@sd142ppr
@pako69

I do agree that this is a WF issue with the new update. I also tried these things (from WF Support).

* Turn off the scan for scanning images and binaries as executable. This is really needed when you are looking for an active compromise but can be disabled until then. We’re making some improvements in this scan but currently it can be resource intensive

* Change the maximum execution time, near the bottom of the options page to a lower number, like 20.

* Try scanning in low resource mode. This scan takes longer to run but it greatly reduces load in the server and helps in situations where hosting providers limit memory and CPU.

They give their ip range 69.46.36.0 to 69.46.36.31 (https://docs.wordfence.com/en/Servers_and_IP_Range). It won’t take it as a range so I whitelisted (in Options) all their IPs. Just ran another scan and it went through fine so maybe this will work?
You can put them like this: 69.46.36.[0-31] under whitelist.

• This reply was modified 7 years, 11 months ago by dannette. Reason: added link to documentation
• This reply was modified 7 years, 11 months ago by dannette. Reason: new information

Same for me. Thought I’d chime in. So far, five of my 20 sites. All on VPS DreamHost.

@danette

“Whitelisted IPs must be separated by commas or placed on separate lines. You can specify ranges using the following format: 123.23.34.[1-50]”

So this should work too: 69.46.36.[0-31]

Same issue, three installations across two different hosting companies; following

Having the same error on one of two sites hosted with the same provider in the same account. Doing a manual scan raises the error only on one of the two sites.

Hi All,
Regarding this specific warning “Unable to accurately detect IPs”, it’s related to the new “Scan for misconfigured How does Wordfence get IPs” option introduced in the recent update, it could be because our servers didn’t manage to connect successfully to your website at certain point, so I suggest:
– Run a scan manually. If there was a temporary problem connecting to your site, this may clear the message.
– Make sure you are not blocking any IPs in Wordfence’s IP range. Check our servers and IP range.
– Deactivating and reactivating the plugin could help in clearing this warning as the same check is initiated upon plugin activation.
– If none of these worked, I suggest checking these steps mentioned on “Misconfigured How does Wordfence get IPs notice” page. (check them at the bottom of the page).

P.S. check my other reply here regarding the memory-related issues.

Thanks.

• This reply was modified 7 years, 11 months ago by wfalaa.

Updated to Wordfence 6.2.7 and received the warning Unable to accurately detect IPs as everyone else here has.

I worked my way through this documentation with no luck
https://docs.wordfence.com/en/Misconfigured_How_does_Wordfence_get_IPs_notice

Checked IP ranges, plugins, IP syntax (commas), settings, etc.

Still looking for anything else to try.