Login Issues

Master@beehaw.org to Beehaw Support@beehaw.org – 4 points –

I can login to my beehaw account through an app but on my computer it just sits and spins forever. Gave it the whole weekend thinking it was just a capacity issue but I think the login might just be broken.

Can anyone else confirm?

11

You are viewing a single comment
View all comments

We've seen a few reports of this, but in every case we've been unable to reproduce the issue.

Can you follow the directions here to create a HAR file with Firefox? Just skip step 7 that says Upload it to CB Vault, instead use a dropbox or gdrive of your own, to share a link from.

I think this may be the same issue: https://github.com/LemmyNet/lemmy-ui/issues/1652

In my case, there was never any POST request/websocket communication (no network activity at all) after pressing the button.

I finally succeeded in submitting my registration application only after disabling the Bitwarden extension completely in my browser.

Oh man now that is an interesting discovery. Thanks for sharing.

https://www.dropbox.com/s/9k7e4dkuxw0hhzi/beehaw.org_Archive%20%5B23-06-26%2012-09-07%5D.txt?dl=0

Text version

Thanks. I don't see any post attempt in that, which it should have if you tried logging in when it was running. I don't know what to make of that... I don't see anything blocked either, I just don't see the POST that should be trying to do the login.

https://www.dropbox.com/s/i85kckcltgpp85b/beehaw.org_Archive%20%5B23-06-27%2009-25-56%5D.har?dl=0

https://www.dropbox.com/s/2kvqce20h1e6rfl/beehaw.org_Archive%20%5B23-06-27%2009-25-56%5D.txt?dl=0

Left it logging for 10 min this time. To me it seems like the script isn't loading in the backend. The forgot password button also doesn't do anything.

Understood, I will keep trying to dig into this further. Thanks for the additional details.

If you open the web developer tools, and go to 'console' tab; when you click the login button, what is printed out to that console tab?

It doesn't actually put anything in the console when I submit username and password. The attached console shows me trying twice between page refreshes. That's where the socket closed comes from.