# Can't follow blog/blog not federated

**URL:** <https://discuss.write.as/t/cant-follow-blog-blog-not-federated/2086>\
**Category:** Help\
**Tags:** troubleshooting, writeas\
**Created:** [November 23, 2020, 5:57pm UTC](https://discuss.write.as/t/cant-follow-blog-blog-not-federated/2086 "2020-11-23T17:57:57Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![cjeller1592](https://discuss.write.as/user_avatar/discuss.write.as/cjeller1592/32/128_2.png) [@cjeller1592](https://discuss.write.as/u/cjeller1592)\
**Post date:** [November 23, 2020, 8:25pm UTC](https://discuss.write.as/t/cant-follow-blog-blog-not-federated/2086/2 "2020-11-23T20:25:14Z")

</div>

Hey @oldyogre, the federation is an an issue on our end that we have to address. It’s not an issue with your configuration or anything you’ve done. Here’s a post to add more context:

> [@Federation: can't follow from mastodon with authorized fetch enabled](https://discuss.write.as/t/federation-cant-follow-from-mastodon-with-authorized-fetch-enabled/2063/5):
>
> Thanks, that helps narrow it down! Based on the 401 statuses and [AUTHORIZED\_FETCH](https://docs.joinmastodon.org/admin/config/#authorized_fetch) documentation, I’m assuming WriteFreely is missing some important actor data on that initial fetch (such as public keys), causing later calls to fail. This is on my list to personally investigate more, but we could use help from anyone in the community interested in solving this (especially if you run a WriteFreely instance)! I think as a next step, it’s worth [opening a bug report](https://github.com/writeas/writefreely/issues/new?labels=%E2%9D%93+bug&template=bug_report.md) about this.

Many thanks for outlining your troubleshooting process though! Sorry for the trouble. We’ll definitely keep everyone updated with progress on this issue and would love for people like you to help us test our fixes.

---

_[View the full topic](https://discuss.write.as/t/cant-follow-blog-blog-not-federated/2086)._
