Hi scruffy1,
Sorry to hear that, let’s figure out what’s blocking it. A few questions to narrow it down:
1. **What version of SlimStat are you running?** Version 5.5.0 (released June 24) included several PHP 8.x fixes. If you’re on an older version, updating is worth trying first.
2. **Do you have a caching or security plugin active** (e.g. Wordfence, LiteSpeed Cache, Cloudflare, Sucuri) on either site? These can silently block the tracking request without showing you any error – we’ve seen this exact “no errors, just stops counting” symptom caused by a firewall quietly blocking the plugin’s tracking endpoint.
3. **Do you use a cookie consent/GDPR banner plugin?** If tracking requires consent and something changed with how consent is granted, hits can silently stop being recorded.
4. Could you open your site in a private/incognito window, load a page, then check the browser’s DevTools → Network tab for a request to /wp-json/slimstat/v1/hit? Let us know if that request appears and what status code it returns (200, 403, 503, etc.) – that tells us immediately whether the request is even reaching the site.
The fact it happened on both sites the same day makes an external cause (plugin, host, or consent setup) more likely than a plugin bug affecting two sites at once, but the network tab check above will confirm it either way.
Hi Mostafa Soufi (@mostafas1990)
Thank you for the reply.
1) I am using the latest on both websites 5.5.0
2) Yes we are using Wordfence and a couple of other security plugins. They have now been disabled to see if Slimstat starts working again. Although, we have no idea why it would suddenly stop on July 5 because we had not updated any plugins on that date or days before.
3)Yes we have to use a banner, and we have no way around this, and we cannot deactivate it because of regulations.
I will give it a couple of days after deactivating the mentioned plugins to before proceeding onto “stage” 4
Thank you, Tracy
HI,
Just an update. For some strange reason both Slimstats on different sites with different PHPs suddenly started working again. Nothing was updated or changed so no clue to why they might have stopped working in the beginning.
Thank you, Tracy
-
This reply was modified 2 days, 13 hours ago by
scruffy1.
Hi,
Great to hear it’s tracking again on both sites! That actually confirms what we suspected: one of the security plugins (most likely Wordfence, based on similar cases we’ve seen) was silently blocking the tracking request without showing you any error.
The delay before it “fixed itself” isn’t really mysterious, it’s a common side effect: firewall rules from these plugins are often cached separately and can take a while to actually clear, even after the plugin itself is disabled. That’s likely why it took a day or two rather than working the moment you turned Wordfence off.
If you’d like to re-enable Wordfence and the other security plugins (recommended for security, generally), the fix going forward is to allowlist the tracking endpoint specifically rather than running without them: add an exception for /wp-json/slimstat/v1/hit in Wordfence’s firewall rules (Firewall → All Firewall Options → Allowlisted URLs), and check the same in any other security plugin you’re running. That should let tracking through while keeping the rest of your site protected.
Glad it’s working, thanks for closing the loop!
