Federation issues on ekk.app
-
[email protected]replied to [email protected] last edited by
@bh4-tech have the server log visible (
tail -f logs/output.log
) when you send activities.Look for error messages or crashes. The day I was sending a reply to your app it was crashing every minute.
-
[email protected]replied to [email protected] last edited by
The latest commits to
activitypub
should re-enable verbose logging for ActivityPub logic, if development mode is enabled (./nodebb dev
or pass inNODE_ENV=development
environment variable) -
[email protected]replied to [email protected] last edited by
Upgraded to latest commits. @[email protected] Is this visible?
-
[email protected]replied to [email protected] last edited by
2024-10-14T01:13:37.325Z [4567/800551] - verbose: [activitypub/get] https://community.nodebb.org/uid/26618#key
2024-10-14T01:13:37.635Z [4567/800551] - verbose: [activitypub/verify] Attempting signed string verification
2024-10-14T01:13:37.637Z [4567/800551] - verbose: [middleware/activitypub] HTTP signature verification failed.
2024-10-14T01:13:41.701Z [4567/800551] - verbose: [activitypub/verify] Starting signature verification...
2024-10-14T01:13:41.701Z [4567/800551] - verbose: [activitypub/verify] Retrieving pubkey for https://community.nodebb.org/uid/26618#key
2024-10-14T01:13:41.703Z [4567/800551] - verbose: [activitypub/verify] Attempting signed string verification
2024-10-14T01:13:41.704Z [4567/800551] - verbose: [middleware/activitypub] HTTP signature verification failed. -
[email protected]replied to [email protected] last edited by
@julian The above is what I get in logs. Apparently, signature verification is failing, nodebb re-tries signature verification but fails every time.
-
[email protected]replied to [email protected] last edited by
Same thing for DMs
2024-10-14T01:18:50.332Z [4567/800636] - verbose: [activitypub/verify] Starting signature verification... 2024-10-14T01:18:50.333Z [4567/800636] - verbose: [activitypub/verify] Retrieving pubkey for https://community.nodebb.org/uid/26618#key 2024-10-14T01:18:50.346Z [4567/800636] - verbose: [activitypub/get] https://community.nodebb.org/uid/26618#key 2024-10-14T01:18:50.666Z [4567/800636] - verbose: [activitypub/verify] Attempting signed string verification 2024-10-14T01:18:50.667Z [4567/800636] - verbose: [middleware/activitypub] HTTP signature verification failed. 2024-10-14T01:18:54.743Z [4567/800636] - verbose: [activitypub/verify] Starting signature verification... 2024-10-14T01:18:54.744Z [4567/800636] - verbose: [activitypub/verify] Retrieving pubkey for https://community.nodebb.org/uid/26618#key 2024-10-14T01:18:54.744Z [4567/800636] - verbose: [activitypub/verify] Attempting signed string verification 2024-10-14T01:18:54.746Z [4567/800636] - verbose: [middleware/activitypub] HTTP signature verification failed.
How to solve the problem?
-
[email protected]replied to [email protected] last edited by
Attempting signed string verification
@bh4-tech that line above means that
ekk.app
is attempting to validate the HTTP signature sent bycommunity.nodebb.org
and is not coming up with the same result. The validation failure means the activity received cannot be trusted and is then dropped.Considering that NodeBB to NodeBB activities are tested as working, I'm inclined to think this is a configuration issue.
Can you please add the following line:
console.log(signed_string);
Right above this line in
src/activitypub/index.js
:// Verify the signature string via public key
... and attempt to send an activity to ekk.app again from here (or from https://activitypub.academy)?
-
[email protected]replied to [email protected] last edited by
@julian This is what I am getting upon logging the signed string as suggested by you.
(request-target): post /inbox host: 127.0.0.1:4567 date: Thu, 17 Oct 2024 14:56:13 GMT digest: SHA-256=x3ALdqJIHsCU66QoCfihAmXAirCQQDj9G63pfoWhsss= content-type: application/activity+json
Is it a host mismatch problem? 127.0.0.1:4567 instead of ekk.app ?
-
[email protected]replied to [email protected] last edited by
Seems I found the solution. One of the required headers was commented in the nginx config file. This coupled with cloudflare proxy was causing the issue. After fixing, I sent a DM to ekk.app and that was successfully received.
Now, shall try a public mention
@[email protected] Did you receive the post? -
Yes, received. So, issue is receolved.
Thanks a lot @[email protected] -
@[email protected] @bh4-tech Glad to hear it is working now