Hello all,

I am trying to understand what I need to do to ensure that my Lemmy instance can be federated, found, and usable with other instances and users.

Currently, the issues I’m running into are:

  • If I search for my own user@myInstance.tld from any other instance, nothing comes up.

  • When I try to add my instance to FediDB.org, it shows that my “Instance is invalid, unreachable or unavailable.”

  • When I subscribe to other communities from my instance, I am seeing posts, but no comments appear at all. I have verified that those same threads appear on the instance that they are generated on. (My understanding is that I should be able to see these comments and be able to respond to them)

  • All of the other communities that I have attempted to subscribe to are showing “Subscribe Pending”, but the 2 communities that I’ve created on my instance are obviously showing as Joined.

I know I’m asking a lot, but it seems to me that obviously something is misconfigured, or I’m using Lemmy wrong.

What am I doing wrong? I can post configs if needed.-

  • Mel@lemmy.melissandre.devEnglish
    0·
    5 days ago

    You should put the lemmy-ui’s port (8635) first then in the conditions blocks, the lemmy’s port

    set $proxpass "http://0.0.0.0/:{{ lemmy_ui_port }}";
if ($http_accept = "application/activity+json") {
set $proxpass "http://0.0.0.0/:{{ lemmy_port }}";
}
if ($http_accept = "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams/"") {
set $proxpass "http://0.0.0.0/:{{ lemmy_port }}";
}
proxy_pass $proxpass;

    https://join-lemmy.org/docs/administration/troubleshooting.html

    • Marmalade3@lemmy.worldOP
      0·
      4 days ago

      So when I look at the docker-compose file, the only exposures are 10633 on nginx-proxy which routes to 8536. Docker ps -a is showing lemmy-ui as 1234/tcp and lemmy as 8536.

      CONTAINER ID   IMAGE                                   COMMAND                  CREATED        STATUS                  PORTS                               NAMES
530dd3852e24   nginx:1-alpine                          "/docker-entrypoint.…"   15 hours ago   Up 15 hours             80/tcp, 127.0.0.1:10633->8536/tcp   geekroomtech-proxy-1
e5976396c4f2   dessalines/lemmy-ui:0.19.9              "docker-entrypoint.s…"   15 hours ago   Up 15 hours (healthy)   1234/tcp                            geekroomtech-lemmy-ui-1
a91f86523a95   dessalines/lemmy:0.19.9                 "lemmy_server"           15 hours ago   Up 15 hours             8536/tcp                            geekroomtech-lemmy-1
15c8a65b2e02   asonix/pictrs:0.5.16                    "/sbin/tini -- /usr/…"   15 hours ago   Up 15 hours             6669/tcp, 8080/tcp                  geekroomtech-pictrs-1
135f75ceccf4   pgautoupgrade/pgautoupgrade:17-alpine   "/usr/local/bin/dock…"   15 hours ago   Up 15 hours (healthy)   5432/tcp                            geekroomtech-postgres-1

      So you’re saying it should look like this instead?

      set $proxpass "http://0.0.0.0/:1234";
if ($http_accept = "application/activity+json") {
set $proxpass "http://0.0.0.0/:8536";
}
if ($http_accept = "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams/"") {
set $proxpass "http://0.0.0.0/:8536";
}
proxy_pass $proxpass;

      is that right?

        • Marmalade3@lemmy.worldOP
          0·
          4 days ago

          I had to set it as this because if I used port 1234 for lemmy-ui then it would give me 502 bad gateway errors.

                  set $proxpass "http://127.0.0.1:10633/";
        if ($http_accept = "application/activity+json") {
        set $proxpass "http://127.0.0.1:8536/";
        }
        if ($http_accept = "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams/"") {
        set $proxpass "http://127.0.0.1:8536/";
        }

          But this works.