2026-09-03 07:11 UTC
Okay I need help with pleroma federation
for some reason a bunch of instances just don't federate properly anymore, or seemingly only federate one way
looking at the logs I see a bunch of stuff like this
pleroma: Failed-signature inbox retry rejected reason=:invalid_signature payload_actor="https://instance.url/users/username" signature_actor="https://instance.url/users/username" activity_id="https://instance.url/activities/uuid" type="Like" request_path="/inbox"
I don't recall changing anything about signing so I have no idea what the issue may be
edit: okay I realize I won't see replies so uh ping @rose@brain.worm.pink when you do reply
Replies (1)
-
@phnt@fluffytail.org 2026-09-03 07:16
@rose@pl.pinkro.se It's Mastodon doing its weird thing with relaying posts to other instances. The actor in the signature is mismatched with the activity, because Mastodon has to resign the request with a new key and fallback to verifying authenticity with LD Signatures which Pleroma doesn't support. You can ignore these warnings and blame Mastodon for not having an internal flag to stop spamming remote instances with requests that will always fail. What's more likely is that you had 410 HTTP response codes on this instance when it went dead, because Misskey craps out when that happens without doing that, and now Misskey treats this instance as dead.