Brian North
Forum Replies Created
-
Digital Ocean. Not shared.
Wordfence is blocking all 66.249.75.x GoogleBot visitors on my site for a few days now.
Just one example below…. [notwithstanding lack of productive src allowances by WP]
src=”http://itnorthwest.ca/img/dig-google.jpg”
That said, another Site at the same Host has no problems allowing all 66.249.65’s.
– i always seem to be baby-sitting WF. Unfortunate really.
Matt, as always, thanks for your concern and timely follow thrus.
I am now seeing 10’s of Pages not Found from the Same IP# and even though my options only allow 3 ‘Not Founds’ WF continues to allow these [various] unfound pages from the same IP#. This was not happening like this prior to the last update.
Also, in my Blocked IPs now I’m seeing tons and tons of “Blank user agent” and hardly any Pages not founds…
Definitely different behaviors being exhibited since the last update…
the “one-byte change” i can forget about for now thank you.
Unfortunately I am in Tech. support for over 25 years and it seems, these days, that Updates ‘surprises’ from Software vendors add to a constant ‘instability creep’. And also, a measurably growing consumer frustration that is not ‘monetizable’ for anyone.
The current trend of Software Updates are also an awful, yes awful, productivity loss – as I’m sure you are aware.
Thank you for bumping the OP’s issue to your programmers. Much appreciated and please forgive me if I don’t get too ‘into’ other, less major, Software issues.
also, as an addendum to this unrequited ‘write to htaccess file’ issue;
When ‘some’ other change is made to the WF Options – e.g. changing the block/lock timeouts from 20 to 10 days – WF writes a 1 byte change to the .htacess.
what is this 1 byte change please?
Confirmed – on new install after having cleared database and tables.
Made 2 entries into “Immediately block IP’s that access these URLs” and .htaccess was overwritten with new WF cachecode. [And yes, WF caching was turned off.]
Re: Prior Post – Apologies!! The problem lay between the keyboard and the chair!
I had never saved the option to ‘delete tables…’ on deactivation. Duh!!
I’ve deactivated, cleared tables and deleted.
then re-installed and WF just picked up ALL prior settings from the site! What’s with that?
I just wanted a clean install…
@wfbrian – after your proposed resolution – second paragraph above – URL Blocking is now [finally] working for me.
thank you much.
I’m off to Uninstall/Reinstall on a few more sites now…
@acekin thanks for the moral support there. Yes, I am constantly and frequently changing the “URL Block” field as I can’t figger why it’s not working for me! Despite the cachecode/htaccess issue does the “Immediately block IP’s…” work for you?
@wfmattr I have several times on a few sites removed this code and then, as the Immediately Block IP’s… isn’t working for me, I re-edit that field and thanks to acekin’s comment above, I find the cachecode back in my htaccess.
as an aside, the last time I did this [and only the last time] the site wouldn’t come back up with a php error line 15 or something. Searched the web and thousands of similar WF errors appeared.
Anyways I’m just off to see if the re-install of WF works for blocking IP’s accessing URL’s.
Thanks all for your input.
@wfbrian – thanks for the speedy response. Appreciate it much. To reply:
My blocks on IP Address times are 10 days for the Firewall Rules and 20 Days for the Login Security Options.
In addition, the WF Other Option clearly states “IMMEDIATELY block…”.
As can be seen in the OP screenshot the IP# in question is neither “immediately blocked” nor is it blocked for the 10 or 20 day period set in my WF Options.
Re: “have you had it running for a while?…”
Yes, it’s been up a while and fwiw I have other sites up even longer exhibiting the same behaviors..
Forum: Plugins
In reply to: W3 Super Cache vs WordfenceGood question!! I have the same 🙂
me too. fwiw all was fine, for me, before mid-january’s update. and now this [as the aboves]
