Mastodon don't pushing statuses to GNU-Social instance on same server

Server administration Troubleshooting
#1

Hello.
I’m not getting what is going on about mastodont.cat (Mastodon instance) don’t pushing new statuses to quitter.cat (GNU-Social instance), both on same server.
If I publish a new status from my mastodon.social account, quitter.cat receive it just fine but it don’t received it from mastodont.cat (running v1.5.1, non-docker).
Seems something in mastodont.cat is not working fine. Any clue will be appreciated.

EDIT : above issue only happen to my user account spla : when spla@mastodont.cat publish a new status, quitter.cat’s spla user don’t receive it.
If any other mastodont.cat’s user publish new status, quitter.cat’s spla receive it just fine.

Thanks

#2

First question first, do any users on quitter.cat follow spla@mastodon.cat? Otherwise they won’t appear.

#3

Yes, spla@quitter.cat follows spla@mastodont.cat. Even I tried to unfollow/follow again but no luck.

#4

I have found this dead job in Sidekiq

Mastodon::UnexpectedResponseError: https://quitter.cat/main/salmon/user/1 returned code 400

spla@quitter.cat is user 1.

#5

Nice. I’ve just created new account in mastodont.cat and send some test toots. All of them are received just fine in quitter.cat. So seems is not related to server’s configuration. Why spla@mastodont.cat’s toots can’t reach quitter.cat but proves@mastodont.cat’s ones can without issues?
Strange thing …

1 Like