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.-

  • PhilipTheBucket@ponder.cat
    0·
    4 days ago

    It says: The server returned this error: couldnt_find_community. This may be useful for admins and developers to diagnose and fix the error.

    rDataHoarder also doesn’t show in the list of local communities.

    Did you change the domain of your host, after it had already done some federation and created databases, or something like that? I do see the rDataHoarder community in the list of non-local communities, which is a real bad type of error to be seeing. You didn’t do any hacking around in the database to fix things or anything did you? That should never be that way as far as I know.

    • Marmalade3@lemmy.worldOP
      0·
      4 days ago

      Originally, I had set the “hostname” in lemmy.hjson as just “geekroom.tech” but that was causing issues with trying to send email. So I changed it to the hostname of the server prd-pub-pod11.geekroom.tech" … then found out that when it sends emails, it uses that hostname as where to send people to in order to verify and login… no bueno.

      So then I changed it to www.geekroom.tech and now just have a redirect at cloudflare for www to naked domain

      It sounds like I need to reinit the entire install …

      • PhilipTheBucket@ponder.cat
        0·
        4 days ago

        Hm, I would try just changing it back first. Use geekroom.tech. Any community or anything that federated or went into the database, with one of the other hostnames, is probably cursed now, and best just deleted and never looked back on. But, if you try to reinstall, you won’t be able to keep geekroom.tech as the domain at all, you’ll have to pick a new one (or just use a subdomain like lemmy.geekroom.tech).

        Once stuff is federated out from one install under some given domain name, it’s pretty much immutable from that point forward. It probably shouldn’t be that way, but that is the current state of things with ActivityPub being the way that it is unfortunately.

        • Marmalade3@lemmy.worldOP
          0·
          3 hours ago

          Yeahh It’s already changed back to geekroom.tech and is operational. The only thing I wanted to start resolving is the www.geekroom.tech hostname that i’m occasionally seeing in the logs now. I’m sure it’s cursed now lol It sucks that it’s so easy to setup a broken instance and then be forever cursed. :(