Fellow reddit refugee here. I’m having trouble logging in using LibreWolf (basically firefox) with multi account containers turned on. I can log in fine with Chrome or in a LibreWolf Private Window, and most other sites work fine, so apparently I’ve got something configured weird or lemmy.ml is doing some weird cross-site authentication or setting a cookie from another site.

I have lemmy.ml set to always use a Lemmy container, Google set to always use a Google container, Hachyderm.io using a Mastodon container, etc., and those all work fine, but Lemmy just spins when I click the button to log in.

Anyone know what else I should whitelist to log in normally?

  • DessalinesAEnglish
    4·
    2 years ago

    I’d need to see the browser console logs to figure out what’s going on. But it sounds like a plugin you’re using is blocking the cookie from being set.

    • fluffman86OPEnglish
      2·
      2 years ago

      Looks like this might be the issue? I get this warning in the console when logging in with a Private window, and I think LibreWolf is blocking it (firefox.exe is blocked at work so I run librewolf portable there)

      Cookie “jwt” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite

      • DessalinesAEnglish
        2·
        2 years ago

        Hrm… didn’t know about that one. I’ll open up an issue in lemmy-ui for it.

    • fluffman86OPEnglish
      2·
      2 years ago

      Thanks for the quick response! It’s almost certainly a tracking protection or a 3rd party cookie. Are you setting any 3rd party cookies or is some other authentication happening? I’ll see if I can grab the console logs for you, too, if I don’t figure it out soon.

  • ICBM@lemmygrad.mlEnglish
    2·
    2 years ago

    Have you tried reloading. That fixes the hanging action issue for a while until I tab away for a bit on mobile. I just reload preemptively when I come back after a while.

    • fluffman86OPEnglish
      2·
      2 years ago

      Yeah, I know the site is getting slammed today, and I did get some http 400/500 errors at times, but this is different. Reloading hasn’t helped. Thanks, though! I think it’s the jwt cookie that’s being blocked.