@whichgodsaves the site seem to have a connection error. Can you head to https://jetpack.com/debug and paste your address there, then ask your host for help with addressing the errors?
You can also have them try curl -I https://godversusreligion.com/xmlrpc.php – I get a 405 error there.
Hi – I contacted bluehost and when they tried those things, didn’t get any errors. They asked if you can send me the errors you received. BTW – I ran the debug myself and also didn’t get any errors – came back clean.
At least according to tests from our end, Jetpack is working properly at https://godversusreligion.com/ now.
Are you still having trouble with this?
It does seem to be doing stats correctly now. I was looking for similar issues and found one about possible problems when uninstalling / disconnecting Jetpack. I did that several months back as part of troubleshooting another problem. Jetpack was stuck in that circle in the stats widget – turned out be be a problem with another plugin, but I did disconnect and then reinstall Jetpack as part of that.
A few hours ago, I disconnected and reconnected. So far, it is recording views on recent posts again.
Hoping it resolved now. Thanks
I guess this maybe isn’t resolved. I got far enough with Bluehost to see that the site is often very slow – apparently causing Jetpack to lose connectivity. Put in Cloudflare and things are getting better.
My question at this point is – are the stats from Jetpack likely to be off because of the previous issues, or should they be correct? I analyzed awstats for June and it shows 16,715 views (for legit posts, filtering out everything other than an actual post) so far this month. Jetpack shows 3.408.
thanks!
chris
AWStats does not filter out bots visits, like search engine spiders, spam bots, etc. It also doesn’t filter out spam referrers.
We do ours best to filter those out, so you only see human visits, hence the discrepancy.
I believe it’s an over simplification to chalk it up to that. Something happened to drastically change what’s reported by Jetpack somewhere around feb or march. There was a site problem around that time – and it seems like something got messed up. Would be nice to fix, but …
Oh no, what I meant over all is don’t compare Jetpack stats to AWStats. 😉
I think you’re on the right path though that maybe the site’s slow load speed lead to browsers eventually timing out on a few elements. Since our stats script is one of the last to load, that makes the most sense.
