Folder not propagating

Help
1

Hey, I’ve been deploying to IPFS for years now. A few months ago I updated a decentralized social network I’m working on (qDesk.org) and started deploying it to IPFS, worked fine, even the version I deployed two weeks ago. But the latest version is not propagating for ~48h now. Unfortunately I don’t have the ability to pin it anywhere but I also don’t think it would help.

It’s available from:
https://35.209.191.77/ipfs/QmTSuYWm2LXyYndEq2W62raSpjjUioSoSW3otSJRFQ1wra/

What would be a good idea to do now? Would really like it to be available from everybody’s favorite Gateway just like the prior versions =)

2

I can only guess that your node is not connected to the main IPFS network for some reason. Check your nodes peer count and/or peers list. My node failed to inspect your CID, so it’s not only an issue with “everyone’s favorite gateway”.

3

These are my peers:

/ip4/104.131.131.82/udp/4001/quic/p2p/QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ
/ip4/116.202.229.43/udp/33529/quic/p2p/12D3KooWF2GuwM8LAVrBuMQqsstT9XmiWhuDUCpWDQwAeSmAeKYm
/ip4/138.201.67.218/udp/4001/quic/p2p/QmbVWZQhCGrS7DhgLqWbgvdmKN7JueKCREVanfnVpgyq8x
/ip4/138.201.67.220/udp/4001/quic/p2p/QmNSYxZAiJHeLdkBg38roksAR9So7Y5eojks1yjEcUtZ7i
/ip4/138.68.224.240/tcp/31006/p2p/12D3KooWEN1NB5qDYbpip4J3ZTNMk8upzBQo2NA4nuFdjxf5to8T
/ip4/138.68.224.240/tcp/31010/p2p/12D3KooWGQQwXLSBm77ijGwxxvTwHQUZgUQLY9dBnY5qQLN1g5eX
/ip4/138.68.224.240/tcp/31013/p2p/12D3KooWNDtS4T3nwFw731TnPJ1cowEeSAcUWmqCQDp45ndpnDZ9
/ip4/138.68.224.240/tcp/31047/p2p/12D3KooWNbGBZp6yFzixKwY1esgmi1A5U7GhUdGELhenQc8DYEDe
/ip4/138.68.224.240/tcp/31056/p2p/12D3KooWP8yrxY4pdSMwdwaVoAiqMH8ZK2Kqw3x4VX8UynWTELcH
/ip4/138.68.224.240/tcp/31072/p2p/12D3KooWLKk1e84nV568zwsrELo4s7sFwyh3arkZWTeqZ9Uv3i22
/ip4/138.68.224.240/tcp/31078/p2p/12D3KooWChqEA6SFxM7u6LkG2UdifUp9ge2k4p1F47kzeqewbYv8
/ip4/138.68.224.240/tcp/31083/p2p/12D3KooWJjDjr1qsbBj7P7yb9f1AHZVbePateE8ENhxd6DdrmL9i
/ip4/138.68.224.240/tcp/31085/p2p/12D3KooWFnkHiCrqdE9L2CX9upcPDNuhr7wDNBGWjWLEYLfMmj7t
/ip4/139.178.88.79/udp/4001/quic/p2p/QmQAVy6RfYcU28W4qLaq3GgGBpFUVMEKQqGMK5EMdEGRjf
/ip4/147.75.100.9/udp/4001/quic/p2p/Qmbut9Ywz9YEDrz8ySBSgWyJk41Uvm2QJPhwDJzJyGFsD6
/ip4/147.75.195.153/udp/4001/quic/p2p/QmW9m57aiBDHAkKj9nmFSEn7ZqrcF1fZS4bipsTCHburei
/ip4/147.75.63.251/udp/4001/quic/p2p/QmYvYcBWoJnbTX4uRL2mcveRrrkDck7LsjTUbgjjQGZoXX
/ip4/147.75.69.147/udp/4001/quic/p2p/QmZMxNdpMkewiVZLMRxaNxUeZpDUb34pWjZ1kZvsd16Zic
/ip4/34.65.215.106/udp/4001/quic/p2p/QmaYAC1yjQvG7Bn1q13Z5KismwFD5VTVjfdxA6gR1NWPNY
/ip4/35.192.122.113/tcp/4001/p2p/QmYufjCdp3SkDgJn1NDGCRpAtR4XwEbomi7fir7ZFhaZMo
/ip4/35.233.189.126/tcp/4001/p2p/QmTiXNcqSSV9inzKXzUbVJ4mc8qov1yXqTEWjAemdbLmVS
/ip4/45.55.43.166/tcp/4001/p2p/QmWpUsfCh7gycv4jteChCP2pg9tRKctnujV7FVJrJxTVKa
/ip4/45.63.74.150/tcp/20011/p2p/12D3KooWGtotR824av3jkpJwcfc39XFhuktwTMPWhHicDYYSGFV2
/ip4/45.63.74.150/tcp/20065/p2p/12D3KooWDmALBvkGqkaNH4CtcLpB3n6YbrMje5Hoh9waKjN13Xps
/ip4/5.196.75.212/tcp/4001/p2p/QmR18dV8CNQBmbn3b1ctjQAvzZMDMj1TVwKKYB5uyeyTzB
/ip4/62.75.168.184/udp/4001/quic/p2p/QmeW92PaNQHJzFM1fJ97JmojmWvGCkyzp1VFj4RURcGZkv
/ip4/64.57.253.21/tcp/4001/p2p/12D3KooWP3F1bTTdoRuE8jNpsWH9fRNPo12BbJNAdap4xshPCsJ9
/ip4/66.42.111.225/tcp/20027/p2p/12D3KooWPRU5K9LP29RBZ8T5M4AC1GMqT73mDJ2yowUD8jooeAVS
/ip4/73.226.111.59/udp/51704/quic/p2p/12D3KooWGJtWvmNad4ZD3Y6nYHAeCQSkvPVdvy1UhTMzNStusJYv
/ip4/80.82.17.10/udp/20409/quic/p2p/QmZatNPNW8DnpMRgSuUJjmzc6nETJi21c2quikh4jbmPKk
/ip4/83.162.42.242/tcp/4001/p2p/QmNLkMi3XXppXMaYzzLrh95KSxcmEwxWDkGCiyxXtbEMXj
/ip4/91.92.144.105/udp/4001/quic/p2p/QmZMq1CfqYaKZRwfmDfxAeLpNaWLdt2bJqFP8aUB8Dr8ym
/ip4/94.130.135.167/udp/4001/quic/p2p/QmUEMvxS2e7iDrereVYc5SWPauXPyNwxcy9BXZrC1QTcHE
/ip4/99.149.215.67/udp/4001/quic/p2p/QmPfAR28wzi7s4BjeH5UVhJPQhGXBojsPe4bGDwZid15jq

