can you share your domain so we can have a look?
thedrewseum.com
I’m seeing a very small amount of hits since yesterday, but versus what JetPack’s stats are showing, something is definitely not right.
Thank you!
Like the other thread you mentioned, it appears also to be an issue with mixed content (which means the site is trying to load http resources on a https website. Can you go to the general WordPress settings:
/settings/general, then check if your site url starts with https://. If it is set to http://, please change it to https:// and save.
I tested your site from multiple locations (UK, Netherlands, Germany), and I see this happens consistently when visited from Germany, which is weird, as I haven’t seen region dependent resources loading before.
I don’t know if it’s related, but when visited from Germany I also get a different cookie banner.
Anyway, I expect it to be resolved if you update your site url.
Hi Rogier,
Thanks for clarifying where to find the setting. It is set to https. Any other thoughts?
I think it is cached somewhere. Because when I visit your site from the Netherlands, I get this as the url for the statistics script:
https://thedrewseum.com/wp-content/uploads/burst/js/burst.min.js?ver=1767821109
If you open it, you will see that the beacon_url starst with https => this one works.
But when I visit from Germany, the script that is loaded is:
https://thedrewseum.com/wp-content/uploads/burst/js/burst.min.js?ver=1767907660
(note the different version id at the end). If you open it, you will see it starts with http, which causes the mixed content warning, and the endpoint is blocked => doesn’t work.
If you change any number randomly at the end, it will load the current, not cached version. You will see it starts correctly with https. So the current, actual (not cached) file is the right one. Only some regions are loading the incorrect one from cache.
If you are using CloudFlare, you can try purging the cache on CloudFlare. If it is cached by your hosting company, there should be a purge cache option in your hosting dashboard. Your hosting company will know more about it.
If you have a caching plugin, try clearing that cache as well, although caching plugins tend not to cache by region in my experience.