zamuz

joined 1 year ago
[โ€“] [email protected] 2 points 1 year ago

@jeena if you deployed your instance using the Ansible method, you may be facing the same issue described here:

https://github.com/LemmyNet/lemmy-ansible/issues/106

The solution, which I applied to my instance and confirm it works, is described in one of the comments:

https://github.com/LemmyNet/lemmy-ansible/issues/106#issuecomment-1606222766

I applied those changes (excluding the port changes) to the nginx_internal.conf template in the lemmy-ansible playbook, ran the playbook again and I can now subscribe to Kbin magazines from my Lemmy instance. There's still the weird quirk of having to click the Subscribe button a couple of times (or maybe clicking and refreshing the page) to make sure you're subscribed correctly.

[โ€“] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Last week I subscribed successfully to a couple of Kbin magazines (/m/linux, /m/photography) from my personal Lemmy instance, and federation seems to be working correctly with new posts and comments showing up in my Lemmy instance as expected. Since then, though, any attempts to subscribe to other Kbin magazines have failed. I understand Kbin is under heavy load and @ernest is working overtime, maybe new subscriptions from remote instances are currently paused or disabled?