Local development working perfectly from Firefox. No extensions are installed on either Chrome or Brave
What steps have you taken to resolve the issue?
Triple-checked CF dashboard for public and private key values. But since all works from one browser that uses :
. the same operating system
. the same ip address
Why would it be broken for other browsers?
Local development working perfectly from Firefox. No extensions are installed on either Chrome or Brave
What steps have you taken to resolve the issue?
Triple-checked CF dashboard for public and private key values. But since all works from one browser that uses :
. the same operating system
. the same ip address
Why would it be broken for other browsers?
Windows 11
Firefox 128
Brave 1.67.123
Chrome 126.0.6478
Apologies for the double post, I posted in the wrong category (here) and tried to delete this post - and then to add a new one in a more relevant subforum.
Anyway
I have just turned off DNSSEC @cloudflare and deleted the DS entry at registrar level.
Out of curiosity:
. how long is that DNSSEC turning off will take approximately?
. and why turn it off? How is it related to turnstile?
(I suspected turnstile was not working due to the site not being fully active. I did not check to see if it was enabled at cf or the registrar, but see on your dash it was cf and the cancelation is in process waiting to confirm the file removal.)
The site loads fine for me in chrome & safari. Is it just brave that is causing issues? In looking at your posts, it seems maybe just chrome is not working? Perhaps clear cache and/or try incognito mode.
The (prod) site is ok but I am encountering problems on a local (127.0.0.1) machine. Might it all be linked to that?
It would be strange, though, as FF doesn’t cause any problems at all.
yeah apart from the “functional delta”. I just noticed that the only page which at the moment uses turnstile on production (Ad Lumens - Drop me a line) works perfectly.
The local, in-development, pages use the same invisible widget with keys set up for local only. They work:
. always for FF
. sometimes for chrome (standard mode) (mostly not, however)
. never for chrome incognito
. never for brave with shields up! (haha)
. never for brave with shields down
well after deploying, it turns out the same problems occur as on local. The invisible challenge works:
. always for FF
. almost never for chrome (standard mode)
. never for chrome incognito
. never for brave with shields up! (haha)
. never for brave with shields down
I really don’t understand why such an integration would work for Firefox and utterly fail for other browsers, knowing the IP and operating system combination remains the same when switching browser…
