Mehmet

Hi @martinm76,

That’s a great suggestion thank you for sharing it!

You’re absolutely right, it would make sense for the plugin to automatically detect the presence of the CF-Connecting-IP header and prompt the administrator to switch to the correct IP detection method. This would help prevent confusion for users who recently moved their sites behind Cloudflare.

Appreciate your thoughtful feedback and for taking the time to follow up!

Best,
Mehmet

Hi @lodree,

First of all, I sincerely apologise for the delayed response and thank you for your patience.
I’ve reviewed your previous ticket and all the related discussions in detail before replying here.

Based on your description, the issue seems to be related to IONOS’s ModSecurity configuration.
IONOS enables ModSecurity by default and usually doesn’t allow customers to disable it directly. In such cases, requests sent to the endpoint
wp-json/wp-statistics/v2/*
are often silently blocked (returning a 403 or being dropped entirely). This would explain why client-side tracking doesn’t record visits properly while server-side tracking works fine.

Here’s what you can do next:
Please contact IONOS support and ask them to whitelist the path:

wp-json/wp-statistics/v2/*

from ModSecurity.

Alternatively, you can request them to temporarily disable ModSecurity for your domain to verify if tracking resumes correctly after that.

Once this exception is added or the rule is disabled, client-side tracking should start recording visits normally again.

Please let us know what IONOS replies.
We’ll gladly assist you further based on their response.

Best regards,
Mehmet

Hi again,

Yes, that’s correct
We haven’t removed those metrics. They should still be collected as usual.

Could you please go to
Slimstat > Settings > General
and check whether the Tracking Mode is set to Client?

If it’s set to something else, that might be the reason why screen resolution and fingerprint stopped appearing.

Hi @blackbird69,

Sorry for the delay in getting back to you.
The screen resolution and fingerprint data haven’t been removed; they should still be available.

Could you please share a bit more information about the issue?
If possible, please attach a screenshot so we can take a closer look and help you resolve it quickly.

Best regards,
Mehmet

Hello @hirngesicht,

Apologies for the delay in getting back to you, and thank you for sharing all these details.

I’ve passed this matter along to our development team for further investigation. I’ll keep you updated here in this thread and follow up with you as soon as I have more information.

Thank you for your patience and cooperation.

Best regards,
Mehmet

Hi Ranveig,

Thank you for following up and confirming that AdBlock is the cause.
In this case, the best solution is to look for a way to prevent AdBlock from blocking the WP Statistics admin files while still keeping the extension active.

Since AdBlock has its own filtering and whitelisting rules, I recommend reaching out to their support team and opening a ticket. They can guide you on how to whitelist your WordPress dashboard specifically, so that the plugin’s CSS/JS files load correctly without having to disable AdBlock entirely.

This way, you can keep AdBlock active while ensuring WP Statistics displays as expected.

Best regards,
Mehmet

Hi Ranveig,

Thank you for sharing the details, that helps a lot.

Based on the error ERR_BLOCKED_BY_CLIENT, the CSS/JS files from WP Statistics are definitely being blocked by one of your browser extensions (most commonly AdBlock or F-Secure). That’s why the page works fine in other browsers/incognito, but not in your main Chrome setup.

Here’s how you can fix it:

1. Whitelist your WordPress dashboard in AdBlock
   • In Chrome, click the AdBlock icon.
   • Choose “Pause on this site”.
   • Reload your WP Admin page to test.
2. Whitelist in F-Secure (if Web Protection is active)
   • Go to the whitelist/allowed sites settings in F-Secure.
   • Add this pattern: https://blaerekreftnorge.no/wp-admin/*
   • Save changes and restart the browser.
3. Restart Chrome after applying the whitelist so the settings take effect.
4. If the issue persists
   • Temporarily disable all extensions in Chrome by visiting chrome://extensions.
   • Then enable them back one by one while checking the Statistics page. This will help identify the exact extension causing the block.

Once the correct whitelist is in place, the WP Statistics page should load with full styling and charts again.

Please give this a try and let me know how it goes.

Best regards,
Mehmet

Hi Ranveig,

Thank you for your update and detailed explanations.

Since the WP Statistics page displays correctly in another browser and in incognito mode, the issue is not with the plugin or WordPress itself. It’s caused by your main browser or one of its extensions blocking the CSS/JS files of WP Statistics.

Could you please let us know:

• Which browser you are using?
• Which extensions are installed on your browser?

This will help us guide you specifically on how to whitelist your WordPress dashboard so that the plugin displays correctly.

Once we have this information, we can give you exact steps to fix the issue.

Best regards,
Mehmet