deadparrotsoftware

There is no “pattern” – it is just a log file naming the virus IT (the ninja firewall) detected by name. Wordfence firewall, ironically, does NOT report the virus found.

The Problem is, that Ninja creates a new log daily – with a new name. And EVERY day, wordfence sees ‘patterns’ in the new log, and issues a warning. We have HUNDREDS of these false warnings!

Sid B.

Screenshot? The warning was IN the email I posted here above – and yes it IS incorrect! the email from wordfence says:

This email was sent from your website “Appbuzzinga” by the Wordfence plugin.
Wordfence found the following new issues on “Appbuzzinga”.

Alert generated at Wednesday 10th of August 2016 at 04:53:29 AM

Critical Problems:

* File appears to be malicious: wp-content/nfwlog/firewall_2016-07.php

Sid B.

That is the mystery – we did not upload them, and we are running the server on Linux. But you are correct – they are normal MAC files – nothing weird about the files themselves. It is a mystery.

Also note that your software listed the ninja firewall file as malicious malware, which it is not.

Sid

yes I tried that – they were not helpful. In a previous help call to them, we gave them access to our production site – and they just started turning plugins on and off without warning (or permission) – including our security plugins! Created no end of havoc on our production site.

As it turns out, we discovered the cause – remnants that were left behind when we deleted the plugin, including entries in the SYSTEM cron, which on our server should NOT have been possible. Yet, there they were! DOZENS of them.
(which were causing THAT log and the php error log to fill up fast)

At any rate, thank you for your response. Fortunately, we ferreted out all the culprits and returned our server to a normal state.

Again, thanks. ??

Sid B.
VP Dead Parrot Software Inc.

Page load speed is not the ONLY way a chat can impact a server – we tested one that, after 3 days, had created SO many temp files it used up ALL the inodes available in the tmp directory and locked up the server.

Sid B.

It was updated a week ago.

Not sure what “meaningful” means, but obviously the creators are still out there doing something . . . except addressing this problem that is. ??

Sid

As I stated in previous replies, WE are the hoster (dedicated server), and no, there was not a previous snapshot, as we had NO inkling that merely turning the plugin off and back on would cause a catastrophic failure! (It ran for a month with NO issues after we configured it)

Sid B.

Normally, we would just uninstall and re-install.

But we spent days configuring w3 to get the max speed. Stupidly, we did not save the settings before we turned it off to test same pages with no cache on – we had NO idea the damn thing would just crash with a fatal error so you can NOT re-activate it.

Sid B.

As we said, memcache was working with W3 – so YES, it was and is installed and running just fine.

We were NOT using object caching. But since W3 gives a FATAL error and does not restart, you can not check settings.

To repeat: W3 was installed AND WORKING WITH Memcache. We JUST turned it off momentarily to run speed tests, and got the fatal error when we re-activated.

We made NO changes, NO installs, NO adjustments. Just ran some speed tests on pages using test sites such as pingdom

Sid B.

Seriously? Your contribution is to point out a spelling error?

We do – we use s2member

Sid

I didn’t. I set it to 1. Have no idea how it has 5.

We own the server. We have both root and admin access, and all our other plugins write to that directory without any issues at all. It is NOT a permissions thing – and yes, we double checked that. And the logs I posted before ARE what it shows after we try saving.

And while I understand this is not a “make a living” thing, people are more inclined to donate when things actually work. We have 14,300+ WP users on our list, but we can’t evaluate for them how well the plugin works because we can’t get the file to load the program it needs.

Based on the debug we already ran, the plugin is faulting before it even tries to write the file – i.e., it never reaches the point of trying to write the file. The error is occuring BEFORE that point. I am guessing that some condition that needs to be met before the cache php is actually written is either not being met or not even being tested.

Sid

We are still getting the message

“Advanced cache file is yet to be generated, please save ? WP-FFPC Settings”

despite reviewing every settting multiple times and saving settings dozns of times.

We have not given a review or rating yet, but the plugin and support so far has been dissappointing.

Sid

The point of hiding it, is because of the brute force attacks occupying the site.

And that was my point. It is a membership site, with login and registration buttons everywhere. Every site has at least one button – linked to a url – people click to login, so it is hardly a secret. It would fool a bot that does NOT walk the site looking for the login link.

Sid