# Cluster add --wait fails

**URL:** <https://discuss.ipfs.tech/t/cluster-add-wait-fails/15970>\
**Category:** Help\
**Tags:** ipfs-cluster\
**Created:** [February 12, 2023, 12:09pm UTC](https://discuss.ipfs.tech/t/cluster-add-wait-fails/15970 "2023-02-12T12:09:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rvalle](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/rvalle/32/2947_2.png) [@rvalle](https://discuss.ipfs.tech/u/rvalle)\
**Post date:** [February 12, 2023, 12:09pm UTC](https://discuss.ipfs.tech/t/cluster-add-wait-fails/15970/1 "2023-02-12T12:09:10Z")

</div>

Hi!

After adding a third member to my IPFS cluster, adding with wait flag has started to fail like:

```auto
 ${IPFS_CLUSTER_CTL} add --wait --quieter --format car ${CONTENT_CAR} 
panic: interface conversion: multiaddr.Multiaddr is nil, not *multiaddr.multiaddr
goroutine 23 [running]:
github.com/multiformats/go-multiaddr.(*multiaddr).UnmarshalJSON(0xc000410360, {0xc0002b64fc, 0x5f, 0x304})
	github.com/multiformats/go-multiaddr@v0.6.0/multiaddr.go:105 +0xe8
github.com/ipfs-cluster/ipfs-cluster/api.(*Multiaddr).UnmarshalJSON(0xc001234850, {0xc0002b64fc, 0x5f, 0x304})
	github.com/ipfs-cluster/ipfs-cluster@v1.0.2/api/types.go:528 +0x74
encoding/json.(*decodeState).literalStore(0xc000430630, {0xc0002b64fc, 0x5f, 0x304}, {0xe9dca0?, 0xc001234850?, 0x197?}, 0x0)
	encoding/json/decode.go:871 +0x1f2c
...

No idea why....

I have verified that each peer in the cluster see the other 2, so, I assume the cluster is well formed.

What could be going on?
```

---

<div class="post-metadata">

**Author:** ![rvalle](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/rvalle/32/2947_2.png) [@rvalle](https://discuss.ipfs.tech/u/rvalle)\
**Post date:** [February 13, 2023, 8:29am UTC](https://discuss.ipfs.tech/t/cluster-add-wait-fails/15970/2 "2023-02-13T08:29:14Z")

</div>

This message is also taking place with other cluster operations, such as adding a pin.

---

<div class="post-metadata">

**Author:** ![rvalle](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/rvalle/32/2947_2.png) [@rvalle](https://discuss.ipfs.tech/u/rvalle)\
**Post date:** [February 13, 2023, 8:49am UTC](https://discuss.ipfs.tech/t/cluster-add-wait-fails/15970/3 "2023-02-13T08:49:36Z")

</div>

looks like upgrading ipfs-cluster-ctl from 1.0.2 to 1.0.5 resolves the issue.

---

<div class="post-metadata">

**Author:** ![hector](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/hector/32/178_2.png) [@hector](https://discuss.ipfs.tech/u/hector)\
**Post date:** [February 13, 2023, 10:49am UTC](https://discuss.ipfs.tech/t/cluster-add-wait-fails/15970/4 "2023-02-13T10:49:41Z")

</div>

If you were using Kubo \>= v0.18, it was probably [ipfs v0.18: "ipfs does not seem to be available after x retries" · Issue #1835 · ipfs-cluster/ipfs-cluster · GitHub](https://github.com/ipfs-cluster/ipfs-cluster/issues/1835)