I see you’ve activated the Stats module again on digifotofan.nl/blog, but you’ll need to do the same on aussiroo.nl, by going to Jetpack > Settings in your dashboard, and clicking on “Activate” next to the Stats module.
Jetpack doesn’t seem to be active and connected to WordPress.com on clackclick.nl, so you’ll need to activate the plugin again, and then go to the Jetpack menu to connect the plugin to your WordPress.com account. Once you’ve done so, you can go to Jetpack > Settings and make sure the Stats module is active.
I hope this helps.
Thanks for your quick reply. I know Jetpack stats are deactivated for Aussiroo and ClackClick, I did that because it slowed the start of the slideshows down a lot, they hardly opened. For Digifotofan I manually removed Jetpack and put the previous one back from a back-up and connected it again. Now my slideshows act normally and I can see the stats again via WordPress.com in the Jetpack menu they don’t do anything at all and I’m getting the text below:
User Agent: “Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.111 Safari/537.36”
Page URL: “http://digifotofan.nl/blog/wp-admin/admin.php?page=stats&noheader”
API URL: “http://dashboard.wordpress.com/wp-admin/index.php?noheader=true&proxy&page=stats&blog=12143637&charset=UTF-8&color=ectoplasm&j=1:3.1.1”
http_request_failed: “Failed to connect to dashboard.wordpress.com port 80: Connection timed out”
I did that because it slowed the start of the slideshows down a lot, they hardly opened.
I’m not sure how Stats could affect the slideshows on your site, since all stats do is adding a tracking code to the bottom of your site, after the slideshow is loaded. That tracking code hasn’t changed between Jetpack 3.1.1 and Jetpack 3.2, so the new version of the plugin won’t add any stats code that wasn’t already in Jetpack 3.1.1. I’d suggest running some more tests by deactivating other plugins, one at a time, in order to check if another plugin could have an effect on the slideshows on your site.
in the Jetpack menu they don’t do anything at all and I’m getting the text below:
http_request_failed: “Failed to connect to dashboard.wordpress.com port 80: Connection timed out”
Do you have SSH access to your site? If so, could you run the following command, and let me know what the results are? If you do not have access, your host should be able to run that command for you:
dig @8.8.8.8 dashboard.wordpress.com
Thanks!
I don’t think so but the weird fact is that the stats work again via WordPress.com since I downgraded to Jetpack 3.1.1 also the slideshows open as they did before. This started a few days ago from one moment on the other, I hadn’t changed anything. But since I updated to version 3.2 it all already became slower. And the past months I haven’t changed any plugins, theme or whatever. The only thing I did do was adding blogposts.
Could you try to upgrade to 3.2 again, and then go to Jetpack > Settings and deactivate each Jetpack module, one at a time? That might help us figure out if a specific module is causing issues on your site.
Let me know how it goes.
I still have 3.2 on the Clackclick site, I’ll try this later this afternoon and will let you know. Thanks for your help.
Unfortunately it didn’t make any difference. I also tried after deactivating all the other plug-ins, also that didn’t make any difference. On my Digifotofan site I still have Jetpack 3.1.1 and the stats activated, on the site they don’t work but I can see them at WordPress.com and for me most important when those are activated they don’t slow down the start of the slideshows in my blogposts which does happen when the stats in version 3.2 are activated. I never had problems before, I didn’t change things, just wrote blogposts like I normally do so I really don’t understand how this could happen.
Could you let me know the results of the command I mentioned above, or ask your host to run it for you if you don’t have ssh access?
Thanks!
Is this the exact command? dig @8.8.8.8 dashboard.wordpress.com
If so the result is Command not found
That’s indeed the exact command:
dig @8.8.8.8 dashboard.wordpress.com
If dig isn’t available on your server, you’ll need to ask your hosting provider to install dnsutils or something similar for you.
Okay I’ll ask but I wonder how this could suddenly be different from one day on the other. It always worked fine. And thanks for your very quick answers.
It’s probably a problem at the site of the host, I informed them after having contact with Mikey from Jetpack. I’ll keep you informed.
i have the same problem. How i can fix it?
I just saw that it is a common problem users host OVH. should resolve in a day
