Hi @richbhanover
That SecurityError: Permission denied message is a common browser console warning and isn’t harmful. It usually happens when scripts from different domains interact — in Jetpack’s case, often related to stats or other features loading from WordPress.com.
Your Jetpack connection looks great, and everything should be working as expected. That said, the error shouldn’t interfere with site performance or functionality. If you’re seeing broken functionality alongside this error (e.g., Stats not loading), please let us know and we can investigate further.
Let us know if anything’s not working right!
Thank you for the speedy response. But I’m not sure how your answer describes what I’m seeing.
I hadn’t expected my simple WordPress site without a lot of plugins, and certainly not accessing off-site resources, would generate this many messages simply to view a post. I didn’t mention earlier that there are cookie errors as well.
As a software developer, I treat all warning messages as danger signals. (Someone went to the trouble to create those messages. They set off my spidey-sense and make me worry, especially when they say a certain feature will soon be rejected.)
I would encourage you to go to my site and check it again. Thank you
Hi @richbhanover
Thank you for your detailed follow-up and for sharing your concerns. The SecurityError: Permission denied and related cookie warnings you’re seeing are indeed triggered by Jetpack’s interactions with external services, even on simple WordPress setups – which can lead browsers to log these security and cookie-related messages as part of their protective measures.
While these messages can look alarming-especially with warnings about future browser changes-they are generally not harmful and are a byproduct of how Jetpack provides its features. However, as a software developer, your caution is understandable.
If these console messages are accompanied by broken functionality, or if you want to minimize them, further troubleshooting (such as testing with a default theme and updating all plugins/themes installed/browser version) may help.
If you’d like, you can share more details by sending screenshots and letting us know which specific browser you’re using (and its version). That way, we can check on our side to see if we get the same result.
You can also try clearing your browser’s cache or using a different browser to make sure your browser is getting the latest information.
Looking forward to your response.
Thanks for the additional details. You’re right – different browsers have different messages. (All tests on macOS 15.4.1)
- Google Chrome Version 137.0.7151.6 (Official Build) beta (arm64) shows
JQMIGRATE: Migrate is installed, version 3.4.1
- MS Edge Version 131.0.2903.86 (Official build) (arm64) also shows
JQMIGRATE: Migrate is installed, version 3.4.1
- Safari Version 18.4 (20621.1.15.11.10) shows the JQMigrate message plus:
[Info] Content blocker prevented frame displaying https://randomneuronsfiring.com/ from loading a resource from https://www.googletagmanager.com/gtag/js?id=G-9HP0KLQ8L1
[Info] Content blocker prevented frame displaying https://randomneuronsfiring.com/ from loading a resource from https://stats.wp.com/e-202518.js (randomneuronsfiring.com, line 751)
[Info] Content blocker prevented frame displaying https://randomneuronsfiring.com/ from loading a resource from https://stats.wp.com/e-202518.js
- Firefox Developer 139.0b2 (aarch64) shows:
JQMIGRATE: Migrate is installed, version 3.4.1 jquery-migrate.min.js:2:981The value of the attribute “expires” for the cookie “_ga_9HP0KLQ8L1” has been overwritten.
- Firefox 138.0.1 (aarch64) on mac shows the error messages I saw. I imagine that I have many of those security settings set, although if I set the privacy settings to “Standard” , I still get the messages.
I don’t think this needs to be pursued further. I’m just documenting my findings. Thanks again
Hi @richbhanover
Thanks for sharing your findings! It really helps if others with the same concern see this post.
I’ll mark this thread as resolved, but if you run into anything else, feel free to start a new topic. 🙂
