Yesterday I followed the docker guide for setting up a new KBin instance. Some parts of it are working, but it seems like it's not federating properly.

What does work:

• I can create new local magazines and threads. They show up in my feed.
• I can search for magazines/communities on other instances and they are added to my magazines list (well about 90% anyway)
• I can (un)subscribe to those communities

What does not work:

• If I visit those magazines from my instance, there is no content. Visiting the community on it's home instance shows new content since I subscribed to it on mine.
• Searching for my user from something like Mastodon yields no results; however, I can search for and find my kbin.social account.
• I cannot access my newly created magazine from the kbin.social instance
• (This is probably unrelated) Since I made my admin accout using the kbin:user:create command, I cannot create any other users with it.

Any ideas on where I can look to resolve this?

This reported issue sounds a lot like my situation: https://codeberg.org/Kbin/kbin-core/issues/73

I recently stood up a kbin instance using the Docker guide for testing purposes. I can see the KBin UI, log in with my admin user, create magazines and threads.

1. After creating my admin user using the sudo docker-compose exec php bin/console kbin:user:create command, I cannot seem to create any other users using that method. Additionally, I tried registering as a new user through the site and I neither receive a confirmation email, nor can my admin account "approve" the user.

2. I can search for magazines/communities on other instances (i.e. [email protected]) and about 90% of them will be added to my federated magazines listing. However there is zero content on them if I visit them from my instance; I can see on the host instances that newer content has been added.

Any ideas on either of these items?