mxmcreation

Hi @dsky,

Yes, it’s now fixed the issue in 2.1.3 and all is working as expected.

Thanks for your prompt help;-)

Resolved my previous issue by doing this:

– Temporarily assign Administrator role to the user
– Remove Administrator role and reassign Editor role
– Deactivate/activate ARMember plugin
– Clear all caches

Hi,

I’m using paid version of ARMember. And in regards to Q2: “Yes, ARMember does follow WordPress standards and you can assign ARMember page capabilities to the user” —> Not possible from my end.

I used User Role Editor Pro and for testing purposes I assigned all existing capabilities to Editor role (all available capabilities similar to admin role including ‘armember’), even with this done, ARMember is still not visible in WordPress dashboard for that role, but available for Administrator.

Could it be some other issue?

Hello,

Past 24 hours I’ve updated to latest version 5.152.3 and tested Spam Firewall with /?sfw_test_ip=10.10.10.10 appended to URL – it’s not working on our website, as well as tested on some other websites which use CleanTalk (5.152.3) and still not working. Also tested random non-existent email address in registration field and it didn’t react to it. I’ll do more testing on our site, because there is some flux in settings at the moment.

Are you sure it is functioning properly?

Hi,

Similar errors I see too. Recent updates messed it up.

Cheers

Thanks for your reply.

I’ll definitely consider upgrading to paid plan because in tech terms your plugin performs well, it utilises vulnerability database for checks and this is great idea. Wish it would cost slightly more affordable ??

@karmatosed

Thanks for reply!

I agree – new editor will be cool for many people once it’s developed.

Currently I’m running advanced WooCommerce store built with Visual Composer.

I’ve decided not to update to WP5.0 for certain period of time on my production server to see how things go with plugins and themes.
It would exhaust my business if we’ll need to recreate pages with another page builder..

Another my major concern here is that extra plugins (like “classic editor”) and mainly the whole new “block system” may create extra database complexity with extra queries which in turn may slow down some advanced sites on WordPress CMS, ie large e-commerce stores etc.

But hopefully, things will run smooth ??

Cheers

Hello @dagigt,

Hmmm, it’s funny indeed. Looks like there is a “tricky” bug, which has dependancies on certain events.

This raises the main question – is Wordfence really secure endpoint system?
Why it doesn’t alert me during the scheduled scan that ‘config.php’ changed ownership and now it’s not visible/accessible by WF, therefore firewall was disabled programmatically and not by user request?!
I mean, whatever happens to WF during installation/configuration (corrupted DB entry or file; conflicting setting etc) – WF should always check its integrity IMHO.

From this point of view, I don’t really feel safe with WF now, although I saw many positive reviews about it and Cloudways pre-install it on every new WordPress.

Btw good to know we are neighbours in cloudways with the same pathology ?? It makes it easier to trace.

I’ll wait till Monday for your update. Please let me know of any outcome and what is the solution, i hope it will work for us.

Hi @wfyann,

I’m a premium Wordfence user, extended protection is on.

I have exactly same problem. WF keeps resetting ‘wflogs/config.php’ ownership to root, making it unreadable for web user and automatically disarms WAF ?? It behaves like it was hacked or tries to hack itself. Please let me explain technically deeper, I was testing your plugin for couple of days in regards of this particular issue which I can’t fix..

This problem was detected on our server and currently active no matter what I’ve tried (tried this https://www.ads-software.com/support/topic/firewall-cant-write-to-wflogs-repeatedly-even-after-being-fixed/ and this https://www.ads-software.com/support/topic/unable-to-open-wflogsconfigphp-for-reading-and-writing/).

Our Wp Cron is disabled in wp-config.php (confirmed disabled status at ‘WF Diagnostics’ page). Currently Wp Cron is running on web server via cURL every 10 mins successfully.

Wordpress is running under web user (confirmed at ‘WF Diagnostics’ page). ‘wflogs’ permissions and ownership – web user, readable/writable by web user. I confirm that Wordfence can easily reach these files and modify them).

Root is not available on my server at cloudways, there is no direct root access for my cloud applications.

Daily (i assume during ‘wordfence_dailycron’ execution – but not 100% sure) something gets to ‘/wflogs/’ folder and changes ownership from web user to root ONLY for this file: ‘config.php’. This automatically switches off extended protection and firewall!

After it happens, I can delete ‘wflogs’ folder and WF will recreate new ‘wflogs’ with all necessary files ok with correct ownership.

I’ve installed Crontrol plugin to troubleshoot Wordfence wflogs behaviour. Strange thing is – if i execute hourly, daily, email report, scans and other WF crons – all works fine for me. Well, at least I couldn’t recreate this behaviour with manual runs.
However, the problem still exists and continuing to disarm WAF.

Could you please help us to resolve this problem? It drives me insane lately…