someone02
Forum Replies Created
-
Problems again (((
now something with api (((
Fatal error: Maximum execution time of 30 seconds exceeded in D:\xampp\htdocs\XXXXX\wp-content\plugins\wordfence\lib\wfAPI.php on line 143
also previously was an error in line 45
I set the “Maximum execution time for each scan stage” option to 20, but it’s not help
in “Scan Detailed Activity”
[Mar 06 00:27:23] Contacting Wordfence to initiate scan
[Mar 06 00:27:25] Getting plugin list from WordPress
[Mar 06 00:27:25] Found 24 plugins
[Mar 06 00:27:25] Getting theme list from WordPress
[Mar 06 00:27:25] Found 3 themes
[Mar 06 00:28:16] Fatal error: Maximum execution time of 30 seconds exceeded in D:\xampp\htdocs\XXXXXX\wp-content\plugins\wordfence\lib\wfAPI.php on line 143I understand that IP is not blocked.
the question was exactly about why history is kept so long and whether it is possible to adjust the frequency of its update in order to database was not very big?
“Block IP’s who send POST requests with blank User-Agent and Referer” is not marked (empty).ie I have on the local host “all hits” shows a more than 6 days. “login and logout” – 13 days.
on a real site “all hits” over a 15 hour, and the “page not found” – more than 5 days.
respectively, all this information is stored in the database and increases its size (((
where and how can I set the period of rotation of this information?Dear developers, I will be grateful if you could find a way to answer my questions.
thank you.TerryN, sorry, but where do you read that, you can block up to 60 days?
about permanent blocking – great opportunity to lock their osetiteley since I doubt that the bad guys have a dedicated ip addresses and use only them. And that is IP is dynamic, but now he’s a cracker, and a little later – a normal visitor.
If I understand correctly answer plugin authors above, the permanent blocking is not provided … or am I wrong?
have any idea?
If I understand correctly, you can not permanently block …
can be maximum 1 month.there is one thing ..
I apply the settings screens
blocking time is set for 30 minutes, but history shows more than 3 days in the tab “all hits” and more than 10 days on the “logins and logouts” (((
it is on the local hoston a live site – time – 5 minutes, see the story for 16 hours on the tab “all hits”, almost 2 days on “humans”, more than 2 days in the page “not found”
how is this possible?
thanks!
actual file permissions higher than the recommended (666 instead of 644 and 777 instead of 755).
on a live site have not tried
I am afraid that will fly settings and will have to re-configure all 🙁May be I try later
Forum: Plugins
In reply to: [All-In-One Security (AIOS) – Security and Firewall] Time in pluginon localhost and live site at the same time?
ok (((Forum: Plugins
In reply to: [All-In-One Security (AIOS) – Security and Firewall] 404 error. scannerWould be cool if you could implement it )))
1.8.3
Forum: Plugins
In reply to: [All-In-One Security (AIOS) – Security and Firewall] Time in pluginJust me with this question? )))
Win (XAMPP for win)
Forum: Plugins
In reply to: [All-In-One Security (AIOS) – Security and Firewall] Time in pluginyes )))
laptop
2:16WP UTC+3
2:16 (UTC 23:16)file name aiowps_2015-02-28_23-16.txt
