Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Logging in displays: auth_cookie_insecure #2193

Closed
4 tasks done
kroese opened this issue Oct 19, 2023 · 4 comments
Closed
4 tasks done

[Bug] Logging in displays: auth_cookie_insecure #2193

kroese opened this issue Oct 19, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@kroese
Copy link
Contributor

kroese commented Oct 19, 2023

Requirements

  • This is a bug report, and if not, please post to https://lemmy.ml/c/lemmy_support instead.
  • Please check to see if this issue already exists.
  • It's a single bug. Do not report multiple bugs in one issue.
  • It's a frontend issue, not a backend issue; Otherwise please create an issue on the backend repo instead.

Summary

In Lemmy 0.19.0-beta.8 when you sign in for the first time, it works fine. But as soon as you logout and try to signin for a second time, it displays the message:

auth_cookie_insecure

This error does not go away until you clear your cache/cookies.

As a workaround I always need to use an incognito tab now.

Steps to Reproduce

  1. Sign in
  2. Sign out
  3. Try to sign in
  4. auth_cookie_insecure error

Technical Details

Samsung Internet browser on Android. But also with Edge on Win11.

Lemmy Instance Version

0.19.0-beta.8

Lemmy Instance URL

No response

@kroese kroese added the bug Something isn't working label Oct 19, 2023
@kroese
Copy link
Contributor Author

kroese commented Oct 20, 2023

Can still reproduce this in 0.19.0-rc.3

@TheSaneWriter
Copy link

Indeed, I'm able to reproduce this issue on lemmy.thesanewriter.com on 0.19.0-rc.3

@fantismo
Copy link

Happened to me on 0.19.0-rc.4.

@dessalines dessalines reopened this Nov 13, 2023
@kroese
Copy link
Contributor Author

kroese commented Nov 13, 2023

I never saw it happen anymore after switching to rc4 from rc3. So I suspect @fantismo 's problem may have some other cause? Like the javascript from rc3 still in the browser cache for example.

@kroese kroese closed this as completed Nov 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants