# Github -\> Issues -\> Here -\> Search -\> Gateway -\> ipfs.io -\> dweb.link **URL:** \ **Category:** Help\ **Created:** [February 21, 2022, 5:06pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540 "2022-02-21T17:06:44Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![dscotese](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/dscotese/32/6049_2.png) [@dscotese](https://discuss.ipfs.tech/u/dscotese)\ **Post date:** [February 21, 2022, 5:06pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/1 "2022-02-21T17:06:44Z")
At Github, it is obvious how devs discover and contribute solutions to issues. It should be that obvious here too, since Github directs users here when they are compelled to submit an issue. On Telegram, my friend @ppmsilver and I discovered that the link at [ipfs.io](http://ipfs.io) for “(PublishingShells.zip)[[https://ipfs.io/ipns/k2k4r8n098cwalcc7rdntd19nsjyzh6rku1hvgsmkjzvnw582mncc4b4/Shells/publishingShells.zip](https://ipfs.io/ipns/k2k4r8n098cwalcc7rdntd19nsjyzh6rku1hvgsmkjzvnw582mncc4b4/Shells/publishingShells.zip)]” which he says comes from a node that currently has between 200 and 1300 peers, but neither of us sees any progress trying to download it. It should also be available at [https://k2k4r8n098cwalcc7rdntd19nsjyzh6rku1hvgsmkjzvnw582mncc4b4.ipns.dweb.link/Shells/publishingShells.zip](https://k2k4r8n098cwalcc7rdntd19nsjyzh6rku1hvgsmkjzvnw582mncc4b4.ipns.dweb.link/Shells/publishingShells.zip) but there’s no progress there either. Our solution currently is for the publisher to send the file directly to whoever wants it. Please let me know if there is more info we can provide. ---
**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\ **Post date:** [February 21, 2022, 6:48pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/2 "2022-02-21T18:48:42Z")
I finally was able to download your file using my node, but it took a really long time (about an hour): ```auto > ipfs dag stat /ipns/k2k4r8n098cwalcc7rdntd19nsjyzh6rku1hvgsmkjzvnw582mncc4b4/Shells/publishingShells.zip Size: 46505, NumBlocks: 1 ``` I’m wondering if your node is actually reachable from the internet. Try this: ```auto > ipfs swarm peers --direction | grep inbound | wc -l 463 ``` If you get 0, that’s a bad sign. ---
**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:** [February 21, 2022, 6:57pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/3 "2022-02-21T18:57:35Z")
I would also try putting your peerID and CID (result of `ipfs name resolve /ipns/k2....`) into [http://ipfs-check.on.fleek.co/](http://ipfs-check.on.fleek.co/). ---
**Author:** ![dscotese](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/dscotese/32/6049_2.png) [@dscotese](https://discuss.ipfs.tech/u/dscotese)\ **Post date:** [February 21, 2022, 10:14pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/4 "2022-02-21T22:14:28Z")
The publishing node reports only two inbound peers. Is there a recommended way to increase the number of inbound peers? ---
**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\ **Post date:** [February 21, 2022, 10:19pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/5 "2022-02-21T22:19:59Z")
My guess is, those 2 nodes are on your local network. This means your node is actually **not** reachable from the internet, which explains why it is so hard to get anything from it. The most likely reason is that you are behind a NAT router and you did not set up port forwarding: > **[NAT configuration | IPFS Docs](https://docs.ipfs.io/how-to/nat-configuration/)** > > Fix common connection issues by managing your routers NAT and forwarding ports so other IPFS nodes can interact with your node. ---
**Author:** ![dscotese](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/dscotese/32/6049_2.png) [@dscotese](https://discuss.ipfs.tech/u/dscotese)\ **Post date:** [February 21, 2022, 10:27pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/6 "2022-02-21T22:27:47Z")
> [@ylempereur](#): > > `/ipns/k2k4r8n098cwalcc7rdntd19nsjyzh6rku1hvgsmkjzvnw582mncc4b4/Shells/publishingShells.zip` The result of the command you provided is: ```auto Error: invalid path "/Shells/publishingShells.zip": unknown namespace "Shells" ``` I tried to look at what might NOT be an “unknown namespace” in that publisher key but every command to which I send `/ipns/k2k4r8n098cwalcc7rdntd19nsjyzh6rku1hvgsmkjzvnw582mncc4b4` returns `Error: not a valid proquint string`. Is that something that isn’t possible? ---
**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\ **Post date:** [February 21, 2022, 10:28pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/7 "2022-02-21T22:28:56Z")
Give me your node ID, I can sniff it from here and determine once and for all if you are reachable. ---
**Author:** ![dscotese](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/dscotese/32/6049_2.png) [@dscotese](https://discuss.ipfs.tech/u/dscotese)\ **Post date:** [February 21, 2022, 10:30pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/8 "2022-02-21T22:30:11Z")
> [@ylempereur](#): > > you are behind a NAT router and you did not set up port forwarding: I assume you mean the publishing node. I sent them the info. We will see how it goes! ---
**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\ **Post date:** [February 21, 2022, 10:31pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/9 "2022-02-21T22:31:04Z")
Correct, the node where the content initially resides. If you know the node ID (peer ID) for it, I can check if it’s reachable. ---
**Author:** ![dscotese](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/dscotese/32/6049_2.png) [@dscotese](https://discuss.ipfs.tech/u/dscotese)\ **Post date:** [February 22, 2022, 1:08am UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/10 "2022-02-22T01:08:52Z")
You were correct about the NAT router. The owner has done all the instructions except the machine reboot at the end, and I was able to download the file, so I guess in his case, the reboot is unnecessary. He may still do it, just in case. Thanks for your help! Do you think there is any chance that IPFS might be enhanced to do an inbound peers count upon publishing to encode your wisdom and notify the operator “Only 0.03% of your peers are inbound. Have you [set up port forwarding](https://docs.ipfs.io/how-to/nat-configuration/)?” ---
**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\ **Post date:** [February 22, 2022, 1:15am UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/11 "2022-02-22T01:15:32Z")
Actually, the daemon already tests what addresses it is reachable through, and only publishes those that work. When doing that, it already knows if it’s accessible from the outside or not, it would just need to let you know. However, if your goal is just to consume content, it doesn’t matter that you are unreachable, but if you want to publish content, it is paramount that you are actually reachable. ---
**Author:** ![miguel99](https://avatars.discourse-cdn.com/v4/letter/m/58f4c7/32.png) [@miguel99](https://discuss.ipfs.tech/u/miguel99)\ **Post date:** [February 22, 2022, 4:42pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/12 "2022-02-22T16:42:15Z")
After the node PC reboot this morning to fully activate the port forwarding, I have far fewer peers with only two non-local inbound. Also, more difficulty accessing via public gateways the newly published content on the node. I think UPnP alone resulted in more connections. If the peer count doesn’t improve will disable the forwarding after the IPFS publish now in process and see if the better results return. Before rebooting it had as many as 8 inbound out of as many as 1300 peers. ---
**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\ **Post date:** [February 22, 2022, 5:33pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/13 "2022-02-22T17:33:50Z")
Something isn’t right either way, you should have hundreds. What is the peer ID, so that I can assess if it’s actually reachable. ---
**Author:** ![miguel99](https://avatars.discourse-cdn.com/v4/letter/m/58f4c7/32.png) [@miguel99](https://discuss.ipfs.tech/u/miguel99)\ **Post date:** [February 22, 2022, 5:43pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/14 "2022-02-22T17:43:22Z")
12D3KooWHWen2dsu4QWJE7srfSFduVPKTnGQ8jbx5MtG7iQc7YWD ---
**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\ **Post date:** [February 22, 2022, 6:00pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/15 "2022-02-22T18:00:50Z")
OK, your node is absolutely not reachable at the moment. I first tried to use “id”: ```auto > ipfs id 12D3KooWHWen2dsu4QWJE7srfSFduVPKTnGQ8jbx5MtG7iQc7YWD Error: failed to dial 12D3KooWHWen2dsu4QWJE7srfSFduVPKTnGQ8jbx5MtG7iQc7YWD: * [/ip4/104.156.24.117/udp/32908/quic] timeout: no recent network activity * [/ip4/104.156.24.117/tcp/32908] dial tcp4 0.0.0.0:4001->104.156.24.117:32908: i/o timeout ``` Then I tried to connect manually: ```auto > ipfs swarm connect /ip4/104.156.24.117/tcp/32908/p2p/12D3KooWHWen2dsu4QWJE7srfSFduVPKTnGQ8jbx5MtG7iQc7YWD Error: connect 12D3KooWHWen2dsu4QWJE7srfSFduVPKTnGQ8jbx5MtG7iQc7YWD failure: failed to dial 12D3KooWHWen2dsu4QWJE7srfSFduVPKTnGQ8jbx5MtG7iQc7YWD: * [/ip4/104.156.24.117/udp/32908/quic] timeout: no recent network activity * [/ip4/104.156.24.117/tcp/32908] dial tcp4 0.0.0.0:4001->104.156.24.117:32908: i/o timeout > ipfs swarm connect /ip4/104.156.24.117/udp/32908/quic/p2p/12D3KooWHWen2dsu4QWJE7srfSFduVPKTnGQ8jbx5MtG7iQc7YWD Error: connect 12D3KooWHWen2dsu4QWJE7srfSFduVPKTnGQ8jbx5MtG7iQc7YWD failure: failed to dial 12D3KooWHWen2dsu4QWJE7srfSFduVPKTnGQ8jbx5MtG7iQc7YWD: * [/ip4/104.156.24.117/tcp/32908] dial tcp4 0.0.0.0:4001->104.156.24.117:32908: i/o timeout ``` Then I tried the fleek tester: ![Screen Shot 2022-02-22 at 9.50.28 AM](https://us1.discourse-cdn.com/flex020/uploads/ipfs1/original/2X/9/97715293974724101967125f2e5ca173c38d34a3.png) Nothing can reach you. So, your port forwarding isn’t set up properly, or your node isn’t announcing the right port. You have some digging to do 🙂 ---
**Author:** ![miguel99](https://avatars.discourse-cdn.com/v4/letter/m/58f4c7/32.png) [@miguel99](https://discuss.ipfs.tech/u/miguel99)\ **Post date:** [February 22, 2022, 6:15pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/16 "2022-02-22T18:15:35Z")
OK, will look it over later. Thanks ---
**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\ **Post date:** [February 22, 2022, 6:26pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/17 "2022-02-22T18:26:53Z")
I tried a few more things, for the heck of it: ```auto > ping 104.156.24.117 PING 104.156.24.117 (104.156.24.117): 56 data bytes 64 bytes from 104.156.24.117: icmp_seq=0 ttl=50 time=60.107 ms 64 bytes from 104.156.24.117: icmp_seq=1 ttl=50 time=61.751 ms 64 bytes from 104.156.24.117: icmp_seq=2 ttl=50 time=60.979 ms 64 bytes from 104.156.24.117: icmp_seq=3 ttl=50 time=64.602 ms 64 bytes from 104.156.24.117: icmp_seq=4 ttl=50 time=60.487 ms ^C --- 104.156.24.117 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 60.107/61.585/64.602/1.605 ms > nc 104.156.24.117 32908 > nc 104.156.24.117 4001 > ``` An interesting clue is that port 32908 has a “block” rule on it, but port 4001 has a “reject” rule on it. So, your firewall handles them differently, or they go to different places. That’s as much as I can tell from here, the rest is up to you. ---
**Author:** ![miguel99](https://avatars.discourse-cdn.com/v4/letter/m/58f4c7/32.png) [@miguel99](https://discuss.ipfs.tech/u/miguel99)\ **Post date:** [February 22, 2022, 10:03pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/18 "2022-02-22T22:03:31Z")
okay, my ufw now allows 4001 and a lot of inbound is now connected. Also, now have about 1300 peers. Much better appearing. Please let me know what your test now shows. Thanks ---
**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\ **Post date:** [February 22, 2022, 10:07pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/19 "2022-02-22T22:07:18Z")
Success!!! Your node is now reachable from the internet. However, it now needs to do a good “reprovide”, as some of your content isn’t advertised properly: ![Screen Shot 2022-02-22 at 2.04.33 PM](https://us1.discourse-cdn.com/flex020/uploads/ipfs1/original/2X/c/c1fa224ea285ad7624e2361eb61cf02f135217e9.png) This will happen automatically within the next 12 hours (unless you have changed the defaults). You can also trigger it manually with the following command: `ipfs bitswap reprovide` ---
**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\ **Post date:** [February 22, 2022, 10:10pm UTC](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540/20 "2022-02-22T22:10:24Z")
Hmmm, your node just disappeared! Did you change something again? [Next page](https://discuss.ipfs.tech/t/github-issues-here-search-gateway-ipfs-io-dweb-link/13540.md?page=2)