• flamingos-cant (hopepunk arc)@feddit.uk
    link
    fedilink
    English
    arrow-up
    13
    ·
    edit-2
    4 hours ago

    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.

    • maptoOP
      link
      fedilink
      English
      arrow-up
      9
      ·
      4 hours 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.