Subscribing to lemmy works but also fails
from peter@discuss.petersanchez.com to azorius@azorius.net on 19 Aug 2023 00:30
https://discuss.petersanchez.com/g/azorius@azorius.net/p/Km1g7lbQ4TBrn3L4W9-Subscribing-to-lemmy-works-but-also-fails

So on my new azorius install I'm noticing that since my initial group import, no updates have come in on subscribed groups. The exception being this azorius.net. All of my other subscribed groups live in Lemmy instances.

Here's the log entry when I subscribed to it earlier today.

failed to post json to https://lemmy.world/c/world/inbox: http post status: 400

I tried unsubscribing and resubscribing and got this:

2023/08/19 00:12:11 posting to https://lemmy.world/c/world/inbox
2023/08/19 00:12:12 failed to post json to https://lemmy.world/c/world/inbox: http post status: 400
2023/08/19 00:12:19 posting to https://lemmy.world/c/world/inbox
2023/08/19 00:12:20 failed to post json to https://lemmy.world/c/world/inbox: http post status: 400

I notice ALL Lemmy instances have the same error. So I'm thinking I'm not actually subscribed to them on their end and thus they're not pushing me updates.

See current Lemmy group:

https://lemmy.world/c/world?dataType=Post&page=1&sort=New

and now my page:

https://discuss.petersanchez.com/g/world@lemmy.world

I haven't received any of the updates since the UK Nurse story (which was part of the original group import)

Now, I have a clue as to what this may be. Before I setup azorius I ran Lemmy on the same subdomain. So I imagine maybe there is a key mismatch possibly that's blocking things?

If that's potentially the issue, is there any solution? Or do I have to change my hostname?

PS, if these types of post don't belong here, just slap my hand with a ruler and I'll ping you via email or honk or whatever.

#azorius

threaded - newest

tedu@azorius.net on 19 Aug 2023 01:03 collapse
It could be a key issue. You could try with a different user name. I would expect a 401 error, but who knows how anything works. Welp, I believe I've confirmed you get 400 errors when the sig fails.

I think this is probably the right place for tech support for now.