this post was submitted on 05 Jun 2023
7 points (100.0% liked)
Lemmy Support
4652 readers
1 users here now
Support / questions about Lemmy.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
For me closely monitoring the reverse proxy logs and the HTTP status therein solved it. Fixing the /inbox routing also fixed the "Susbscription pending" problem for me.
I also have one subscription that has said "Subscription pending" for a while now...
Can you explain what you mean by fixing the /inbox routing? I set up lemmy using ansible and did not set up my own routing: https://github.com/LemmyNet/lemmy-ansible
Anyway, I added "inbox" to the proxy config labeled with a
#backend
comment in the nginx config that the cookbook set up. Fromlocation ~ ^/(api|pictrs|feeds|nodeinfo|.well-known) {...}
tolocation ~ ^/(inbox|api|pictrs|feeds|nodeinfo|.well-known) {...}
. I'm not seeing any immediate difference, but let's see what happens.Also, I'm not sure why it would be like this, but I thought you might want a heads up that this is how your comment appears for me on lemmy.ml, though I can see it fine on my own instance: https://i.imgur.com/pZDRxhz.png
I deleted it because I posted it from my user (not mod) account, so I guess the alt is blown lol. Interesting to see how deletion works/propagates in Lemmy anyhow. I originally had
^/(inbox|api|pictrs|feeds|nodeinfo|.well-known)/
and added an explict/inbox
rule. I found it because I was watching proxy logs and was seeing that path 400, so if you're not seeing 400s in your logs, it's probably something else.