- 4 Posts
- 4 Comments
Joined 2 years ago
Cake day: July 10th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
mplewis@lemmy.worldOPtoLemmy Support@lemmy.ml•My instance isn't federating with others very well. What's wrong?English1·2 years agoThank you for the suggestion!
mplewis@lemmy.worldOPtoLemmy Support@lemmy.ml•My instance isn't federating with others very well. What's wrong?English1·2 years agoThanks! I will try your tool out.
mplewis@lemmy.worldOPtoLemmy Support@lemmy.ml•My instance isn't federating with others very well. What's wrong?English2·2 years agoSorry for the late response. I was out of town and wanted to give the server a chance to catch up just in case.
I am running this on a bespoke stack:
- Kubernetes for lemmy, lemmy-ui, and pict-rs
- AWS S3 storage backend for pict-rs, with a persistent volume claim for the sled db
- Postgres “serverless” DB hosted by https://neon.tech/
For all the communities with 1 subscriber (me), they have not gone from “pending” to “joined” yet, so I am worried there is some issue with establishing communication between the instances.
What I discovered is this was due to me running a past instance of Lemmy on this domain, then wiping it and losing the instance/user public keys. So all the servers I’ve talked to in the past have a public key in mind for globe.pub which no longer exists. I think this means that the domain is no longer usable for federation, as instances don’t prune dead instances from their list.