Yesterday i upgraded ff to the current version and since today i experienced problems with a bunch of different sites. Either the cloudflare verification sends me into a loop or i get through and the site’s not working correctly. Some others work, though. Disabling add-ons (noscript, ublock) and allowing all cookies didn’t help. Most work with microsoft edge, but i don’t know if the others worked with edge before.

Does somenone have info on that or experienced the same problem? I’m not sure is it just a coincidence or does the update cause the problems.

Edit:

I found a workaround for some. First i set the cookie block from “all cookies” to “all cross-site cookies”, then i allowed via STRG+i to set cookies for the refreshed page. Then i set the cookie block back again.

I assume cloudflare changed the address for some of their cookies which got blocked by ff.

The only one still not working (so far) is suprfit.com. It’s not a big shop, their software might produce their own shenanigans. I’ll shoot them a mail later.

Edit2:

suprfit.com works now too. Whatever it was got fixed.

  • abhibeckert@beehaw.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    Most work with microsoft edge, but i don’t know if the others worked with edge before.

    The fact you say “most” and not “all” suggests this isn’t a FireFox problem. Also, given how popular Cloudflare is (30% of global web traffic?) I’d bet if there was something incompatible it would be fixed. Immediately.

  • mat@linux.community
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I’m stuck in Cloudflare loops as well, been a week or two. It works in “Private” windows so I’m guessing it’s an addon. I think it might be either uBO, Privacy Badger, IDCAC (fork), or DecentralEyes.

    • catacomb@beehaw.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I’ve read not to bother with Decentraleyes. The dependencies are often out of date which mean you’ll hit 3rd party CDNs anyway. Unless its coverage is 100℅, it’s less than useless for privacy as the hit pattern to CDNs might even make you stand out.

      Privacy Badger is also redundant if you have uBO.

    • d3Xt3r@lemmy.nz
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      It’s the opposite for me, private mode causes more Cloudflare prompts (and Google captchas).

      • acastcandream@beehaw.org
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        I basically can’t have anything running for privacy anymore without Google capchas triggering. It’s driving me crazy.