Point release 6.1.3 out now – Update when you are able

slight improvement over yesterdays release.
now only the backend becomes unusable when wordfence enabled

Hi WFSupport,

Wordfence Plugin firewall is not working since upgraded to version 6.1.1 and later it has been upgraded to version 6.1.3 automatically but the plugin has stopped working completely and displaying an error mentioned below:

“Wordfence could not get an API key from the Wordfence scanning servers when it activated. You can try to fix this by going to the Wordfence “options” page and hitting “Save Changes”. This will cause Wordfence to retry fetching an API key for you. If you keep seeing this error it usually means your WordPress server can’t connect to our scanning servers. You can try asking your WordPress host to allow your WordPress server to connect to noc1.wordfence.com.”

I can able to view the file update log on the server wp-content/wflogs.php whenever I try to save the file setting of Wordfence [File permission is set to 0600 by default]

I’m on shared hosting plan and they aren’t blocking outgoing connection to noc1.wordfence.com.

I’m using Wordfence plugin since it’s released date but have faced no issues at all except in version 6.1.3.

Deleted, reinstalled, cache cleared but nothing seems to be fixing this issue.

Any help would be appreciated.

Hi,
After upgrading to wp4.5 and wf6.1.3 I’m getting the following log messages:

mod_fcgid: stderr: Unable to open /var/www/html/public_html/wp-content/wflogs/ips.php for reading and writing.

Checking permission for ips.php file I found that ips.php are located in
var/www/html/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/logs/ips.php

Please advise how to fix this.
Thank you,
A

After upgrading 6.1.3, I get this error while scanning: Scan can’t continue – stored data not found after a fork. Got type: boolean. I tried it on three different wordpress sites.

Live traffic not working after updating to 6.1.3. I’m on WordPress 4.5…

Seeing the same behavior as redisztribucio

I just wanted to let you know that there is a memory leak in live traffic when it’s enabled. I’ve spent 3 days tracing it down. Previously I thought it was the browser (FF) since both were updated at about the same time. If you need memory outputs email me. They are not anonymous so I won’t post them here.

With me monitoring two sites with live traffic I was getting browser lockups, slowed performance, non responsives, etc. I’m on version 4.5

BTW, it does take a few hours for this to happen in my case, the memory leak that is.

Experiencing the same as @bluebearmedia (same versions WP and WF)…

Just an update on the memory leak issue .. even when the traffic page is not set to LIVE, there is a memory leak that builds over time, so it’s not just live traffic monitoring, it’s also the applet when the traffic is turned off. WF version 6.1.3 on WP 4.5

Just as a follow-up… I reverted the site back to WordPress 4.4.2 and the blank Live Traffic problem disappeared with Wordfence 6.1.3.

Seems WF 6.1.3 doesn’t play nicely with WordPress 4.5, at the moment…

Similar issue for a large network site. On admin login, you do not have sufficient permissions to view this page. Restoring previous version plugin files restores admin access. When is it safe to update? Thanks in advance!

FYI .. the .4 update does not fix the memory leak in live traffic view in the slightest.

@breezyohio,

The problem you mention I don’t recognize (but that’s due to my lack of knowledge).

But for all the others who experience a blanc display in the Life Traffic: the solution is to check all your plugins. They all have to be compatible with WP4.5!! So de-activate all the plugins, except WF. Then one by one activate them, and each time check whether WF stays steady.

Then you will see WF is fantastically updated!!

Mandigit, The way to tell is to open your favorite browser, open task manager, and see the cpu usage. It’s easier to do it in FF because it’s a single file rather a series files like Chrome is.

Anyway, at any given time I have about a hundred tabs loaded up in FF .. displayed really .. they don’t load till you click them. Let’s say I have maybe 30 or 40 actually loaded.

If you have a “clean” FF installation it will sit there with next to no CPU usage. In my case that’s around 5% cpu, and and about a gig of memory because of all those tabs. It runs like that all day, day after day.

When I load my Wordfence Live traffic page though, cpu goes to 25-30%, and memory starts creeping up. An hour later my FF is slow to load or switch pages and the UI slows down. Another hour later I have to restart FF.

So there you go .. this is typical of what a memory leak looks like. Over time things deteriorate.