this post was submitted on 19 Jun 2025
25 points (87.9% liked)
Lemmy
13645 readers
9 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
So, here's the full error :
I've also been seeing this one :
As for the reverse proxy, I'm using Caddy with the configuration provided here, and it's supposed to pass those headers by default.
The suggested
curl
requests work.I wish there was a tool that could just tell what's wrong, like https://federationtester.matrix.org/ for Matrix...
Hmmm, some InboxTimeouts are to be expected. The second one could be the result of a scraper or bot. It's still strange your federation list is empty. I'd take a look at the database, clearing the federation queue (public.federation_queue_state) is a good idea. 'public.instance' should be populated with servers (mine has 2836). Peaking into the log files of the database could give some more insight as well.
A successfully federated incoming action will look like this:
2025-07-14T22:40:54.321151Z INFO HTTP request{http.method=POST http.scheme="http" http.host=0d.gs http.target=/inbox otel.kind="server" request_id=61bf0ea2-8df3-42ff-a433-3bec8b37047c}: actix_web::middleware::logger: 10.10.0.1 'POST /inbox HTTP/1.1' 200 0 '-' 'Lemmy/0.19.12; +https://lemmy.ml/' 0.158242
Your outgoing federation seems to be fine now on my end, this is how my server sees yours:
id 2794; ;domain "blog.kaki87.net"; published "2025-06-30T11:35:32.398830Z" ;updated "2025-07-14T00:42:32.758669Z" ;software "lemmy" ;version "0.19.11" ;federation_state: ;instance_id 2794 ;last_successful_id 46037 ;last_successful_published_time "2025-07-14T21:12:27.481507Z" ;fail_count 0
You could try updating or reinstalling your back-end as well, lemmy is at 0.19.12.