I’m experimenting with hosting my own instance. It seems like things are working, e.g. the steps in the troubleshooting doc work, http routing seems correct, etc. I can subscribe to other instance’s communities and see the posts. However, comments are not syncing at all not even new ones. I suspected it might be a lemmy.ml problem, but I also get this behavior from other instances as well. I am running 0.17.3. How do I debug this, or is it the expected behavior (new to Lemmy, of course).
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
#backendcomment 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/inboxrule. 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.