# Remote gateway can't resolve ipns address

**URL:** <https://discuss.ipfs.tech/t/remote-gateway-cant-resolve-ipns-address/6445>\
**Category:** Help\
**Tags:** ipns\
**Created:** [October 11, 2019, 12:14am UTC](https://discuss.ipfs.tech/t/remote-gateway-cant-resolve-ipns-address/6445 "2019-10-11T00:14:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rusfearuth](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@rusfearuth](https://discuss.ipfs.tech/u/rusfearuth)\
**Post date:** [October 11, 2019, 12:14am UTC](https://discuss.ipfs.tech/t/remote-gateway-cant-resolve-ipns-address/6445/1 "2019-10-11T00:14:56Z")

</div>

Hey there,

I have the next problem. I have resource with CID **QmResource**. I don’t want to share a new one CID each time when I update it. In this case, I tried to use IPNS and it worked locally fine except of remote gateways. When I try to get content by link `ipfs.io/ipns/QmIpnsHash`, I get the next message in browser:

```auto
ipfs resolve -r /ipns/QmResource/: context deadline exceeded

```

How I got `QmResource`:

1. Got CID of folder
2. Run the next command `jsipfs name publish QmResource`
3. Checked QmIpnsHash locally `jsipfs name resolve QmIpnsHash`
4. Requested locally `localhost:9090/ipns/QmIpnsHash`

Does anybody know what can be wrong?

---

<div class="post-metadata">

**Author:** ![rusfearuth](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@rusfearuth](https://discuss.ipfs.tech/u/rusfearuth)\
**Post date:** [October 16, 2019, 8:45am UTC](https://discuss.ipfs.tech/t/remote-gateway-cant-resolve-ipns-address/6445/2 "2019-10-16T08:45:58Z")

</div>

Can Anybody help me?

---

<div class="post-metadata">

**Author:** ![ipfs\_lover](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ipfs_lover/32/3697_2.png) [@ipfs\_lover](https://discuss.ipfs.tech/u/ipfs_lover)\
**Post date:** [April 18, 2020, 8:21pm UTC](https://discuss.ipfs.tech/t/remote-gateway-cant-resolve-ipns-address/6445/3 "2020-04-18T20:21:28Z")

</div>

Did you solve the problem?
