this post was submitted on 18 Jan 2026
25 points (96.3% liked)

Fediverse

40979 readers
47 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, Mbin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)

founded 2 years ago
MODERATORS
 

I suppose this is a problem with the instance, but I have no idea how to debug it.

This is the post https://feddit.bg/post/292412 and this is a comment from a mastodon user that doesn't make it through: https://mastodon.social/@dimkorchev/115912556149075848

All the prerequisites seem to be there, so I suppose the problem is with my instance. Any ideas what I should debug to understand the problem better?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] flamingos@feddit.uk 11 points 1 month ago* (last edited 1 month ago) (1 children)

Assuming you have a standard deployment with docker compose, go to the directory with the docker-compose.yml file and run this:

docker compose logs lemmy | less

You might have to scroll for a bit, you can hit / then type mastodon.social then enter to find occurrences in the logs. Jump to next/previous match by hitting n and N/shift-n respectively.

I was able to fetch the comment without issue (https://feddit.uk/post/42810312/22639417), so it could be something in your setting somewhere. You can try to resolve the comment (go to search in the web UI and past the URL for comment), then after you can run the command above and jump to the end (Alt->) and it should say something about why it failed to resolve.

[โ€“] mapto@feddit.bg 11 points 1 month ago

It showed up now, so I guess it was a matter of synchronisation (9 hours is a lot of time). Probably also has to do with the fact that there's low usage, so few "pull" attempts. I'm not very clear on what are the triggers.

Anyway, your feedback is very useful and now I know that I should be able to see traces in the container logs of lemmy backend.