Follow activity rejected (federation) #107
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#107
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow activity to plume was rejected with 502. Formatting of key and signature blobs below is messed up from pasting but is correct in the original. This would have also been signed in the header with an HTTP signature. If this assists debugging any, at least one other project failed in a similar way when presented with an inline object for the actor instead of a simple url.
Otherwise the timestamp is 2018-07-02T02:08:18Z
f79f01a
should fix this. It has been deployed on https://baptiste.gelez.xyz if you want to test. If it works correctly feel free to close this issue.Unfortunately same result, 502. Timestamp was 2018-07-09T01:53:07Z
I was hopeful because that certainly looked like it would fix an inline author object, but perhaps we are dealing with multiple issues.
I fixed some issues, but when Plume tries to fetch the new follower's representation (at
https://hub.zilla.tech/channel/baptistegelez
in my tests), Hubzilla responds with an empty body. The following header was present in the request, if it helps:I see what is happening - that site has "block public access" enabled which is preventing access to some urls unless you're logged in (either locally or as a Zot network guest). It looks like this check happens before the ActivityPub plugin gets called. I try to convince folks that this isn't a good option to combine with federation protocols (GNU-Social won't work either because the public feed is blocked); but this may not be adequately documented. I can change the project code to allow the actor document through - as it doesn't contain sensitive or personal information beyond the connection details; but there may be other content exchanges (fetching activities) that will fail.
[edit: no I just tested this scenario on my test site and the activitypub actor document is allowed , so there seems to be a problem specifically with that site. I'll try another connection test to Plume a bit later on - though it's shaping up to be quite a busy day.]
OK, it's probably even simpler than that - visit https://hub.zilla.tech/settings/featured and under 'ActivityPub Protocol Settings' select 'Enable the ActivityPub Protocol for this channel' and submit.
[I just tested adding the Plume connection and still getting 502 at 2018-07-18T23:16:45Z]
@redmatrix That was the solution! I successfully added a Plume connection from Hubzilla. I'll close this issue, but if it doesn't work on your side feel free to re-open it.