Testing preview uses piwikUrl from database to reference the domain for hosting container_CONTAINERID_preview.js.
In my case this is http(s)://10.244.24.61/js/container_CONTAINER_preview.js and not http(s)://analytics.example.com/js/container_CONTAINER_preview.js
piwikUrl is updated by core:archive and visits to matomo dashboard on https://matomo-dash.example.com and they race about updating this field in the db.
Hi @roflmao
What happens in the network (while using the production container AND also the preview one)?
How is configured the MTM bootstrap code: with 10.244.24.61, or with analytics.example.com?
It seems it is automatically configured via matomo’s piwikUrl from the database which is automatically set by matomo upon visiting the site and same with running core:archive. Visiting the page gives piwikUrl set to analytics.example.com and running the archive updates it do the ip of the container running the core:archive.
Hi @roflmao
Very strange behavior…
Does problem occur only in preview mode?
To which address do you configure MTM container (10.244.24.61 , or with analytics.example.com)?