All Collections
EN FAQ
Domains
3.11 Connected a domain through Cloudflare, but it does not work in the tracker, what could be the reason?
3.11 Connected a domain through Cloudflare, but it does not work in the tracker, what could be the reason?
Viktoria Petruk avatar
Written by Viktoria Petruk
Updated over a week ago

Typically, the main reason is that Cloudflare automatically turns on proxying, both on the primary domain and on the domain created to be added to AdsBridge. The enabled proxy status in Cloudflare affects the stability of the domain and technically makes it impossible to keep everything under control when adding a domain to AdsBridge. For this reason, in order for the added domain to work correctly in AdsBridge, you must deactivate Proxy status. An example of what the setup should look like:

Type: CNAME

Name: subdomain name (e.g. www). It is important!

Content: system domain from the tracker, located in the Section Domains. Typed without https

Proxy status: DNS only

Next, in the Domains section of the tracker you add the domain from the record in the following form: example, www.domain.com

Did this answer your question?