# Node on a Private network

**URL:** <https://forums.suse.com/t/node-on-a-private-network/13334>\
**Category:** General\
**Created:** [February 14, 2019, 4:09pm UTC](https://forums.suse.com/t/node-on-a-private-network/13334 "2019-02-14T16:09:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![edpichler](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/edpichler/32/4848_2.png) [@edpichler](https://forums.suse.com/u/edpichler)\
**Post date:** [February 14, 2019, 4:09pm UTC](https://forums.suse.com/t/node-on-a-private-network/13334/1 "2019-02-14T16:09:49Z")

</div>

Hello Ranchers, is it possible to run a Node on a private network, that has access to the Internet, while the rancher server is on a public network (accessible by browser)?

---

<div class="post-metadata">

**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\
**Post date:** [February 14, 2019, 6:09pm UTC](https://forums.suse.com/t/node-on-a-private-network/13334/2 "2019-02-14T18:09:34Z")

</div>

Yes, the agent on the nodes opens the connection to the server\* and the server does not have to be able to reach the nodes directly. All the nodes in a cluster do need to be able to reach each other and should be on the same network though.

\*: (except for the pubic hosted kubernetes providers, GKE/EKS/AKS, where we open the connection to the provider)

---

<div class="post-metadata">

**Author:** ![edpichler](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/edpichler/32/4848_2.png) [@edpichler](https://forums.suse.com/u/edpichler)\
**Post date:** [February 20, 2019, 2:03pm UTC](https://forums.suse.com/t/node-on-a-private-network/13334/3 "2019-02-20T14:03:03Z")

</div>

I don’t know why I can’t get my node up. My rancher shows this message.  
My rancher is in an internet server, while my node is in a private network.

Failed to communicate with API server: Get [https://172.13.13.201:6443/api/v1/componentstatuses?timeout=30s:](https://172.13.13.201:6443/api/v1/componentstatuses?timeout=30s:) dial tcp 127.0.0.1:6443: connect: connection refused
