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.
Thanks, I am pretty sure you have uncovered my problem! I am not properly reverse proxying requests with the Accept: application/activity+json header (docs). I will configure this now.
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.
i'm still having trouble federating in from lemmy.globe.pub, so hello from lemmy.world!
Hello there!
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.
sdoijsdfoijsdf
test 2
test
test comment
hello from lemmy.world!
Thanks, I am pretty sure you have uncovered my problem! I am not properly reverse proxying requests with the
Accept: application/activity+jsonheader (docs). I will configure this now.Thank you for the suggestion!
Thanks! I will try your tool out.
Sorry 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:
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.