Use Zaraz on domains not proxied by Clou...
Hello, Team. 🙂
I've noticed that my Cloudflare Zaraz scripts are returning a 522 error.
Looking at the Security Analytics shows that this number is increasing.
I don't know the exact time this started, as I left it untouched for a month, so this isn't the case when "I did something wrong."
I tried purging the cache and excluding the URIs from the path rules, but that did not help. The custom paths are correct (as said - I haven't touched anything). This happens across various websites (https://developers.cloudflare.com/zaraz/advanced/domains-not-proxied/) and can even be seen on page speed testers (this is how I noticed it).
For the context - I use the custom Endpoints, where the
/consent/app/init.js is /cdn-cgi/zaraz/i.js
How can this be solved?Cloudflare Docs
Use Zaraz on domains not proxied by Cloudflare · Cloudflare Zaraz ...
You can load Zaraz on domains that are not proxied through Cloudflare. However, you will need to create a separate domain, or subdomain, proxied by Cloudflare (also known as orange-clouded domains), and load the script from it:
1 Reply
I think this has something to do with the cache.
But cache purge helps a little, and it looks like the rules of bypass cache also do not solve this. :/