This seems to be more a problem with Lemmy as I have experienced it on other instances and probably better suited for the Github issue tracker. But I wanted to make a test post anyway so figure I’d start here and see if anyone else has experienced the problem or can direct me to active discussion already started on it.

Signup almost always hangs and just pinwheels. Tried multiple times today, FF in mobile/desktop. Chrome. Same result. Console just keeps dumping messages like ‘CreatePostLike’, ‘RemovePost’, etc., which seem to be global activity being pushed to the client (I haven’t dug too deep, but I’m not actively doing anything so I can only assume it is some kind of global push updates). Likely unrelated to the signup hanging, and it happens on all pages; I realize this is all very early release stuff, but seems a bit poor form to just have console.log endlessly dumping on production to me, even in early release.

Also hangs when trying to login and the account isn’t activated (attempted when I thought maybe it went through despite the hang). Never received a response such as “invalid account” or “waiting for validation”

Eventually an attempt did go through. But a second attempt has resulted in the same behaviour.

Again probably better for the issue tracker, but curious if anyone else local here has found the same issue with signup/login.

  • sinnerdotbinOPEnglish
    2·
    1 year ago

    With some help from our guy @[email protected] , seems the second signup hangup was an issue with user name char limit (which was kindly upped to 30 to accommodate the name).

    Same issue with @sinnerdotbin requiring multiple attempts despite not being over the previous limit. I am running with a theory that there is something it isn’t liking contained in my randomly generated passwords. Seems maybe Lemmy sign-up just doesn’t return any validation errors to the client at the moment.

    • smorksMAEnglish
      1·
      1 year ago

      The only other things I can think of is that passwords need to be 60 chars or less (I think?) and e-mail addresses need to be unique across accounts as well. Hope that helps! It will be better once they get proper error messages showing again, hopefully in the next version.

      • sinnerdotbinOPEnglish
        2·
        1 year ago

        Yeah, definitely password was an issue. My random generated were definitely under 60 chars, but manually creating one instead of random seemed to work on another instance I was having trouble with. No idea what, but maybe some character is not allowed for some reason.

        Thanks again for looking into it!