# ERROR | the item is unexpectedly not pinned on IPFS

**URL:** <https://discuss.ipfs.tech/t/error-the-item-is-unexpectedly-not-pinned-on-ipfs/3684>\
**Category:** Help\
**Tags:** ipfs-cluster\
**Created:** [August 21, 2018, 1:15pm UTC](https://discuss.ipfs.tech/t/error-the-item-is-unexpectedly-not-pinned-on-ipfs/3684 "2018-08-21T13:15:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![przemeko](https://avatars.discourse-cdn.com/v4/letter/p/c5a1d2/32.png) [@przemeko](https://discuss.ipfs.tech/u/przemeko)\
**Post date:** [August 21, 2018, 1:15pm UTC](https://discuss.ipfs.tech/t/error-the-item-is-unexpectedly-not-pinned-on-ipfs/3684/1 "2018-08-21T13:15:21Z")

</div>

My env:  
**Ubuntu Linux** x86\_64 x86\_64  
ipfs version **0.4.17**  
ipfs-cluster-service version: **0.4.0**

I have ipfs cluster with 3 servers with default configuration.  
When i upload file to cluster (using proxy):

> curl -v “[http://localhost:9095/api/v0/add](http://localhost:9095/api/v0/add)” -F file=@filename

everything seems to be fine :

> ipfs-cluster-ctl --debug status QmWfvQz47x5eZH1XtMaQZY1HdGmHDNaVfiGu5W6jp9qQNe

> QmWfvQz47x5eZH1XtMaQZY1HdGmHDNaVfiGu5W6jp9qQNe :  
> \> Peer xxxxxxxx1 : PINNED  
> \> Peer xxxxxxxx2 : PINNED  
> \> Peer xxxxxxxx3 : PINNED

But after couple of minutes when i check again it fails:

> ipfs-cluster-ctl --debug status QmWfvQz47x5eZH1XtMaQZY1HdGmHDNaVfiGu5W6jp9qQNe

> 12:56:38.146 DEBUG cluster-ct: Using http(s) to /ip4/127.0.0.1/tcp/9094 app.go:235  
> 12:56:38.146 DEBUG apiclient: GET: [http://127.0.0.1:9094/pins/QmWfvQz47x5eZH1XtMaQZY1HdGmHDNaVfiGu5W6jp9qQNe?local=false](http://127.0.0.1:9094/pins/QmWfvQz47x5eZH1XtMaQZY1HdGmHDNaVfiGu5W6jp9qQNe?local=false) request.go:14  
> 12:56:38.150 DEBUG apiclient: Response body: {“cid”:“QmWfvQz47x5eZH1XtMaQZY1HdGmHDNaVfiGu5W6jp9qQNe”,“peer\_map”:{“xxxxxxx1”:{“cid”:“QmWfvQz47x5eZH1XtMaQZY1HdGmHDNaVfiGu5W6jp9qQNe”,“peer”:“xxxx”,“status”:“pin\_error”,“timestamp”:“2018-08-21T11:58:49Z”,“error”:“the item is unexpectedly not pinned on IPFS”},“xxxxxxx2”:{“cid”:“QmWfvQz47x5eZH1XtMaQZY1HdGmHDNaVfiGu5W6jp9qQNe”,“peer”:“xxxx”,“status”:“pin\_error”,“timestamp”:“2018-08-21T11:58:55Z”,“error”:“the item is unexpectedly not pinned on IPFS”},“xxxxxxx3”:{“cid”:“QmWfvQz47x5eZH1XtMaQZY1HdGmHDNaVfiGu5W6jp9qQNe”,“peer”:“xxxx”,“status”:“pin\_error”,“timestamp”:“2018-08-21T12:03:39Z”,“error”:“the item is unexpectedly not pinned on IPFS”}}}  
> request.go:18  
> QmWfvQz47x5eZH1XtMaQZY1HdGmHDNaVfiGu5W6jp9qQNe :  
> \> Peer xxxxxxx1 : ERROR | the item is unexpectedly not pinned on IPFS  
> \> Peer xxxxxxx2 : ERROR | the item is unexpectedly not pinned on IPFS  
> \> Peer xxxxxxx3 : ERROR | the item is unexpectedly not pinned on IPFS

Any suggest how to handle / debug / fix it ?

PS. When i list pinned files (ipfs pin ls) - i see this file on every peer

> ipfs pin ls | grep QmWfvQz47x5eZH1XtMaQZY1HdGmHDNaVfiGu5W6jp9qQNe  
> QmWfvQz47x5eZH1XtMaQZY1HdGmHDNaVfiGu5W6jp9qQNe direct

---

<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:** [August 21, 2018, 6:26pm UTC](https://discuss.ipfs.tech/t/error-the-item-is-unexpectedly-not-pinned-on-ipfs/3684/2 "2018-08-21T18:26:29Z")

</div>

hi @przemeko, unfortunately this is a bug in 0.4.0.

But it’s been fixed in master, and today or tomorrow in 0.5.0-rc1.

Note that the proxy /add endpoint will now do a “cluster add”. Preliminary changelog: [https://github.com/ipfs/ipfs-cluster/blob/fc48578df4b8e30b9d971ab4319c00670937ebf4/CHANGELOG.md](https://github.com/ipfs/ipfs-cluster/blob/fc48578df4b8e30b9d971ab4319c00670937ebf4/CHANGELOG.md)

---

<div class="post-metadata">

**Author:** ![przemeko](https://avatars.discourse-cdn.com/v4/letter/p/c5a1d2/32.png) [@przemeko](https://discuss.ipfs.tech/u/przemeko)\
**Post date:** [August 21, 2018, 6:44pm UTC](https://discuss.ipfs.tech/t/error-the-item-is-unexpectedly-not-pinned-on-ipfs/3684/3 "2018-08-21T18:44:07Z")

</div>

@hector sounds great!  
Thank You for your time.