# HOP\_CANT\_SPEAK\_RELAY error when setting up IPFS private network

**URL:** <https://discuss.ipfs.tech/t/hop-cant-speak-relay-error-when-setting-up-ipfs-private-network/13897>\
**Category:** Help\
**Created:** [April 4, 2022, 3:33pm UTC](https://discuss.ipfs.tech/t/hop-cant-speak-relay-error-when-setting-up-ipfs-private-network/13897 "2022-04-04T15:33:39Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![adin](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/adin/32/2679_2.png) [@adin](https://discuss.ipfs.tech/u/adin)\
**Post date:** [April 29, 2022, 10:23pm UTC](https://discuss.ipfs.tech/t/hop-cant-speak-relay-error-when-setting-up-ipfs-private-network/13897/7 "2022-04-29T22:23:19Z")

</div>

Recommend reading the release notes [Release v0.11.0 · ipfs/go-ipfs · GitHub](https://github.com/ipfs/go-ipfs/releases/tag/v0.11.0) which has the relevant information about the recent changes to relay v1 (i.e. unlimited relaying of your data) within go-ipfs. In particular go-ipfs cannot act as a relay v1 server anymore and there is a separate binary you should run for that.

As mentioned in the release notes there’s a standalone relay daemon at [GitHub - libp2p/go-libp2p-relay-daemon: A standalone libp2p circuit relay daemon providing relay service for versions v1 and v2 of the protocol.](https://github.com/libp2p/go-libp2p-relay-daemon/). I don’t think it has support for private swarm keys, but if not you could submit a PR to modify the config to take your key and pass it into the libp2p host, it should be relatively simple to do so.

---

_[View the full topic](https://discuss.ipfs.tech/t/hop-cant-speak-relay-error-when-setting-up-ipfs-private-network/13897)._