Debug Mode not able to connect

Hi,

I am unable to connect to debug mode.

The error states:

Connection failed

This may be caused by:

  1. Mismatched container code: Check if the installation code on the website you’re connecting to matches the site or app in the site/app picker in the upper right corner.

  2. Blocked popups: Check if your browser is automatically blocking popups and enable them in the settings if needed.

  3. Missing tracking container code: Ensure the necessary code is installed on your site.

  4. Incorrect site address: Check that you are connecting to the correct URL.

  5. Blocked ads: Temporarily disable ad-blocking extensions.

I already checked this support ticket: ‼️ Help! New debug mode does not work anymore in our setup! which seems very similar to what I experience but that one was answered via a PM so that does not help much.

I also checked this guide About debug mode | Piwik PRO help center but as far as I can tell everything is configured in accordance to this document.

About the suggestions:

  1. I installed a script on each of the pages of my website like described here: Set up your account | Piwik PRO help center. I am also getting the consent popup, so I guess this must be good.
  2. I have tested in Chrome and Safari and ensured popups are allowed in the settings.
  3. Isn’t this the same point as number 1?
  4. Domain name is correct. It also opens the website correctly in a new tab, but that tab does not get the popup and on the piwik.pro debug page the error I mentioned earlier appears.
  5. I do not have any ad blocking activated

Anyone any idea what I am missing?

Best, Roel

Hello @roelnoort and welcome to our community!

Can you provide me more details about this website? I can take a look.

If you want to keep it private you can send it as PM.

@roelnoort

I’ve checked your setup, nothing seems to be odd except CSP added to script.

Could you please check if disabling it will allow debug mode to work?

Indeed disabling the Content Security Policy header makes it work.
I will try running it in Report-Only mode and see what is missing.

1 Like