The strange thing is, in my Lemmy back-end, everything seems normal, and your server is telling mine it’s receiving correctly, but we can see it is not.
/inbox is the endpoint for federation with ActivityPub, so definitely on the right track. Try increasing verbosity to get a full stack traceback to where in the code it’s bugging.
InboxTimeout means your server is taking too long to process API calls to /inbox, I’ve had them before too due to misconfiguration of the reverse proxy. Make sure you’re passing on the right headers, especially the IP headers so they aren’t rate limited and the Accept header so your server knows to send json when requested.
Troubleshooting federation gives many options for testing and checking your configuration, running through them might give your more insight.
Oh, no ! I’ll have to look into that, thank you for noticing ! Any ideas how to debug that ?
No problem haha, I’ve been wanting this for a while already ^^
Interesting !
Thanks again !
Lemmy’s docs show how to increase the verbosity of your logs, taking a look at them could point to possibly issues.
Compare https://blog.kaki87.net/api/v3/federated_instances with https://jlai.lu/api/v3/federated_instances and I don’t think your server is federating properly. This graph of instance health shows federation stopped around 20/06.
Since then, your new posts have federated to for example my server and lemmy.world, but 2 new posts from the last week did not make it to my server.
I tried voting on this post with lemmy.world and the same post with 0d.gs which do not seem to federate but are visible on their respective servers.
The strange thing is, in my Lemmy back-end, everything seems normal, and your server is telling mine it’s receiving correctly, but we can see it is not.
What am I looking for in the logs though ? All I see is “InboxTimeout”…
/inbox is the endpoint for federation with ActivityPub, so definitely on the right track. Try increasing verbosity to get a full stack traceback to where in the code it’s bugging.
InboxTimeout means your server is taking too long to process API calls to /inbox, I’ve had them before too due to misconfiguration of the reverse proxy. Make sure you’re passing on the right headers, especially the IP headers so they aren’t rate limited and the Accept header so your server knows to send json when requested.
Troubleshooting federation gives many options for testing and checking your configuration, running through them might give your more insight.