## 💡 Summary
A friend recently moved to a Mastodon instance that my Misskey instance fully federates with. She has been able to see our accounts and submit follow requests, but we do not receive them. When I attempted to search for her account, the logs output an error.
While troubleshooting, I ended up seeing that I cannot refresh the accounts of anyone on that instance and it kicks out an error. The admin of that instance said everything looks good on his end and his admin panel isn't showing any errors for us. Full information and screenshots below.
## 🙂 Expected Behavior
When I search for a user on a Mastodon instance I federate with, I should see that account come up.
## ☹️ Actual Behavior
When I search for @sourcookie@rage.love, I encounter the error page:
Retry does not have a different result.
The logs show the following:
- 4m ago [remote.resolve-user] WebFinger for sourcookie@rage.love
- 4m ago [remote.resolve-user] return new remote user: sourcookie@rage.love
- 4m ago [api] failed to resolve remote user: [object Object]
While reviewing the logs, I noticed that she replied to a user from her instance that we currently follow, and a 401 error came in the logs regarding us receiving that note:
- 51s ago [remote.ap] Error in inReplyTo https://rage.love/users/sourcookie/statuses/106547988326511288 - 401
- 47s ago [api] Internal error occurred in ap/show: 401 Unauthorized
When I attempt to update any of that instance's users, I get this error:
When I attempt to look at any of their users' ActivityPub info, I get this error:
We are still receiving posts and interactions from the users we are following from that instance:
The instance's admin is filing a ticket with their server provider, but I want to also verify that there is not something wrong on my Misskey instance.
## 📝 Steps to Reproduce
See above.
## 📌 Environment
Misskey v12.83.0