4

Nowhere near what I’m used to. My IPFS node currently has 717 peers connected. It runs consistently with >600 peers. Even when my Internet drops, it climbs from 0 back to >500 within 30-60 seconds.

Do you know how many peers you had when your CIDs were accessible via the gateway? I always monitor things when they’re working so I know what might have changed if/when things stop working.

5

About the same amount that’s why I’m so surprised it’s not working now. Maybe it has something to do with the update to 0.7.0?

6

I’m running 0.7.0. My current peers list is at QmaG26NirBVB3s4inkecvtrZCgD6Fv5MiwbSL4AuUZdTyt. See if you can view that CID on your own node’s webui.

7

I can’t cat the list from my node and ipfs.io times out - If you could paste a few peers in here, I could try to manually ipfs swarm connect to them, maybe that helps?

8

https://ipfs.io/ipfs/QmaG26NirBVB3s4inkecvtrZCgD6Fv5MiwbSL4AuUZdTyt shows my list of peers. Came up for me just now, without delay.

10

I’m connected to all your peers that didn’t time out for me now (just ran ipfs swarm connect on the entire list). In case anyone is ever in need: https://github.com/QuestNetwork/qDesk/blob/0.9.4/ipfs-swarm-connect.js

11

I just did an inspect on my node’s webui and am able to view the root directory of QmTSuYWm2LXyYndEq2W62raSpjjUioSoSW3otSJRFQ1wra. So apparently it was a connectivity issue.

I tried the same CID at ipfs.io, and I think it is loading. At least the title of the browser tab has changed to “QuestNetwork Messenger” although the body has not yet arrived.

12

That’s good news then. Do you know if there is a list of peers publicly available in case I or anyone else ever runs into the same problem?

13

You can see the configured bootstrap peers with ipfs bootstrap, or by just looking in the config file.

14

@swedneck unfortunately the bootstraps peer didn’t let @Ideffenb 's and my node connect, I had to connect to his peers manually from the list he posted. So for troubleshooting it would be cool if there was a place where people can always find a list of peers that can get you through to the ipfs.io gateway.

15

@StationedInTheField I am not aware of a public list of peers, sorry.