Lemmy Support

4651 readers

1 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago

MODERATORS

[email protected]

"Subscribe pending" for all communities on self hosted lemmy instance (lemm.ee)

submitted 1 year ago by [email protected] to c/[email protected]

16 comments fedilink hide all child comments

I recently setup my own lemmy instance per the guide with docker and I have been having issues getting content to my server. I discovered a bunch of communities and instances and started subscribing to some communities to get constant updates. The problem is no matter what I do it is stuck on "subscription pending" and I get no new content on my server. I have been trying to figure this out for a week now, thanks in advance for any help.

top 13 comments

sorted by: hot top controversial new old

[–] [email protected] 8 points 1 year ago (1 children)

Look at your server logs and make sure that POST requests get routed to the lemmy backend, not the frontend. The frontend does not proxy requests to the backend if the frontend doesn't handle it.

Check your NGINX logs and look for POST requests to /inbox as well as /.well-known/webfinger.

You can unsubscribe and subscribe again while tailing the logs to hopefully see the request come in, and make sure it's a 200. If it's a 400 or 404, triple check it's not going to lemmy-ui.

Been there, done that.

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago) (1 children)

So far from tailing access.log I get a status of 200 from subbing and unsubbing from a community. Still stuck on pending though.

[–] [email protected] 2 points 1 year ago (1 children)

Did you get posts to webfinger and inbox coming from the remote instance as well? If you have nothing then the remote instance was unable to push back to you.

You should see a whole bunch of lines like these in the NGINX logs:

54.36.178.108 - - [09/Jul/2023:23:27:08 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.1; +https://lemmy.ml"

If you don't, then that's a problem.

[–] [email protected] 2 points 1 year ago

yeah this appears to be the issue. I have all of the communities and the initial content from discovery but they don't seem to want to talk now.

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (1 children)

Try this script and set it up. It seems to work out the kinks of federation.

[–] [email protected] 2 points 1 year ago (1 children)

Well I already spent the time to set it up manually so I kinda wanna get it working as it is. If nothing else works I might have to give it a shot.

[–] [email protected] 2 points 1 year ago (1 children)

I was on the same boat, then nuked the whole thing and tried that script and it solved my headache instantly.

[–] [email protected] 2 points 1 year ago (1 children)

Hm, well I'll debug this for a lil bit just for the learning experience and just fallback to this if needed.

[–] [email protected] 2 points 1 year ago (1 children)

Good luck 🍀

[–] [email protected] 1 points 1 year ago

Yeah I just broke down and used the script. Shit just worked lol.

[–] [email protected] 3 points 1 year ago

New install of a server... typical Docker proxy setting or Nginx.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

I see this often using any instance other than the one the community is on. It's because the instances need to talk to each other communicating any changes and also approving them. It will do this automatically, it just takes varying amounts of time depending on the queue and distance from each other.

[–] [email protected] 1 points 1 year ago

Make sure your activity pub Is working by using curl to fetch it with the activitypub type. There's instructions on the main Lemmy instance guide.

load more comments