Peter Smits

Hi thanks for your answer.

After installing it on three of my sites, all three I could not block IP’s from the 404 pages list. Then I went to another site which I did not update. There I could pick a IP from the 404 list and blacklist it. On this site it is working as expected.

On the sites where it does not work, after clicking the screen is refreshed, but there is no indication in the list that the IP is blocked afterwards.

I believe this has nothing to do with the plugin. You are using xammp on Windows as local environment. Xammp has a config file, and I believe the folder path for WordPress is not 100% ok. The site is running obviously, but the plugin picks up the wrong value, or does not find it.

Maybe this helps finding the cause of the problem

• This reply was modified 1 year, 9 months ago by Peter Smits.

hi @chmichael

the colors do change if you toggle to move/duplicate.

could you test with a different theme, because I suspect that your theme is causing problems (active user of the addon)

regards,

peter

Hi,

After checking the last period, the problem did not occur again.
I think that it might be caused by the fact that the IP was on two pages further in the list when I blocked it. So when deleting the first page after checking, I noticed the same IP on some pages further away.
So this issue can be closed for now
Regards,

Hi,
I may have found the reason why the page is not working
This is what I found in the server log
[Tue Nov 22 10:09:41.581359 2022] [:error] [pid 8029:tid 139702778644224] [client 5.132.73.70:33712] [client 5.132.73.70] ModSecurity: [file "/etc/httpd/conf/modsecurity.d/rules/tortix/modsec/10_asl_rules.conf"] [line "523"] [id "340165"] [rev "292"] [msg "Atomicorp.com WAF Rules: Uniencoded possible Remote File Injection attempt in URI (AE)"] [data "/wp-json/wp-statistics/v2/hit?_=1669067933&_wpnonce=f97f6fb512&wp_statistics_hit_rest=yes&referred=https://xxxx.com&exclusion_match=no&exclusion_reason&track_all=1&current_page_type=home&current_page_id=8&search_query&page_uri=/"] [severity "CRITICAL"] Access denied with code 403 (phase 2). Pattern match "=(?:ogg|tls|ssl|gopher|file|data|php|zlib|zip|glob|s3|phar|rar|s(?:sh2?|cp)|dict|expect|(?:ht|f)tps?)://" at REQUEST_URI. [hostname "psmits.com"] [uri "/wp-json/wp-statistics/v2/hit"] [unique_id "Y3yR1R6Bebl7NE3b6KPq6gAAABQ"], referer: https://xxxx.com/

Seems that the server is blocking the page due to what they call a “Injection attempt”

