Why responses from mastodon.social don't arrive to my Lemmy instance?
-
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/115912556149075848All 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?
-
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/115912556149075848All 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?
Assuming you have a standard deployment with docker compose, go to the directory with the
docker-compose.ymlfile and run this:docker compose logs lemmy | lessYou might have to scroll for a bit, you can hit
/then typemastodon.socialthen enter to find occurrences in the logs. Jump to next/previous match by hittingnandN/shift-nrespectively.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. -
Assuming you have a standard deployment with docker compose, go to the directory with the
docker-compose.ymlfile and run this:docker compose logs lemmy | lessYou might have to scroll for a bit, you can hit
/then typemastodon.socialthen enter to find occurrences in the logs. Jump to next/previous match by hittingnandN/shift-nrespectively.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.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.
