Pleroma "fe.disroot.org" - ActivityPub node not able to post error 400/401/500 #187

Closed
opened 2021-12-17 20:20:35 +01:00 by PresGas · 10 comments

Getting another node telling me that they can't post to me. The error on their node says.

Post to https://fe.disroot.org/users/presgas/inbox is unauthorized. Code 400

To them it looks like they let me follow them. To my end it looks like I am waiting for them to approve my follow request.

Are you seeing any log entries of 400/401 errors for inbox urls on our end?

Getting another node telling me that they can't post to me. The error on their node says. > Post to https://fe.disroot.org/users/presgas/inbox is unauthorized. Code 400 To them it looks like they let me follow them. To my end it looks like I am waiting for them to approve my follow request. Are you seeing any log entries of 400/401 errors for inbox urls on our end?
Author

I was able to get a relevant entry from the user and node I have been attempting to connect with. Pasting here with some redaction. Can you see if there is a matching entry on your end? The timestamp here is UK time:

Dec 17 19:33:21 activitypub.server python3[1323664]: WARN: threadSendPost: Post is unauthorized https://fe.disroot.org/users/presgas/inbox {"@context": "https://www.w3.org/ns/activitystreams", "type": "Accept", "actor": "https://node.activitypub.server/users/username", "to": ["https://fe.disroot.org/users/presgas"], "cc": [], "object": {"@context": ["https://www.w3.org/ns/activitystreams", "https://fe.disroot.org/schemas/litepub-0.1.jsonld", {"@language": "und"}], "actor": "https://fe.disroot.org/users/presgas", "cc": [], "id": "https://fe.disroot.org/activities/69e77383-810f-401f-b2f0-3f26211ad278", "object": "https://node.activitypub.server/users/username", "state": "pending", "to": ["https://node.activitypub.server/users/username"], "type": "Follow"}, "signature": {"type": "RsaSignature2017", "creator": "https://node.activitypub.server/users/username#main-key", "created": "2021-12-17T19:28:40Z", "signatureValue": "hugesigline=="}}
I was able to get a relevant entry from the user and node I have been attempting to connect with. Pasting here with some redaction. Can you see if there is a matching entry on your end? The timestamp here is UK time: ``` Dec 17 19:33:21 activitypub.server python3[1323664]: WARN: threadSendPost: Post is unauthorized https://fe.disroot.org/users/presgas/inbox {"@context": "https://www.w3.org/ns/activitystreams", "type": "Accept", "actor": "https://node.activitypub.server/users/username", "to": ["https://fe.disroot.org/users/presgas"], "cc": [], "object": {"@context": ["https://www.w3.org/ns/activitystreams", "https://fe.disroot.org/schemas/litepub-0.1.jsonld", {"@language": "und"}], "actor": "https://fe.disroot.org/users/presgas", "cc": [], "id": "https://fe.disroot.org/activities/69e77383-810f-401f-b2f0-3f26211ad278", "object": "https://node.activitypub.server/users/username", "state": "pending", "to": ["https://node.activitypub.server/users/username"], "type": "Follow"}, "signature": {"type": "RsaSignature2017", "creator": "https://node.activitypub.server/users/username#main-key", "created": "2021-12-17T19:28:40Z", "signatureValue": "hugesigline=="}} ```
PresGas changed title from Pleroma "fe.disroot.org" - ActivityPub node not able to post error 400 to Pleroma "fe.disroot.org" - ActivityPub node not able to post error 400/401 2021-12-18 17:23:20 +01:00
muppeth added this to the (deleted) milestone 2021-12-18 23:38:56 +01:00
muppeth added the
bug
Akkoma
labels 2021-12-18 23:39:06 +01:00
Owner

I think it was due to proxy vhost settings.

I think it was due to proxy vhost settings.
PresGas changed title from Pleroma "fe.disroot.org" - ActivityPub node not able to post error 400/401 to Pleroma "fe.disroot.org" - ActivityPub node not able to post error 400/401/500 2021-12-30 16:08:29 +01:00
Author

@muppeth - I am reopening this again as the same server is still not able to communicate with fe.disroot.org.

The server admin is seeing 400 and 500 errors in their logs as return codes from fe.disroot:

Failed to post to https://fe.disroot.org/users/muppeth/inbox status code 500

sharedInboxUrl: https://fe.disroot.org/inbox127.0.0.1 - - [30/Dec/2021 14:45:27] "GET /users/bob/statuses/107536314487342008 HTTP/1.1" 400

@muppeth - I am reopening this again as the same server is still not able to communicate with fe.disroot.org. The server admin is seeing 400 and 500 errors in their logs as return codes from fe.disroot: Failed to post to https://fe.disroot.org/users/muppeth/inbox status code 500 sharedInboxUrl: https://fe.disroot.org/inbox127.0.0.1 - - [30/Dec/2021 14:45:27] "GET /users/bob/statuses/107536314487342008 HTTP/1.1" 400
PresGas reopened this issue 2021-12-30 16:13:39 +01:00
fede added this to the (deleted) project 2022-01-07 21:46:57 +01:00
Owner

Is this still issue? Could you provide me with address of the node that does not federate? it will be easier to test.

Is this still issue? Could you provide me with address of the node that does not federate? it will be easier to test.
Author

@muppeth - This seems to still be an issue with this domain.

epicyon.libreserver.org

@muppeth - This seems to still be an issue with this domain. epicyon.libreserver.org
Author

@muppeth - I messaged bob who runs the node epicyon.libreserver.org and he is still seeing a 500 error trying to post to our node.

Failed to post to https://fe.disroot.org/users/presgas/inbox status code 500

@muppeth - I messaged bob who runs the node epicyon.libreserver.org and he is still seeing a 500 error trying to post to our node. `Failed to post to https://fe.disroot.org/users/presgas/inbox status code 500`
Owner

Is this still the issue?

Is this still the issue?
Author

Yes, this person I have been following; I see nothing from him and he says he is getting those 500 errors from his server logs when contacting fe.disroot.org.

Yes, this person I have been following; I see nothing from him and he says he is getting those 500 errors from his server logs when contacting fe.disroot.org.
Owner

@PresGas sorry for asking again, but is this still an issue?

@PresGas sorry for asking again, but is this still an issue?
Author

Hey, @meaz ! I would say you we can close this, and doing so with this comment. Thanks for checking in!

Hey, @meaz ! I would say you we can close this, and doing so with this comment. Thanks for checking in!
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Disroot/Disroot-Project#187
No description provided.