# Problem reaching a cluster peer through the REST API

**URL:** <https://discuss.ipfs.tech/t/problem-reaching-a-cluster-peer-through-the-rest-api/9495>\
**Category:** IPFS Cluster\
**Created:** [November 23, 2020, 7:13am UTC](https://discuss.ipfs.tech/t/problem-reaching-a-cluster-peer-through-the-rest-api/9495 "2020-11-23T07:13:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![AleXerZ](https://avatars.discourse-cdn.com/v4/letter/a/cc9497/32.png) [@AleXerZ](https://discuss.ipfs.tech/u/AleXerZ)\
**Post date:** [November 23, 2020, 7:13am UTC](https://discuss.ipfs.tech/t/problem-reaching-a-cluster-peer-through-the-rest-api/9495/1 "2020-11-23T07:13:06Z")

</div>

Hello,

I am trying to build a web interface that would add files to IPFS through my IPFS Cluster network.  
To do so, I know I should try to reach the cluster by reaching /ip4/anyClusterPeerIpAddress/tcp/9094 or via port 9095.

To test if I can first reach one peer via an other peer’s CLI running ipfs-cluster-ctl -l.  
The issue I have doing so, is that whatever peer I try to reach from whatever other peer, I get a connection timeout code 0 error:

```
An error occurred:
  Code: 0
  Message: Get "http://clusterPeerIp:9094/peers": dial tcp clusterPeerIp:9094: i/o timeout

```

My webdev also tried to reach every peer from our web app using [https://github.com/ipfs-cluster/js-cluster-client](https://github.com/ipfs-cluster/js-cluster-client) but for every request sent, we got an empty response, as if the server could not be reached or was sending back nothing.

I have tried many thing with firewalls to make sure the ports were open(which they already should be, as the peers have no trouble reaching eachothers via the 9096 port),  
I have also tried to edit the service.json to allow API requests from any IP:

```
  "api": {
      "ipfsproxy": {
          "listen_multiaddress": "/ip4/0.0.0.0/tcp/9095",
          "node_multiaddress": "/ip4/127.0.0.1/tcp/5001",
     }
  }
"restapi": {
    "http_listen_multiaddress": "/ip4/0.0.0.0/tcp/9094",
}

```

But still no success. If anyone has any ideas of what might be going wrong, I’m open to any suggestions!

---

<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:** [November 23, 2020, 8:36am UTC](https://discuss.ipfs.tech/t/problem-reaching-a-cluster-peer-through-the-rest-api/9495/2 "2020-11-23T08:36:30Z")

</div>

Your configuration seems correct.

An i/o timeout usually means your firewall/router/something is indeed filtering traffic from or to that port. If you can talk to it locally but not from a different location on the network that is a pretty clear signal.

---

<div class="post-metadata">

**Author:** ![AleXerZ](https://avatars.discourse-cdn.com/v4/letter/a/cc9497/32.png) [@AleXerZ](https://discuss.ipfs.tech/u/AleXerZ)\
**Post date:** [November 23, 2020, 8:55am UTC](https://discuss.ipfs.tech/t/problem-reaching-a-cluster-peer-through-the-rest-api/9495/3 "2020-11-23T08:55:48Z")

</div>

I just checked and I can indeed make ipfs-cluster-ctl -l work between two cluster peers operating under the same local internet network (though on 2 different machines).

There might be some extra step I have not done yet, like maybe port forwarding(though I tried) or something of that fashion. I’m kinda stuck here I admit lol

---

<div class="post-metadata">

**Author:** ![AleXerZ](https://avatars.discourse-cdn.com/v4/letter/a/cc9497/32.png) [@AleXerZ](https://discuss.ipfs.tech/u/AleXerZ)\
**Post date:** [November 23, 2020, 3:01pm UTC](https://discuss.ipfs.tech/t/problem-reaching-a-cluster-peer-through-the-rest-api/9495/4 "2020-11-23T15:01:47Z")

</div>

Finally made it work, problem was coming from 2 layers of firewall from my VPS provider that were messing with each others. If anyone encouters the same problem, don’t forget to ask your provider if they have a master firewall lol