@[email protected] I updated the db and it seems like it’s fixed. Thanks for helping! The solution was the actor_id for the user account was still pointing to Frank_Bot URL, which is already invalid.
Oh wait… sorry @[email protected] I just realized I made a mistake there. T_T You actually cannot change your account name(only your display name) which I now understand the reason. I changed the account name a long time ago so I forgot that I changed the account name manually via the database without updating the actor_id and inbox_url correctly.
E.g. the actor_id should be https://monyet.cc/u/MonyetBot instead of https://monyet.cc/u/Frank_Bot, which was the old URL.
The reason you can’t change your account name is most probably everything relies on the actor_id to work, and if the actor_id is invalid, it won’t be able to federate. Even if they updated the actor_id and inbox_url, all your past post, comments and messages etc. should be tied to the old url, which won’t carry over after you change your account name.
luckily we caught this early before monyetbot had a lot of posts. anyway, i think what’s even more important is the keypair in the db, so it is good the problems monyetbot had were not related to that.
by the way, you may want to do a sql dump and search if there’s any other reference to frank_bot that can be updated. i heard lemmy 0.18.3 (out last night) has quite a bit of db optimizations, so don’t want any outdated reference to cause issues with that.
I tried checking the foreign key contrainsts in the db but it seems like there aren’t any tables referencing actor_id, usually just the id(PK column) of the person table.
okay, anyway maybe there’ll be a lemmy 0.18.4 soon.
they’re finding all sorts of bugs including a duplicate comment bug, and another one that makes the lemmy version in the instances list become 2.0 instead of 0.18.x.
i wonder if someone was dreaming about an early lemmy 2.0, lol.
@[email protected] I updated the db and it seems like it’s fixed. Thanks for helping! The solution was the actor_id for the user account was still pointing to Frank_Bot URL, which is already invalid.
oh that’s nice, may i know what sql statement you used?
anyway, time to upvote everything in this thread so it federates over 🤣
I’m going to open a github issue on this so I’ll just link it here later haha
Oh wait… sorry @[email protected] I just realized I made a mistake there. T_T You actually cannot change your account name(only your display name) which I now understand the reason. I changed the account name a long time ago so I forgot that I changed the account name manually via the database without updating the actor_id and inbox_url correctly. E.g. the actor_id should be https://monyet.cc/u/MonyetBot instead of https://monyet.cc/u/Frank_Bot, which was the old URL.
The reason you can’t change your account name is most probably everything relies on the actor_id to work, and if the actor_id is invalid, it won’t be able to federate. Even if they updated the actor_id and inbox_url, all your past post, comments and messages etc. should be tied to the old url, which won’t carry over after you change your account name.
luckily we caught this early before monyetbot had a lot of posts. anyway, i think what’s even more important is the keypair in the db, so it is good the problems monyetbot had were not related to that.
by the way, you may want to do a sql dump and search if there’s any other reference to
frank_botthat can be updated. i heard lemmy 0.18.3 (out last night) has quite a bit of db optimizations, so don’t want any outdated reference to cause issues with that.I tried checking the foreign key contrainsts in the db but it seems like there aren’t any tables referencing actor_id, usually just the id(PK column) of the person table.
okay, anyway maybe there’ll be a lemmy 0.18.4 soon.
they’re finding all sorts of bugs including a duplicate comment bug, and another one that makes the lemmy version in the instances list become
2.0instead of0.18.x.i wonder if someone was dreaming about an early lemmy 2.0, lol.
lol 2.0 😂