Hi,
I just spun up Lemmy 0.17.3 in my kubernetes cluster but I'm having trouble getting it to federate with anything.
I can curl the API endpoints for local posts which all looks good, but all searches fail. In the logs for the backend the stack trace looks like it's failing at trying to resolve the object.
My instance is https://campfyre.nickwebster.dev (which is funny because I briefly ran a hand-made social network called Campfyre from ~2014-2016)
Edit: I am now running 0.18.0 and still have the problem with search.
Edit 2: I added a RUN update-ca-certificates step to my docker container for lemmy_server and now I can do a direct connection (i.e. https://campfyre.nickwebster.dev/c/memes@reddthat.com) although search still fails.
Make sure you don’t have private instance checked. No idea what it does but I noticed in the logs you can’t have both private instance and federation checked. I’m guess private is just that, no federation, just a walled garden, possibly for non-prod and test.
Leave allowed instances blank. Only use blocked to defederate ones that are undesirable.
Start searching instances and communities in the search feature. This will reach out to them and start syncing posts and content.
Also, may want to look into 0.18.0. It doesn’t use web sockets for federation anymore. Which is a lot more efficient and I’m seeing less syncing issues with things like comments.
Also don’t know why numbers don’t show in my replied in mobile
Thanks. I'm not private and that is blank. All searches fail, although it might be federating in the background.
I haven't upgraded to 0.18.0 yet because the Dockerfile I wrote uses the crates.io release to build Lemmy from source but they haven't published 0.18.0 on crates.io yet. I can change that to git though. I'll probably do that tomorrow and see what happens.
How are you searching? The best way I found to load up my instance was to head to this site
https://lemmyverse.net/
Click the house in the top right and input your instance domain. This will reformat everything to the right search term.
Then click the little copy link (it’s the one under the primary instance name). And paste that into searc and mash search a few time. The instance will appear in search after a few tries (heavier trafficked instances are slower to respond). Then just open the instance and subscribe. That will start syncing the community. Your federated instances will slowly grow from there.
Yes, searching is what is not working.