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.
this post was submitted on 08 Oct 2023
35 points (97.3% liked)
Lemmy
12541 readers
42 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
founded 4 years ago
MODERATORS
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.
Do you have any relevant logs to share?
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.
How can I check the logs?
You can use this command to see a live feed of logs
docker compose -p lemmy-easy-deploy logs -f
need to cd ./live first
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.
check your firewall/reverse proxy settings maybe
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.
How does one even check to learn if their content is federating out?
Comment somewhere else off your instance and then view it from the instances community url