Hello! I recently got https://globe.pub up and running and I’d like to get it federated with other instances.

My https://globe.pub/instances page shows that globe.pub can talk to other instances, but it doesn’t seem to be pulling in their full metadata properly – the Software or Version columns are entirely empty.

I am receiving some posts from other communities (see attached photo), but only three of them are sending posts my way at all. For any other communities, I am unable to view posts, even when I navigate to them manually, and I do not see any of their posts in my All feed.

I have no communities in my whitelist or blacklist, so my server should be configured to openly federate.

Does anyone know what might be going wrong here? What debugging tips should I try next to diagnose this issue?

  • RoundSparrow
    link
    fedilink
    English
    18
    edit-2
    1 year ago

    Welcome to the Lemmy network.

    There is a pretty steep learning curve to this, and there have been a lot of little tweaks to the install that it’s hard to know for certain what is causing your problems.

    Lemmy does not bring in messages automatically. You have to subscribe to each community from one user on your server. I see some of your listed communities have zero subscribers: https://globe.pub/communities?listingType=All&page=1

    You also have many that do list 1 subscriber, did it ever go past “pending” for that one user to “joined” for the community?

    Are you running on Ubuntu 22.04 server? How did you do the install?

    • @mplewisOP
      link
      English
      21 year ago

      Sorry for the late response. I was out of town and wanted to give the server a chance to catch up just in case.

      I am running this on a bespoke stack:

      • Kubernetes for lemmy, lemmy-ui, and pict-rs
      • AWS S3 storage backend for pict-rs, with a persistent volume claim for the sled db
      • Postgres “serverless” DB hosted by https://neon.tech/

      For all the communities with 1 subscriber (me), they have not gone from “pending” to “joined” yet, so I am worried there is some issue with establishing communication between the instances.

      • RoundSparrow
        link
        fedilink
        English
        21 year ago

        If you are getting pending to every server you try, your proxy (typically nginx) config might be the problem. You should maybe try some of the curl test to federation endpoints from an outside box and see if something isn’t blocking the connection.

        • @mplewisOP
          link
          English
          11 year ago

          Thanks, I am pretty sure you have uncovered my problem! I am not properly reverse proxying requests with the Accept: application/activity+json header (docs). I will configure this now.