So I’ve recently set up an instance and I’ve run into a strange behaviour that I assume is down to a subtle misconfiguration at my end.
When I attempt to remote follow a user, for example Mastodon (@Mastodon@mastodon.social) - Mastodon I click through the choosing which account to follow from, and end up on the /authorize_interaction page on my own instance which reports:
“Unfortunately, there was an error looking up the remote account”
If I go and find the @email@example.com profile at my end (via Moderation -> Accounts) and look at it, it shows with the hourglass as “Awaiting approval. Click to cancel follow request”.
If I cancel the follow request (and click Unfollow) that seems to work - I can then click the “Follow” button and it seems to work this time - however when I then look at my profile the account doesn’t show up in my follows, and if I reload the profile it again shows the hour glass.
Configuration wise I pretty much followed Installation - Mastodon documentation
For debugging I have checked the nginx logs and see a whole bunch of 200 OK requests.
Checking journalctl for mastodon-web shows:
method=POST path=/api/v1/accounts/4/follow format=html controller=Api::V1::AccountsController action=follow status=200 duration=64.98 view=0.93 db=9.62
Checking journalctl for mastodon-sidekiq shows a bunch of ActivityPub::DeliveryWorker things which have starts and ends and nothing else so probably fine.
Checking journalctl for mastodon-streaming means every time I refresh the local view of the profile page I see (account 2 is mine)
npm: verb 23ae7fe5-692d-4361-9632-d9db794d4ec8 Ending stream for 2
npm: verb Unsubscribe timeline:2
npm: verb e17ea342-6042-4eb9-94b8-446921f1dd2f Starting stream from timeline:2 for 2
npm: verb Subscribe timeline:2
The server is using: