I’ve hit an issue with Lemmy. Initial startup was fine… I created my admin user and logged in. Then I created this account.

Third account I went to test with failed to login… then my other accounts also failed, so I rebooted.

Now when I try to log into my admin account, it just spins forever. Checking logs, I see this:

lemmy_server::api_routes_websocket: email_not_verified: email_not_verified

Can anyone tell me how I can manually flag my admin account as having been email verified already?

  • Lodion@lemmy.clickOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Sorry Chris, I was figuring that out as I went. It looks like a postgres syntax error but the command matches what I used.

    If you run “SELECT * from local_user;” do you get output showing your list of registered users? Perhaps you’re not attached to the lemmy database?

      • Lodion@lemmy.clickOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Not sure what to suggest, sorry I’m not a DBA :(

        To make it clear, here is the command I ran enclosed with "

        “UPDATE local_user SET email_verified = ‘t’, accepted_application = ‘t’ WHERE id = 1;”

        • Chris A Moody@thediscussion.site
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          “lemmy=# UPDATE local_user SET email_verified = ‘t’, accepted_application = ‘t’ WHERE id = 1; ERROR: column “‘t’” does not exist LINE 1: UPDATE local_user SET email_verified = ‘t’, accepted_applica… ^ HINT: Perhaps you meant to reference the column “local_user.id”.” This was its response.