# Reaching my node from anywhere

**URL:** <https://forum.grin.mw/t/reaching-my-node-from-anywhere/9990>\
**Category:** Tech Support\
**Created:** [August 25, 2022, 12:33pm UTC](https://forum.grin.mw/t/reaching-my-node-from-anywhere/9990 "2022-08-25T12:33:42Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cadmus](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/cadmus/32/5391_2.png) [@Cadmus](https://forum.grin.mw/u/Cadmus)\
**Post date:** [August 25, 2022, 12:33pm UTC](https://forum.grin.mw/t/reaching-my-node-from-anywhere/9990/1 "2022-08-25T12:33:42Z")

</div>

hi guys, hope everybody is doing great so far! Just set up a grin node on a VPS server with a background service. So far so good, grin server seems running from what I see in the grin-server log and port listening. But when I tried to use it as the specific node for my grin-wallet (executing the command grin-wallet -r “[http://myIPaddress:3413](http://myIPaddress:3413)” info) installed on my mac I get the following message: _ERROR grin\_wallet\_impls::node\_clients::http - Error calling get\_tip: ResponseError error: Cannot parse response_  
_WARN grin\_wallet\_libwallet::api\_impl::owner\_updater - Updater Thread unable to contact node_  
_WARNING: Wallet failed to verify data against a live chain. The above is from local cache and only valid up to the given height! (is your grin server offline or broken?)_. When using grin-wallet -r “[https://grinnode.live:3413](https://grinnode.live:3413)” info, this is working well. Would you have some advice for the noob I am in Grin to troubleshoot this issue? Thanks to all. FYI my server is reachable through a telnet with IP address and port 3413.

---

<div class="post-metadata">

**Author:** ![Cadmus](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/cadmus/32/5391_2.png) [@Cadmus](https://forum.grin.mw/u/Cadmus)\
**Post date:** [August 25, 2022, 1:25pm UTC](https://forum.grin.mw/t/reaching-my-node-from-anywhere/9990/2 "2022-08-25T13:25:12Z")

</div>

Got my answer on Keybase general chat, thanks to vegycslol!

---

<div class="post-metadata">

**Author:** ![mcm-mike](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/mcm-mike/32/3492_2.png) [@mcm-mike](https://forum.grin.mw/u/mcm-mike)\
**Post date:** [August 25, 2022, 5:41pm UTC](https://forum.grin.mw/t/reaching-my-node-from-anywhere/9990/3 "2022-08-25T17:41:32Z")

</div>

> Got my answer on Keybase general chat, thanks to vegycslol!

Do you mind sharing the answer, perhaps @stakerV can add it to the FAQ section to [https://grinnode.live/](https://grinnode.live/) to explain it in a more simple matter ?

---

<div class="post-metadata">

**Author:** ![stakerV](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/stakerv/32/4080_2.png) [@stakerV](https://forum.grin.mw/u/stakerV)\
**Post date:** [August 25, 2022, 6:47pm UTC](https://forum.grin.mw/t/reaching-my-node-from-anywhere/9990/4 "2022-08-25T18:47:52Z")

</div>

@mcm-mike I created an issue for this. Based on vegycslol’s answer, one needs to either use foreign\_api\_secret or comment it out in grin-server.toml.

---

<div class="post-metadata">

**Author:** ![Cadmus](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/cadmus/32/5391_2.png) [@Cadmus](https://forum.grin.mw/u/Cadmus)\
**Post date:** [August 25, 2022, 8:10pm UTC](https://forum.grin.mw/t/reaching-my-node-from-anywhere/9990/5 "2022-08-25T20:10:59Z")

</div>

As soon as I find time I will expose in details what was my issue, and what was the fix :). Likely tomorrow.  
Thanks to all for your great responsiveness,

---

<div class="post-metadata">

**Author:** ![Cadmus](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/cadmus/32/5391_2.png) [@Cadmus](https://forum.grin.mw/u/Cadmus)\
**Post date:** [August 26, 2022, 9:16am UTC](https://forum.grin.mw/t/reaching-my-node-from-anywhere/9990/6 "2022-08-26T09:16:02Z")

</div>

hi there, here is the summary of the issue I faced:

- I installed a grin node via grin-server package on a VPS server
- I installed a grin wallet on my Mac via grin-wallet package
- I followed [GRIN Full node and Wallet Installation Linux | by Private Payments | Medium](https://privatepayments1.medium.com/grin-full-node-and-wallet-installation-linux-9025684802fa) to make the grin server run permanently and launched at reboot
- I tested my grin-wallet on my Mac with command: _grin-wallet -r “[http://myIPaddress:3413](http://myIPaddress:3413)” info_, it failed with the error: _ERROR grin\_wallet\_impls::node\_clients::http - Error calling get\_tip: ResponseError error: Cannot parse response_  
_WARN grin\_wallet\_libwallet::api\_impl::owner\_updater - Updater Thread unable to contact node_  
_WARNING: Wallet failed to verify data against a live chain. The above is from local cache and only valid up to the given height! (is your grin server offline or broken?)_
- I then tested my grin-wallet with command: _grin-wallet -r “[https://grinnode.live:3413](https://grinnode.live:3413)” info_ to see if the issue was on my wallet or server, and it worked fine. I concluded something was wrong in my server setup.
- I asked for advice on Keybase and after few exchanges Vegycslol gave me the answer (thanks to him!) I needed to comment the line _foreign\_api\_secret\_path = “/home/grinuser/.grin/main/.foreign\_api\_secret”_ in the grin-server.toml (basically inserting a # before the line) to bypass the basic auth

Hope it helps to describe what happened. Do not hesitate to comment if this setup is not ideal or if better ways exist. Thanks!  
Cheers,
