Nikolay Nikolov

Actually I have made a horrible mistake :D. I just assumed the site is his, and now that I checked, it looks like there is another admin user in the site that is the owner and this admin user is added later somehow. It does make sense now to be a hacker. I will contact the other admin to see if he knows about this guy.

• This reply was modified 8 years, 2 months ago by Nikolay Nikolov.
• This reply was modified 8 years, 2 months ago by Nikolay Nikolov.

Well I tried making a user with one plugin that I have. I registered in the frontend via its form and then created a site, and scanned with WF but my test user was not found as created outside… So I don’t know how this other user made his user, but his site seems legit to me, so I am ignoring this.

• This reply was modified 8 years, 2 months ago by Nikolay Nikolov.

Yes, but how do you determine that this user is bad? What criteria? How is he different?

Looking at the code I cannot understand, too many functions and classes and no comments explaining the function… You are comparing logged admins and current admins, but what does this mean, logged admins and what is current admins?

I cannot believe that such popular plugin does not have this done. This is very important. When some user gets locked out from login for example, they see a message that they cannot read. I have to change the source code directly to translate ??

The slow sites are still around 20 sec for 100 files like my previous reply. The original issue was around 40 sec for 100 files. So I don’t know if this is solved or not.

Looking at the debugging mode data, I do not see anything strange or different on the slow site compared to the super fast site. Just everything is slower. There is not one given type of task that is slow, just everything. I do not see any errors too.

By the way at the moment the slow site that was like 40 sec for every 100 files is now around 20 sec. Maybe at the moment the server is less overloaded? I don’t know.

Could it be that just the two servers of the two sites are different in the hardware and that to cause such a huge difference in speed. I know that the faster site is on all SSD. Maybe this is the reason.

I got some more information. On some sites I manage the scan is super fast, and 6.2 is even faster. It scans 100 files for less than a second. On other sites it takes like 40 seconds. One of the things that the slow sites have in common is that they have like 2000 users. Maybe this has something to do with it.

Also everything in the diagnostics page is green, no errors.

Имам същия проблем. С най-новия wp и woo.

Thank you for all your help. I was finally able to finish a scan.
I set php max execution time to 60 and the wordfence setting to 30 and then it worked. Before that I tried php 60 and wordfence 20 and it still failed.
But I must say, this was not a great user experience ;). If you guys can come up with a way to improve this issue with the scan, it would be great.
Thanks.

Did it and still get the same: https://postimg.org/image/y7amaipf5/
The last hashing line said something about the wp-content folder, could it be that there is located a problematic file that causes this?

Still get the same error. Setting it to 20, 28 or 15 does not work.

Scan Scheduling is not even a feature I can use, since it is a free version. Here is the screenshot: https://postimg.org/image/run8z8xbl/

Thanks, debuging mode helps me see some things.

First thing is, I am constantly getting these for no reason:

[Jun 24 17:45:02:1466783102.957429:4:info] Scheduled time for day 6 hour 1 is: Saturday 25th of June 2016 01:40:51 AM
[Jun 24 17:45:02:1466783102.956003:4:info] Scheduled time for day 5 hour 1 is: Friday 1st of July 2016 01:58:00 AM
[Jun 24 17:45:02:1466783102.955159:4:info] Scheduled time for day 4 hour 1 is: Thursday 30th of June 2016 01:01:08 AM
[Jun 24 17:45:02:1466783102.953762:4:info] Scheduled time for day 3 hour 1 is: Wednesday 29th of June 2016 01:45:25 AM

And they go on and on. I have even turned off regular scans.

The second thing is, I got the idea to exclude from the scan the biggest directory and then I saw these without wating too long:

[Jun 24 18:02:33:1466784153.252340:1:error] <br /> <b>Fatal error</b>: Maximum execution time of 30 seconds exceeded in <b>/**************/wp-content/plugins/wordfence/lib/wordfenceHash.php</b> on line <b>181</b><br />
[Jun 24 18:02:15:1466784135.935538:4:info] Scan process ended after forking.

Then I excluded a few large files and even all rar and zip with *.zip and *.rar but it still got stuck. It would be helpfull if it says which file is the problem.

Hi.
They were turned off. The scan for heartbleed was also on the first time I tested this, but it was already finished in the status log. So the scan core files stage was the one that was scaning everything.

Today the firewall is showing disabled, so I guess the first issue is fixed somehow…