so, I just had created /c/ecriture_libre which was working fine, but now this adress returns a “community not found” error. It is still there, but only reachable if I add @lemmy.ca at the end, like that : https://lemmy.ca/c/[email protected]
Maybe this happened beacuse I modified the community description with a second mod account from beehaw.org while I was also logged with my lemmy.ca account in the same browser ? And it messed up something… ?
Is there a way to rectify this so the normal addres /c/ecriture_libre can be accessed again ? Is it a bad writing in DB ?
By the way, thanks for your time on here :)
that’s really strange. I’ll see if I can see anything weird in the logs/db when I’m at home.
ok, it should working now without the @lemmy.ca on the end. for some reason it wasnt’ flaged as
localin the db, so maybe what you said by editing the description it messed something up. i’m going to try and reproduce the issue and submit a bug to the lemmy dev’s if i can figure it out. thanks!Thanks ! I responded without knowing you had looked into it, because I couldn’t see this latest comment from you in my beehaw account, nor had a notification for it, so I had to search it manually with its fedilink.
And I reproduced the bug : the issue was fixed after you stepped in, but when I modified the content of the community again, it stopped being reachable locally again.
Not sure what triggered it exactly, I did two things from a mod beehaw account like last time it broke (but not logged in a second lemmy/instance account at the same time in the same browser) :
I submitted an issue for this: https://github.com/LemmyNet/lemmy/issues/3017
just editing the description does it, but editing it again with a local user should fix it.
Thanks a lot. I already tried editing with a local user mod though, it didn’t work. The problem is editing the side bar is available to any mod of the community, but editing a post from another mod user is not. So if this issue is also raised by posts from outside mods and I need to log as local mod to fix them, well I can’t.
I’m trying again to confirm.
Edit : No more luck. I tried everything from a local user mod, editing the sidebar again, creating a new post, editing this new post.
https://lemmy.ca/c/ecriture_libre is stil 404
it should be fixed again. i guess editing the sidebar with a local user doesn’t fix the problem.
Good, thanks !
[2] Also, I don’t know if it’s normal, but a post created on Lemmy.ca from my account on Beehaw ends up with one lemmy.ca url (https://lemmy.ca/post/615745), but it’s Fediverse link is actually : https://beehaw.org/post/492361
(Edit : The situation described above seems to be normal)
And when I seach them in Mastodon, only the beehaw link works, the lemmy.ca one shows no results.
Plus when I comment on this post from Mastodon (other account), the comment doesn’t show on Lemmy.ca but it does on the beehaw version of the post… So Federation doesn’t seem to be OK, but I don’t know if it’s related to the issue of community being un-local.
Tell me if I can help with bug reporting to Lemmy devs.
yes, the first part is normal.
I’m aware there’s issues with lemmy.ca and mastodon, but I think only the original “fediverse” link is searchable.
From Mastodon I can’t find any post from Lemmy.ca when the address is like https://lemmy.ca/post/xxxxxxx I tried the same thing with other posts from others instances, there is no issue and I can find posts and comment them, and the comments show up instantly.
Could this be an issue with the hosting provider ?
that’s possible? i’m still trying to look into the issue, it’s a little strange.
I don’t know, I was thinking of ports/domains issues, but Activitypub is all JSON and GET/POST queries right ? So nothing outside of port 80 ? unless API endpoints are on something else like 8080 and there are ports issues with the Hosting… It was only an vague assumption, as you see I’m not an expert.
In any case, to me nothing is visible from Lemmy.ca urls on Mastodon. And I also tried using https://activitypub.academy to verify.
It’s back to normal now. I don’t know if you did something to fix that, but thanks anyway !
I’ll avoid logging with two different Lemmy accounts in the same browser next time, we’ll see if it breaks again…