https://lemmy.globe.pub is an instance I'm setting up as a community for world travelers. Thanks!
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.
Hello! I am working through some issues with federation between my own server, https://globe.pub, and all other Lemmy servers.
When I subscribe to a community on a foreign server (e.g. https://lemmy.world/c/world), I get an error saying Activity was rejected by https://lemmy.world/inbox, aborting: Incoming activity has invalid signature.
I'm having trouble figuring out what is misconfigured on my server. Does anyone have advice on how I can resolve this?
Below are my debug logs for a failed subscription request:
2023-07-16T20:05:17.562556Z DEBUG activitypub_federation::activity_queue: Sending https://globe.pub/activities/follow/7dec89e1-eea0-4265-98c4-8e927fde3f6f to https://lemmy.world/inbox, contents: {"@context":["https://www.w3.org/ns/activitystreams","https://w3id.org/security/v1",{"lemmy":"https://join-lemmy.org/ns#","litepub":"http://litepub.social/ns#","pt":"https://joinpeertube.org/ns#","sc":"http://schema.org/","ChatMessage":"litepub:ChatMessage","commentsEnabled":"pt:commentsEnabled","sensitive":"as:sensitive","matrixUserId":"lemmy:matrixUserId","postingRestrictedToMods":"lemmy:postingRestrictedToMods","removeData":"lemmy:removeData","stickied":"lemmy:stickied","moderators":{"@type":"@id","@id":"lemmy:moderators"},"expires":"as:endTime","distinguished":"lemmy:distinguished","language":"sc:inLanguage","identifier":"sc:identifier"}],"actor":"https://globe.pub/u/mplewis","to":["https://lemmy.world/c/world"],"object":"https://lemmy.world/c/world","type":"Follow","id":"https://globe.pub/activities/follow/7dec89e1-eea0-4265-98c4-8e927fde3f6f"} 2023-07-16T20:05:18.250812Z DEBUG activitypub_federation::activity_queue: Activity https://globe.pub/activities/follow/7dec89e1-eea0-4265-98c4-8e927fde3f6f was rejected by https://lemmy.world/inbox, aborting: Incoming activity has invalid signature
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.
Hello! I recently got https://globe.pub up and running and I'd like to get it federated with other instances.
My https://globe.pub/instances page shows that globe.pub can talk to other instances, but it doesn't seem to be pulling in their full metadata properly – the Software or Version columns are entirely empty.
I am receiving some posts from other communities (see attached photo), but only three of them are sending posts my way at all. For any other communities, I am unable to view posts, even when I navigate to them manually, and I do not see any of their posts in my All feed.
I have no communities in my whitelist or blacklist, so my server should be configured to openly federate.
Does anyone know what might be going wrong here? What debugging tips should I try next to diagnose this issue?
Hello, I'm setting up Lemmy + Lemmy-UI + pict-rs on my k8s cluster. I've gotten all the components deployed, and I'm able to access the Lemmy and Lemmy-UI instances via local tunneling. However, I'm having trouble using Lemmy-UI to sign in or administer my instance.
I can successfully POST to /api/v3/user/login against the Lemmy API directly, but this same request fails when made in my browser through Lemmy-UI. Instead of rendering JSON, I receive an HTML "not found" page.
I also see this category of failure on other pages. For example, visiting http://localhost:lemmy-ui-port/communities in my browser makes a request to GET http://localhost:lemmy-ui-port/api/v3/community/list?type_=Local&sort=TopMonth&limit=50&page=1, which returns the Lemmy-UI 404 page rendered as HTML (The page you are looking for does not exist).
It seems like Lemmy-UI is failing to handle requests to /api endpoints properly and is not forwarding them along to the backend.
I've verified that Lemmy-UI can access Lemmy by shelling into the Lemmy-UI container and running these commands successfully:
sh wget $LEMMY_UI_LEMMY_INTERNAL_HOST wget $LEMMY_UI_LEMMY_INTERNAL_HOST/api/v3/community/list
I've included both the successful and failing login requests below. Do you have any idea why I might be seeing this?
---
Making a login request against Lemmy:
``` POST /api/v3/user/login HTTP/1.1 Content-Type: application/json; charset=utf-8
{"username_or_email":"admin","password":"PASSWORD_GOES_HERE"}
HTTP/1.1 200 OK content-type: application/json
{"jwt":"..."} ```
Making a login request through Lemmy-UI, just like the one I see in my browser's Network pane when I use the /login form:
``` POST /api/v3/user/login HTTP/1.1 Content-Type: application/json; charset=utf-8
{"username_or_email":"admin","password":"PASSWORD_GOES_HERE"}
HTTP/1.1 404 Not Found Content-Type: text/html; charset=utf-8
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Error</title> </head> <body> <pre>Cannot POST /api/v3/user/login</pre> </body> </html> ```