Infinite "verify you are a human" loop

Infinite verify loop on Firefox despite my verifications. Works on Chrome but I don’t use Chrome regularly.

I’m a human and I’m willing to prove that through video, etc.

I’m a developer and I’m comfortable providing any diagnostics you need. I have a HAR file export showing the issue though I don’t see an upload option in this forum.

I’m on Linux but otherwise not doing anything special. No VPN, no Tor, no ad-block, no extensions. Just vanilla Firefox.


At the advice of a user on Hacker News, I created a new profile in Firefox using about:profiles and I cannot reproduce the issue in the new profile while I can in the old profile. I had cleared cookies/cache in the old profile but maybe it’s something else in the Firefox profile? I’m willing to provide any Firefox profile data for both profiles for comparison although I don’t know how to share that securely without passwords, etc. I customized Firefox very lightly when first installing (e.g. setting a main password, enabling smooth scroll, etc.) and I’m not aware of enabling any advanced privacy features that could cause issues (I’m perfectly willing to send Cloudflare whatever it would like).

I forgot that I had general.useragent.override set in about:config pointing to a Chrome User Agent. I must’ve done that to debug some issues a long time ago. However, disabling it did not help.

Would you be able to send me a HAR of that behavior with default user-agent being set? We’d love to take a look.

Do you see the same thing with Firefox in safe mode?

Edit: Or if a HAR is difficult to get, would you mind sending me the rayID?

1 Like

@amart Thanks for your response. I can no longer reproduce the issue. I’m not sure if there was a fix on your side or if it was because I cleared cookies and cache and restarted by browser after resetting general.useragent.override.

If it was the latter, I’m sorry to Cloudflare as this was user error. I will post this apology to my original Hacker News post.

However, I do think the two meta points still stand: 1) Better diagnostics: perhaps a FAQ page that lists common issues such as an overridden about:config, etc. (obviously without giving anything away to bad people, but I’m sure certain things such as this can be pointed out), 2) Better responsiveness in the community forum particularly to this category of errors which blocks public internet activity.

1 Like

I think your two meta points are good ones, and we will start writing up an FAQ next week. Better diagnostics make sense as well, but we will need to carefully consider how we might surface useful diagnostic information to legitimate users seeing false positives without giving away meaningful information on how to bypass the challenge to bad actors.


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