I checked your suggestion, but there are no XHR errors to see in Network
The below lines are from my console
`jquery.js?ver=3.6.1:10135 XHR finished loading: POST “https://xxxx.com/wp-admin/admin-ajax.php”.
send @ jquery.js?ver=3.6.1:10135
ajax @ jquery.js?ver=3.6.1:9716
jQuery.ajax @ jquery-migrate.js?ver=3.3.2:305
connect @ heartbeat.js?ver=6.1.1:416
(anonymous) @ heartbeat.js?ver=6.1.1:511
Navigated to https://xxxx.com/wp-admin/admin.php?page=wps_overview_page
jquery-migrate.js?ver=3.3.2:69 JQMIGRATE: Migrate is installed with logging active, version 3.3.2
jquery.js?ver=3.6.1:3832 [Violation] ‘setTimeout’ handler took 82ms
jquery.js?ver=3.6.1:3832 [Violation] ‘setTimeout’ handler took 71ms
jquery.js?ver=3.6.1:3832 [Violation] ‘setTimeout’ handler took 181ms
jquery.js?ver=3.6.1:3832 [Violation] ‘setTimeout’ handler took 65ms
[Violation] Forced reflow while executing JavaScript took 37ms
jquery.js?ver=3.6.1:3832 [Violation] ‘setTimeout’ handler took 63ms
jquery.js?ver=3.6.1:10135 XHR finished loading: GET “https://xxxx.com/wp-json/wp-statistics/v2/metabox?name=summary&_=1669110277078”.
send @ jquery.js?ver=3.6.1:10135
ajax @ jquery.js?ver=3.6.1:9716
jQuery.ajax @ jquery-migrate.js?ver=3.3.2:305
t @ admin.min.js?ver=1669110276:1
c.ajaxq @ admin.min.js?ver=1669110276:1
d.ajaxQ @ admin.min.js?ver=1669110276:1
d.run_meta_box @ admin.min.js?ver=1669110276:1
(anonymous) @ admin.min.js?ver=1669110276:1
d.run_meta_boxes @ admin.min.js?ver=1669110276:1
(anonymous) @ admin.min.js?ver=1669110276:1
mightThrow @ jquery.js?ver=3.6.1:3766
process @ jquery.js?ver=3.6.1:3834
setTimeout (async)
(anonymous) @ jquery.js?ver=3.6.1:3872
fire @ jquery.js?ver=3.6.1:3500
fireWith @ jquery.js?ver=3.6.1:3630
fire @ jquery.js?ver=3.6.1:3638
fire @ jquery.js?ver=3.6.1:3500
fireWith @ jquery.js?ver=3.6.1:3630
ready @ jquery.js?ver=3.6.1:4110
completed @ jquery.js?ver=3.6.1:4120
chunk-frontend-vendors.js?ver=1669110276:13 XHR finished loading: POST “https://xxxx.com/wp-admin/admin-ajax.php”.
(anonymous) @ chunk-frontend-vendors.js?ver=1669110276:13
t.exports @ chunk-frontend-vendors.js?ver=1669110276:13
t.exports @ chunk-frontend-vendors.js?ver=1669110276:13
Promise.then (async)
c.request @ chunk-frontend-vendors.js?ver=1669110276:1
o.forEach.c.<computed> @ chunk-frontend-vendors.js?ver=1669110276:1
(anonymous) @ chunk-frontend-vendors.js?ver=1669110276:1
(anonymous) @ chunk-common.js?ver=1669110276:1
a @ chunk-common.js?ver=1669110276:1
Rt @ chunk-common.js?ver=1669110276:1
(anonymous) @ chunk-frontend-vendors.js?ver=1669110276:13
y.dispatch @ chunk-frontend-vendors.js?ver=1669110276:13
dispatch @ chunk-frontend-vendors.js?ver=1669110276:13
(anonymous) @ frontend.js?ver=1669110276:1
(anonymous) @ chunk-common.js?ver=1669110276:1
tryCatch @ regenerator-runtime.js?ver=0.13.9:63
invoke @ regenerator-runtime.js?ver=0.13.9:294
(anonymous) @ regenerator-runtime.js?ver=0.13.9:119
r @ chunk-frontend-vendors.js?ver=1669110276:20
c @ chunk-frontend-vendors.js?ver=1669110276:20
(anonymous) @ chunk-frontend-vendors.js?ver=1669110276:20
(anonymous) @ chunk-frontend-vendors.js?ver=1669110276:20
(anonymous) @ chunk-common.js?ver=1669110276:1
(anonymous) @ chunk-frontend-vendors.js?ver=1669110276:13
y.dispatch @ chunk-frontend-vendors.js?ver=1669110276:13
dispatch @ chunk-frontend-vendors.js?ver=1669110276:13
o.dispatch @ chunk-frontend-vendors.js?ver=1669110276:13
ye @ chunk-common.js?ver=1669110276:1
(anonymous) @ chunk-frontend-vendors.js?ver=1669110276:13
y.dispatch @ chunk-frontend-vendors.js?ver=1669110276:13
dispatch @ chunk-frontend-vendors.js?ver=1669110276:13
mounted @ frontend.js?ver=1669110276:1
ne @ chunk-frontend-vendors.js?ver=1669110276:7
Un @ chunk-frontend-vendors.js?ver=1669110276:7
In @ chunk-frontend-vendors.js?ver=1669110276:7
Sr.$mount @ chunk-frontend-vendors.js?ver=1669110276:7
(anonymous) @ frontend.js?ver=1669110276:1
load (async)
d67f @ frontend.js?ver=1669110276:1
i @ frontend.js?ver=1669110276:1
4 @ frontend.js?ver=1669110276:1
i @ frontend.js?ver=1669110276:1
n @ frontend.js?ver=1669110276:1
(anonymous) @ frontend.js?ver=1669110276:1
(anonymous) @ frontend.js?ver=1669110276:1
jquery.js?ver=3.6.1:10135 XHR finished loading: GET “https://xxxx.com/wp-json/wp-statistics/v2/metabox?name=browsers&_=1669110277079&#8221;.
send @ jquery.js?ver=3.6.1:10135
ajax @ jquery.js?ver=3.6.1:9716
jQuery.ajax @ jquery-migrate.js?ver=3.3.2:305
t @ admin.min.js?ver=1669110276:1
i @ admin.min.js?ver=1669110276:1
fire @ jquery.js?ver=3.6.1:3500
fireWith @ jquery.js?ver=3.6.1:3630
done @ jquery.js?ver=3.6.1:9822
(anonymous) @ jquery.js?ver=3.6.1:10083
load (async)
send @ jquery.js?ver=3.6.1:10102
ajax @ jquery.js?ver=3.6.1:9716
jQuery.ajax @ jquery-migrate.js?ver=3.3.2:305
t @ admin.min.js?ver=1669110276:1
c.ajaxq @ admin.min.js?ver=1669110276:1
d.ajaxQ @ admin.min.js?ver=1669110276:1
d.run_meta_box @ admin.min.js?ver=1669110276:1
(anonymous) @ admin.min.js?ver=1669110276:1
d.run_meta_boxes @ admin.min.js?ver=1669110276:1
(anonymous) @ admin.min.js?ver=1669110276:1
mightThrow @ jquery.js?ver=3.6.1:3766
process @ jquery.js?ver=3.6.1:3834
setTimeout (async)
(anonymous) @ jquery.js?ver=3.6.1:3872
fire @ jquery.js?ver=3.6.1:3500
fireWith @ jquery.js?ver=3.6.1:3630
fire @ jquery.js?ver=3.6.1:3638
fire @ jquery.js?ver=3.6.1:3500
fireWith @ jquery.js?ver=3.6.1:3630
ready @ jquery.js?ver=3.6.1:4110
completed @ jquery.js?ver=3.6.1:4120

Hi @fendervr ,

Do you have security and other blocking addons installed?
Try again after disabling all your active addons
Maybe that helps
Regards Peter

@hjogiupdraftplus

Answers to your questions.
Currently I do not have an Ip as example, so have to wait for it.
Yes I have a htaccess enabled as all the commands I added to it via All in One Security are within htaccess.
Regards,

Hi @pedromendonca,

Well done with the new version no more errors, and the statistics are shown pretty quick!
No more errors within my debug.log

Thanks for your efforts

Hi,

Yes that is what I understood.
These errors are within my debug.log
I can see that the errors are generated, because within the plugin list, the spinner keeps turning at a plugin. Others do get a result. It is not a specific plugin that causes this, it is the amount of plugins selected to fetch the data for.
If I only have one or two plugins selected, then it works as expected. The server seems to run out of memory when more then a couple of plugins are selected

Hi Pedro,
I installed the new version, but the problem persists
This is a piece of the log

[07-Nov-2022 18:11:42 UTC] PHP Notice:  include_once(): Read of 1659 bytes failed with errno=12 Cannot allocate memory in plugins/so-widgets-bundle/widgets/slider/slider.php on line 10
[07-Nov-2022 18:11:42 UTC] PHP Notice:  file_get_contents(): Read of 8192 bytes failed with errno=12 Cannot allocate memory in wp-includes/functions.php on line 6620
[07-Nov-2022 18:11:42 UTC] PHP Notice:  require(): Read of 7588 bytes failed with errno=12 Cannot allocate memory in /wp-content/themes/fameup/functions.php on line 16

/wp-includes/l10n.php(139): get_locale()
/httpdocs/wp-includes/l10n.php(766): determine_locale()
/wp-includes/load.php(1395): load_textdomain()
/wp-includes/class-wp-fatal-error-handler.php(174): wp_load_translations_early()
/wp-includes/class-wp-fatal-error-handler.php(154): WP_Fatal_Error_Handler->display_default_error_template()
/wp-includes/class-wp-fatal-error-handler.php(58): WP_Fatal_Error_Handler->display_error_template()
#6 [internal function]: WP_Fatal_Error_Handler->handle()

I removed pieces of text to not reveal my system

Hi Pedro,

Ok will test with this new version today.
The more plugins are selected then the problem starts. With only a few plugins selected it works.
My WordPress installation is running within a virtual server hosted somewhere else. I have another WordPress site, running on a different type of server, if the problem persists I will take that installation and test what happens.

Hi Pedro,

Further investigation reveals that it is the amount and size of the plugin that causes my problem
If I set Page Builder SiteOrigin to show stats together with several other smaller plugins, then my installation seems to run out of memory. If I remove Page Builder, but set UpdraftPlus active, the same problem as back again

Hi Pedro,

Here are my answers to your questions
I started with setting the plugins I want to see the details for
My installation is running on PHP 8.0
My WP version is 6.1 the latest.
The language locale is Dutch e.g. nl_NL
I have not yest tested with only Translation Stats active, but for that plugin stats are shown.
I have not customized any of the default settings of the plugin
I see several 500 errors and have the inpression that a memory problem is created when the plugin runs.
The next step is disable all plugins I do not directly need
With only Translation Stats, there are no errors.
It seems that one of the plugins within the settings is causing the problem
So I need to set them one by one to see which one is causing the crash

Hi Pedro,

Here are my answers to your questions
I started with setting the plugins I want to see the details for
My installation is running on PHP 8.0
My WP version is 6.1 the latest.
The language locale is Dutch e.g. nl_NL
I have not yest tested with only Translation Stats active, but for that plugin stats are shown.
I have not customized any of the default settings of the plugin
I see several 500 errors and have the inpression that a memory problem is created when the plugin runs.
The next step is disable all plugins I do not directly need