Hi there @compudevit,
Thanks for reaching out and sharing the configuration that results in this error. I’d be happy to check this for you. In the meantime there may also be some CSP directives impacting Site Kit on your site. I can see various console errors relation to your current setup.
I’ll report back here once I’ve checked the same setting you’ve mentioned. In the meantime can you confirm you don’t see this error if you have the Really Simply SSL plugin temporarily deactivated?
In this screenshot you’ll see an example of some of your CSP directives, which may be impacting your setup, possibly set via a plugin. If the same error appears with your Really Simply SSL plugin temporarily deactivated let me know if you’re aware of how you’ve implemented your CSP policy.
I’ll report back to you shortly on the Really Simply SSL plugin check. I’ll need to check if the free version of the plugin has this same setting you referenced.
Hi there @compudevit,
I’m after checking the Really Simply SSL plugin (free version) and in my case I wasn’t able to recreate the same dashboard error you’re encountering.
While I didn’t encounter any errors I did notice there are some CSP options with the pro plugin. If applying a “self” origin policy for scripts, which it looks like you do have applied, this could result in dashboard errors, with Site Kit communicating with Analytics and AdSense resources.
While I haven’t been able to locate any “Enforce” mod with the free version, in order to resolve your issue and ensure the Site Kit dashboard works as expected, can you reset the Really Simply SSL plugin to it’s default configuration before checking Site Kit once more? After doing so you can re-apply any configurations you set previously, to determine any specific conflict. If you are able to share this I can check this further, or feel free to share more details on the “Enfore” mode and I’ll check further.
As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.
