[Bug] Cannot load overlay -- Loading spinner keeps spinning

[freelock]

What happened?

When loading a page in the page overlay, the site loads in the iframe, but the "Loading" spinner never finishes.

What should happen?

I should see the overlay bubbles and other content in the sidebar.

How can this be reproduced?

This can be reproduced on the demo site - open the demo site, go to Behavior -> Entry Pages, and click on the page overlay icon. For the /jobs page, this is giving me this URL: https://demo.matomo.cloud/index.php?module=Overlay&period=month&date=today&idSite=1#?l=https$3A$2F$2Fdivezone.net$2Fdiving$2Findonesia$3F__prod_demo$3D1$26__enterprise_demo_idsite$3D1

... same result in current Firefox or Chrome.

There are a bunch of console errors on the demo site related to cross-site cookies, but I've resolved all of those on my instance, and still getting the same behavior -- I don't see any relevant console.log messages on my instance. I do see a warning from Chrome about Third party cookies will be blocked in future Chrome versions, but I think that's getting triggered by Google Analytics, not Matomo.

Matomo version

5.1.1

PHP version

8.1.29

Server operating system

Ubuntu

What browsers are you seeing the problem on?

Firefox, Chrome, Microsoft Edge

Computer operating system

Linux

Relevant log output

index.php?module=Pro…b06a2933b4d9619a:10 Fetch finished loading: GET "https://matomo.freelock.com//index.php?idSite=1&module=GoogleAnalyticsImporter&action=displayConfigureImportNotification".
mastofeed.com/dark.css:1 
 
 Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
www.google-analytics…pa=1&z=1040202966:1 
 
 Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
infinite-scroll.js:1 
 
 Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
[Violation] Forced reflow while executing JavaScript took 50ms
analytics.js:36 XHR finished loading: POST "https://www.google-analytics.com/j/collect?v=1&_v=j101&a=761408191&t=pagevi…d=13l3l3l3l3l1&dma=0&tag_exp=0&did=dMDhkMT&gdid=dMDhkMT&npa=1&z=1040202966".
js_ThAvGAozqlUevFcbp…hXKpdvRDvgGVGJ6U:16 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
js_VDTuq49-yWsUGN-iC…2hXKpdvRDvgGVGJ6U:3 XHR finished loading: POST "https://www.freelock.com/core/modules/statistics/statistics.php".
www.google-analytics…location&tfd=5889:1 
 
 Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
js?id=G-K68R2QNV78&l=dataLayer&cx=c:223 Fetch failed loading: POST "https://www.google-analytics.com/g/collect?v=2&tid=G-K68R2QNV78&gtm=45je494…&en=page_view&_ee=1&ep.page_placeholder=PLACEHOLDER_page_location&tfd=5889".


Validations

• Read our Contributing Guidelines.
• Follow our Security Policy.
• Check that there isn't already an issue that reports the same bug to avoid creating duplicates.
• The provided steps to reproduce is a minimal reproducible of the Bug.

[randy-innocraft]

Hi @freelock. Thank you for creating the issue and bringing this to our attention, that's very appreciated. We have reviewed and triaged the problem internally, and we have confirmed it is an issue. Our team will prioritise this, and we will update you on the progress here when we have an update to share. If you have any further information or questions, please feel free to add them here.

[sgiehl]

@freelock This is in most cases a problem of the setup. On our demo the overlay doesn't work, as the page does not include the tracking code of the demo (as the displayed demo is faked and not real).
You can find further help here: https://matomo.org/faq/reports/troubleshoot-page-overlay-issues/

This could otherwise also be a duplicate of
#16762 or #18291

[freelock]

Hi,

Thanks for looking into this!

I did already add the tracking part to the javascript on the site for the proxy issue, so I don't think that's it -- here's the code in the HEAD of my page:

var _paq = _paq || [];(function(){var u=(("https:" == document.location.protocol) ? "https://matomo.freelock.com/" : "https://matomo.freelock.com/");_paq.push(["setSiteId", "1"]);_paq.push(["setTrackerUrl", u+"matomo.php"]);_paq.push(["setDoNotTrack", 1]);_paq.push(["setCookieDomain", ".www.freelock.com"]);_paq.push(['setSecureCookie', true]);
_paq.push(['setAPIUrl', 'https://matomo.freelock.com/']);if (!window.matomo_search_results_active) {_paq.push(["trackPageView"]);}_paq.push(["setIgnoreClasses", ["no-tracking","colorbox"]]);_paq.push(["enableLinkTracking"]);var d=document,g=d.createElement("script"),s=d.getElementsByTagName("script")[0];g.type="text/javascript";g.defer=true;g.async=true;g.src=u+"matomo.js";s.parentNode.insertBefore(g,s);})();

... I've tested Firefox, Chrome, Edge, so I'm not thinking it's #16762 - have not looked into the "Tracker Domain". Hmm would the cookie domain matter here? Looks like it's setting that for the site domain but not accessible to Matomo....