Pleroma "fe.disroot.org" - ActivityPub node not able to post error 400/401/500 #187
Labels
No Label
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
Fixed
forgejo
fun_project
Goal 2024
help wanted
Howto
In progress
🤔️ Investigate
ios
jitsi
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
question
Ready
refined
Roundcube
searX
spam-protection
Staging Server
Themes
TOR
Urgent!
Website
windows
wontfix
xmpp
Yearly Report
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#187
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Getting another node telling me that they can't post to me. The error on their node says.
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?
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:
Pleroma "fe.disroot.org" - ActivityPub node not able to post error 400to Pleroma "fe.disroot.org" - ActivityPub node not able to post error 400/401I think it was due to proxy vhost settings.
Pleroma "fe.disroot.org" - ActivityPub node not able to post error 400/401to Pleroma "fe.disroot.org" - ActivityPub node not able to post error 400/401/500@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
Is this still issue? Could you provide me with address of the node that does not federate? it will be easier to test.
@muppeth - This seems to still be an issue with this domain.
epicyon.libreserver.org
@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
Is this still the issue?
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.
@PresGas sorry for asking again, but is this still an issue?
Hey, @meaz ! I would say you we can close this, and doing so with this comment. Thanks for checking in!