I just searched for this community, as I wanted to link to their starting guide from my instance. I searched for [email protected] via my instance’s search option, and now while I can visit it, it always appears empty.

  • twitterfluechtling
    1•2 years ago

    I saw the same issue, but would like to provide some additional information (for my case): I searched for https://lemmy.world/c/mildlyinfuriating on my instance. According to https://join-lemmy.org/docs/en/administration/federation_getting_started.html, my expectation was I’ll see the community within a couple of seconds.

    My lemmy-log shows

    > lemmy_1 | 2023-06-12T15:14:49.089405Z ERROR HTTP request{http.method=GET http.scheme=“http” http.host=lemmy.pathoris.de http.target=/api/v3/ws otel.kind=“server” request_id=7c0dd0ef-2766-4e69-b9de-53d1459556ff http.status_code=101 otel.status_code=“OK”}: lemmy_server::api_routes_websocket: couldnt_find_object: Request error: error sending request for url (https://lemmy.world/c/mildlyinfuriating): error trying to connect: dns error: failed to lookup address information: Try again

    My setup is based on docker-compose, https://join-lemmy.org/docs/en/administration/install_docker.html

    Any ideas?

    EDIT: It might be Centos 7 issue with default configuration or something I did in the past :-( I connected to lemmy_1 via docker exec and wasn’t able to initiate any outgoing connection from within the container. Seems I’m filtering it somewhere.

    • twitterfluechtling
      1•2 years ago

      Seems the lemmy-container was supposed to use nginx as a reverse proxy to reach other servers, but for some reason that didn’t work. I added

      lemmy:
    ....
    networks:
        ....
        - lemmyexternalproxy

      Now it works… I assume there should be a better option for me to fix it, maybe something in the nginx.conf or so?