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?
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;”
“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.
I’ve just taken a look at your instance… you’re running a slightly older version. I’m guessing the DB schema has changed.
Does “SELECT * from local_user.id;” get you a list of users? You may need to update the other references to match whatever the old DB schema is.
no it doesn’t work. “ERROR: relation “local_user.id” does not exist LINE 1: SELECT * from local_user.id;”
Sorry mate, I’m out of ideas.
My instance is only 4 days old, how do I update it?
updated my instance, no change however as far as the database is concerned.