So things have been going smoothly on my instance since setting it up. While setting things up from scratch was an adventure, everything has worked as expected, with no real hiccups, since I got it off the ground.

Then I opened up the tab in Firefox today only to be greeted by a little orange notification in the bottom left of the screen telling me that I didn’t have admin rights.

Odd, I thought, but maybe I had just been logged out, or the service stopped running, or something. So I refreshed the page, but I remained logged in. I checked the service on the host, and it was still running.

So I logged out, only to find that I can’t log back in again. It doesn’t recognize my username/email + password.

If I try to go to my user account URL, it doesn’t recognize it. Clicking on my account name in posts I’ve posted brings me to www.example.com/c/Kichae@www.example.com, i.e. it now recognizes my account as being remote.

I checked out my user info in the database, and that all seems ok, though I admit that I hadn’t gotten around to looking at that before the issue, so I don’t have a clean memory to compare it to. But the entry in the local_user table points to the right ID in the person table. I also found some actual remote accounts in the user table, which I found kind of weird, as, while I have federation enabled, I can’t imagine anyone on other instances would have found the site.

Now, I have managed to regain access to my account, and to my admin status, by directly editing the database. Removing the www prefix from my actor_id, inbox_url, and shared_inbox_url fields got me that far, but it still seems to think my profile is located at example.com/u/Kichae@example.com and not just example.com/u/Kichae.

I’m a bit perplexed, especially since nothing seems to have happened between yesterday and today. No settings have been changed. No new posts have been made. No new users have joined. The last thing I did before going to bed yesterday was post a comment.

Any leads as to what’s happened would be well appreciated so that I can guard against it happening again.

  • @nutomic@lemmy.ml
    link
    fedilink
    21 year ago

    Did you change the domain of your Lemmy instance? You said you didnt change anything, but it could explain the problems you are seeing. This includes adding or removing a subdomain like www.