As the title says… I moved my lemmy instance from one host to a new host. The domain remains the same.

Initially, I just started up a new lemmy instance and repointed the domain, as I’m the only user I care about on my instance at the moment.

I have incoming federated content, which seems to be fine. But if I respond to a message or post a new message on a federated community, it never shows up outside my server.

Thinking there may be some sort of AP ID that is unique to my install, I copied over the entire Postgres database to my new instance and restored from there. Everything came up as expected and everything works, but the same problem remains.

I’m not sure how to even diagnose what’s going on.

Can anyone tell me what might be happening and how to fix it? Everything seems to be working just fine as it should, content is coming in… but if I post anything, nothing seems to go out to the wider Fediverse.

I’m ok with blowing everything out and starting from scratch, but that didn’t seem to work, either. Everything comes in just fine, even if I send myself a PM from another instance, it shows up immediately. Replying to that PM, though, and nothing goes out.

I don’t quite know what to do.

  • luxyr42@lemmy.dormedas.comEnglish
    5·
    1 year ago

    Are you using the same user name? I had a similar issue with my local instance, ended up just having to make a new user name, since the previous one was already known about, even though all of the other instance says was different. So it wouldn’t federated my posts and comments. Admin tried a bunch of stuff to no avail.

    • 2MnyDcksOnThDncFlr@lemmy.worldOPEnglish
      3·
      1 year ago

      I created a new user just now on my instance and it’s stuck in “Subscribe pending” for communities. I ran into that same issue when I started a fresh copy of the instance as well. As such, I don’t think any of the information from my instance is getting out to the Fediverse (such as subscribes) and thus my new user can’t be searched from other instances, either.

      Is it possible that there’s some NGINX blocking something? I can’t imagine there’s any outgoing issues, and as I said, incoming appears to work perfectly, which is why I’m at a loss here.

    • 2MnyDcksOnThDncFlr@lemmy.worldOPEnglish
      2·
      1 year ago

      I’m not even sure how to obtain those logs?

      I’m using the Lemmy Easy Deploy, as the docs for installing from Ansible appear to be out of date/don’t work.

        • 2MnyDcksOnThDncFlr@lemmy.worldOPEnglish
          1·
          1 year ago

          Yeah I’ve done that; there’s a ton of data so I’m not sure what to look for specifically. All my federated connections flow through that log, so it’s constant scrolling with lots of irrelevant data, plus it looks like there’s some bugs in Lemmy that are throwing exceptions for some incoming federated content (I’m suspecting from older than 0.18.5 servers connecting?) that take up a huge bulk of what’s scrolling. If there something specific I can grep for, I can pull that out, but there’s no human way to sort through what’s there given the volume.

  • JumutaEnglish
    2·
    1 year ago

    check your firewall/reverse proxy settings maybe

    • 2MnyDcksOnThDncFlr@lemmy.worldOPEnglish
      1·
      1 year ago

      Well, like I said incoming is working fine, and firewall/reverse proxy settings are usually tied to incoming, not outgoing… so I’m not sure what to look for in that regards. I agree, it may be something related to that line of thought, but I can’t figure out what it might be.

    • willya@lemmyf.ukEnglish
      1·
      1 year ago

      Comment somewhere else off your instance and then view it from the instances community url