# Why can public IPFS gateways not show my files?

**URL:** <https://discuss.ipfs.tech/t/why-can-public-ipfs-gateways-not-show-my-files/17607>\
**Category:** Help\
**Created:** [February 23, 2024, 4:35pm UTC](https://discuss.ipfs.tech/t/why-can-public-ipfs-gateways-not-show-my-files/17607 "2024-02-23T16:35:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![interplanet](https://avatars.discourse-cdn.com/v4/letter/i/ecccb3/32.png) [@interplanet](https://discuss.ipfs.tech/u/interplanet)\
**Post date:** [February 23, 2024, 4:35pm UTC](https://discuss.ipfs.tech/t/why-can-public-ipfs-gateways-not-show-my-files/17607/1 "2024-02-23T16:35:26Z")

</div>

Hi, I’ve uploaded a directory of json files to IPFS. I can use ipfs get to retrieve them via their hash. I can use [http://localhost:8080/ipfs/](http://localhost:8080/ipfs/) to resolve them by their hash as well. I can not see the images on [https://ipfs.io/ipfs/](https://ipfs.io/ipfs/) or any other public gateways as it always says 504. I can however see all of the file names on IPLD explorer website though for the directory I added. How do I know if my IPFS is connected right?

---

<div class="post-metadata">

**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 23, 2024, 10:55pm UTC](https://discuss.ipfs.tech/t/why-can-public-ipfs-gateways-not-show-my-files/17607/2 "2024-02-23T22:55:16Z")

</div>

Using [ipfs.io](http://ipfs.io) isn’t a very good test, it tends to fail even on good CIDs. We need to check a few things:

We need your node’s PeerID, so that:

- we can see if its address is in the DHT
- we can test if we can connect to your node

We need a couple example CIDs that are on your node, so that:

- we can see if your node reports having them
- we can see if they are in the DHT, pointing to your node
- we can see if we can download them from your node

Any of these things could fail, and would point to a different problem. If nothing fails, you are fine and it’s just [ipfs.io](http://ipfs.io) not doing a very good job at finding you.
