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.

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:

• 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.

i'm still having trouble federating in from lemmy.globe.pub, so 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+json header (docs). I will configure this now.

Thank you for the suggestion!

hello from lemmy.world!

test comment

test

test 2

Hello there!

sdoijsdfoijsdf

Thanks! I will try your tool out.