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.

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.

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.

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.

I totally agree with your sentiment… However they don’t have a choice. They are legally obligated to turn that information over if they are served a warrant. Doing anything less is obstruction at the very least and they could be shut down and put into receivership.

The fault here is with the two individuals trusting a corporation to keep data private and to put the individuals interests ahead of the corporation. Neither is a realistic expectation.