EDIT: Solved by deleting all cookies (check on Dev Tools > Storage > Cookies=. Thanks @CMahaff.

------------------------------------------------------------
Hi, I’m not able to login on lemmy.world from Firefox.

Here it is the screenshot with the HTTP calls.

What I’ve done and tried:

  • Today I learnt about https://mlmym.org/lemmy.world/ and gave it a try
  • Then I realized I had input my credentials without checking if it was trustable, so I went to lemmy.world and changed my password
  • To confirm the password had changed correctly, I logout out and when I try to log in, I could not
  • I’ve tested that I can log in using Ms Edge
  • I restarted Firefox in Troubleshooting mode (all addons disabled) and still cannot log in (the screenshot was taken in troubleshooting mode).
  • I’ve tested that I can log in via https://mlmym.org/lemmy.world/ (I know, now I should change the password again, but I wanted to get more info). This post has been sent from there.

Any idea (to fix or diagnose it further) is very welcome, thanks!

  • @CMahaff
    link
    English
    2
    edit-2
    1 year ago

    Maybe clear site data / cookies for lemmy.world in Firefox?

    If you click on the login API call in Firefox, it should be returning you a token. I’d be curious if the other calls show that token being used, or an old one.

    Could maybe be some kind of front-end bug where it’s using your previous token for some reason?

    (And don’t post the tokens here - they could be used to hijack your account :) )

    • @CrulOP
      link
      English
      31 year ago

      TL;DR: Solved by deleting all cookies, there was a duplicated jwt cookie, thank you very much!

      Maybe clear site data / cookies for lemmy.world in Firefox?

      I thought I had already done that… I’m happy I forgot to say because I looked at the Storage > Cookies section and I saw 2 jwt with different values.

      Could maybe be some kind of front-end bug where it’s using your previous token for some reason?

      That’s exactly what was happening (because the duplicated jwt cookie, probably). I saw that the first characters of the token were the same, but didn’t really checked the rest. My bad!

      (And don’t post the tokens here - they could be used to hijack your account :) )

      Yeah, important advice. That’s why I blacked it out on the screenshot.

      Thanks again!

      • @CMahaff
        link
        English
        21 year ago

        Yeah definitely sounds like a bug, but glad you got it sorted!