I'm not sure why that's happening. I'll try restarting the service to see if that helps at all.
Lemmy.ca's Main Community
Welcome to the lemmy.ca/c/main community!
All new users on lemmy.ca are automatically subscribed to this community, so this is the place to read announcements, make suggestions, and chat about the goings-on of lemmy.ca.
For support requests specific to lemmy.ca, you can use [email protected].
Are you on the most current version of lemmy? I had read that there were improvements recently on how lemmy federates with Mastodon v4, including fixing starting new posts.
yes, we're on the most recent version. it could be just a cosmetic thing too. I will try and follow a lemmy community from mastodon and see what it says in the lemmy db.
so how's that going?
haven't gotten around to it yet. probably won't have a chance this weekend, will report back then.
Sorry for the late answer, haven't seen any notification about the answers.
Unfortunately, the problem is still there. I cancelled the request and tried again - the contact immediately changes back to 'pending request'.
i've done some more investigation into this, and i'm not sure why it's not working. i was able to successfully follow my lemmy account from my mstdn.ca account, however i do get the "Pending Request" thing when trying to do it from my main social.linux.pizza mastodon account.
also, trying to search for communities didn't appear to work at all from mstdn.ca, but it does from social.linux.pizza, but i wasn't able to follow it without getting the "Pending Request" thing. weird.
there isn't any error in the lemmy logs or anything, so i'm not sure what else i can do at this point. i'll ask in the lemmy instance admin matrix channel to see if anyone has any further ideas how i can troubleshoot this issue. the weird part is i'm not consistently seeing the request being logged in my web logs, so maybe the request is being blocked further up? i'll investigate that as well.
i also compared getting the json returned from both a community & user on both lemmy.ca & lemmy.ml, and i couldn't see any obvious differences.
thanks for your patience!
The way follows work in this case is that Mastodon sends a Follow
activity to the Lemmy inbox, and Lemmy responds with Accept
to the Mastodon inbox. If the follow action is stuck as pending, then one of those didnt get delivered properly.
To debug this, grep the logs for the Mastodon domain name while sending a follow. You should have RUST_LOG=...,lemmy_apub=debug,activitypub_federation=debug
in docker-compose.yml. If it works correctly, you should see the incoming Follow
and outgoing Accept
activities being logged. It might also help to get logs from the Mastodon side.
thanks for the info! i will try this when i have some free time, and hopefully be able to get to the bottom of this.
edit:
just tried it. similar to what i found above, i see the Follow and Accept activities being logged when sending a follow request from mtdn.ca
, but not my main account social.linuz.pizza
. it could be it's getting blocked along the way, for whatever reason. will contact the admin for social.linuz.pizza
to see if they can help get this figured out, or if they can provide any more info.
ok, after talking with the admin of social.linux.pizza
, it was because ipv6 wasn't working. once I got that fixed, everything started working again normally.
@[email protected], @[email protected] you may have to contact your mastodon admins and get them to check to make sure lemmy.ca is active or something.
ok, i don't think this issue is fully resolved yet. it seems that ipv6 seems to stop working every once in a while, and just doing a reboot of it appears to fix it. i'm going to contact my vps support to see if they can help.
Thanks for the commitment and success that it works soon. Can hardly wait. 😉
ok, i've made some changes this morning that will hopefully resolve the ipv6 issues. i will continue to monitor it for the next few days to make sure everything is working correctly.
it's been over two days and the ipv6 connection appears to be holding. i will continue to monitor it but i believe the issue has been resolved. 🎉
you will probably need to contact the admin of your instance (or I can if you let me know which instance you're on) so they can re-enable communication with lemmy.ca. from what I understand, since the ipv6 hasn't been working since late January, mastodon will eventually just give up. so the instance admin I contacted said they just pressed a "Start Deliver" button and things started working again on that instance.
A public explanation of where to find this 'start deliver'-button would be super if possible. I might have to notify a few for the my larger community. 😉
edit: tried to open a comment or account from various instances I'm on: Mastodon: brands.town, die-partei.social
Friendica: friendica.xyz, loma.ml
None worked. Maybe I'll rather give up on this.
A public explanation of where to find this ‘start deliver’-button would be super if possible. I might have to notify a few for the my larger community. 😉
i'm not 100% sure sorry, i'm pretty sure it's just something a mastodon admin has access to.
edit: tried to open a comment or account from various instances I’m on: Mastodon: brands.town, die-partei.social
Friendica: friendica.xyz, loma.ml
None worked. Maybe I’ll rather give up on this.
i'm not sure what you mean by this? do you mean you tried to follow your lemmy.ca account from those instances and none worked?
i’m not sure what you mean by this? do you mean you tried to follow your lemmy.ca account from those instances and none worked?
this plus explicit search for a post to open like https://lemmy.ca/comment/139287. Says nothing found as if it would not exist.
fyi: This is what I see if I'm trying to join a lemmy.ca-community from friendica.xyz which I can do without issues on other Lemmy-instances:
The network type was not detected. The contact cannot be added.
The specified profile address provides insufficient information.
No compatible communication protocols or feeds were found.
The network type was not detected. The contact cannot be added.
hmmm, weird, i'll look into this.
It's probably DNS. Somehow, it's always DNS.
🤣 i think i fixed it! and for once it wasn't dns! 🎊