My self hosted instance works in every way for federation, the test curl commands return JSON, I can comment and invite on another federation, and I can retrieve comments and posts by search.
My current problem is my instance does not appear to get updates from other servers when new comments are made. Is there any other troubleshooting or recommended configuration changes I should do?
For context, I am hosting my instance through kurbenetes using nginx-ingress.
I had the same issue and the answer seems to be that it takes some time for comments to sync, especially from busy instances.
I’ve seen this if you don’t have the specific nginx rules set up on the ingress. Check this out and see if it solves your problem: https://lemmy.kutara.io/comment/700
Thanks for the link. I recently did something similar, this fixed my federation issue allowing me to post / comment / upvote. I am wondering now if there is an issue with the proxy config that prevents subscriptions from going through.
I got content updating now. I had to add a nginx deployment with the standard nginx.conf loaded through a config map then used nginx-ingress to proxy the proxy container so that it would be live. Comments and posts are not syncing yet, but I think that may just need some time for the instances to sort themselves out with my instance. I’ll update if I can get comment / posting working or not.
Do you have at least one user who is subscribing to these communities? You’ll need that.
I am subscribing but they all show pending subscription, which I read doesn’t matter usually but a first time setup private instance I was thinking that it might.
Probably want to avoid federation with lemmy.ml right now.
I avoided lemmy.ml since I read some controversy with admins of it, does having it not blocked but not pulling from it cause any issues?
I am not 100% sure since I am still getting up to speed on all this, but I belive there is a bug where its not updating correctly and that is causing posts/votes/mods to not federate correctly. You could block and test to see if that helps.
Yes, it does matter. Unfortunately you will have to try canceling (just tap or click the pending button) and subbing several times until you get lucky and it finally works.
This is sort of a catch 22, because the issue is caused by the server being under load (and some bad code or database queries likely needing to be fixed / optimized / refactored), and clicking the buttons is adding to that load, contributing to the problem.
TL;DR pending subscriptions are not subbed, so do not federate.
On my personal instance, this hasn’t been the case. I’m fully federated with communities that show “subscription pending”. I get comment updates with sub-minute delays. I think this is sometimes just a cosmetic issue.
It does. I’m having that issue a lot with lemmy.ml communities, think it’s an issue on their end.
Try communities on other instances.
I avoided lemny.ml, doing lemmy.world and a few others and those won’t subscribe after retrying a bunch either.
