ERR_CONNECTION_REFUSED logs caused by Adblocker

I see a crap ton of this in my logs. When the server goes to start a recording yesterday on TVE.
The domains it is trying to connect to "dpm.demdex.net" and "geolocation.onetrust.com" and "googletagmanager.com" and "js-agent.newrelic.com" are being blocked by my AdguardHome DNS server.
It takes about 18 secs, then it does auth fine and says something about getting a cookie.
Googeling these domains not really giving me any useful info.

What are they? I gather they are used in some part for the auth for TVE? But, If they are not necessary to Channels DVR function, as it seems since they are being blocked and i have not had any issues....why are they used?

ChatGPT is fun.

Specifically, "demdex.net" is a domain used by Adobe for their Audience Manager product, which is a data management platform (DMP). Audience Manager enables organizations to collect, organize, and activate their audience data for targeted advertising and personalization purposes. It helps marketers create detailed customer profiles and deliver relevant content and advertisements across different channels.

Regarding the specific purpose of the "geolocation.onetrust.com" domain, it is likely used for geolocation services provided by OneTrust. Geolocation services involve determining the physical location of a device or user based on various data sources, such as IP addresses, GPS coordinates, or Wi-Fi signals. Geolocation data can be used for a variety of purposes, including personalizing website content, targeting advertisements, and ensuring compliance with regional data protection laws.

The domain "googletagmanager.com" is associated with Google Tag Manager, a widely used tag management system provided by Google. Google Tag Manager (GTM) allows website owners and marketers to manage and deploy various tracking codes, tags, and scripts on their websites or mobile apps without directly modifying the underlying code.
The purpose of Google Tag Manager is to simplify the process of adding and managing tags for analytics, advertising, and other third-party services on a website. With GTM, users can centrally manage their tags, define triggers and variables, and control when and where these tags are fired on their website.

The purpose of the "js-agent.newrelic.com" domain is related to New Relic's browser monitoring capabilities. When a website or web application incorporates New Relic's browser monitoring solution, a JavaScript agent is typically included in the webpage's code. This JavaScript agent collects performance data from the users' browsers, such as page load times, JavaScript errors, and network requests.
The JavaScript agent communicates with the New Relic server infrastructure, and that's where the "js-agent.newrelic.com" domain comes into play. It serves as the endpoint where the JavaScript agent sends the collected data. This data is then processed and made available on the New Relic platform, where users can access detailed insights, metrics, and visualizations to understand the performance of their web applications.

The geolocation may be the TVE auth making sure u are in USA or whatever? I thought only Local channels via tve need geolocation?

The js-agent thing, seems to be part of the internal script that Channels is running to do the auth process.

These 2 domains seem like the most functional needed to allow?

The Adobe one, I know that there is Adobe tech in the auth system in some way, but this seems to be just data collection and not needed.
The Google Tag thing, No idea on that one.

However, aside from causing a delay in authing the tve channel stream, these do not seem to be mandatory to be allowed to connect.
But wonder about any long term side affects of blocking them.
I have whitelisted those just for the device the server is on, just cause it does cause a auth delay.

The way websites and streaming services work is a very complicated thing. Without digging into each specific situation (which can change at any time), it's impossible to know how important a given dependency is to the functioning of a site. Our guidance is that you do not block anything for the DVR because anything you do block may or may not actually impact the stream and the effort required to diagnose each individual issue is far more than the benefit of blocking. If you are blocking and you do report a problem, our first step will be to ask you to disable any ad blocking you have.

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.