# Rancher Agent force public/external IP

**URL:** <https://forums.suse.com/t/rancher-agent-force-public-external-ip/10360>\
**Category:** SUSE Rancher Prime\
**Created:** [May 10, 2018, 1:12am UTC](https://forums.suse.com/t/rancher-agent-force-public-external-ip/10360 "2018-05-10T01:12:44Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![dwitzig](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/dwitzig/32/4397_2.png) [@dwitzig](https://forums.suse.com/u/dwitzig)\
**Post date:** [May 10, 2018, 1:12am UTC](https://forums.suse.com/t/rancher-agent-force-public-external-ip/10360/1 "2018-05-10T01:12:44Z")

</div>

is there anyway to force rancher agent to register a node only using the public/external IP?  
one or more of my nodes are on a separate network and cant communicate using InternalIP

I have tried setting --address & --internal-address in every combination.  
Have also tried editing the node directly with `kubectl edit node <node_name>` and changing the address to ExternalIP however after saving it is changed back immediately.

---

<div class="post-metadata">

**Author:** ![Akito](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/akito/32/5805_2.png) [@Akito](https://forums.suse.com/u/Akito)\
**Post date:** [January 6, 2020, 2:29pm UTC](https://forums.suse.com/t/rancher-agent-force-public-external-ip/10360/2 "2020-01-06T14:29:05Z")

</div>

Exact same problem here. I am shocked, nobody provided even a hint to this problem since 1.5 years.  
I am stuck with this, but we need to have a forced IP address for our setup to work.

---

<div class="post-metadata">

**Author:** ![dwitzig](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/dwitzig/32/4397_2.png) [@dwitzig](https://forums.suse.com/u/dwitzig)\
**Post date:** [January 7, 2020, 12:25am UTC](https://forums.suse.com/t/rancher-agent-force-public-external-ip/10360/3 "2020-01-07T00:25:46Z")

</div>

I can’t remember if I ever got this working.

I ended up changing to K3S. K3S has a `--node-ip ` flag that works well

---

<div class="post-metadata">

**Author:** ![taina0407](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/taina0407/32/6217_2.png) [@taina0407](https://forums.suse.com/u/taina0407)\
**Post date:** [March 30, 2020, 9:52am UTC](https://forums.suse.com/t/rancher-agent-force-public-external-ip/10360/4 "2020-03-30T09:52:55Z")

</div>

I’m facing this problem too, 2 years old issue without any workaround or solution!

---

<div class="post-metadata">

**Author:** ![Harutyun\_Dermenjyan](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/harutyun_dermenjyan/32/5419_2.png) [@Harutyun\_Dermenjyan](https://forums.suse.com/u/Harutyun_Dermenjyan)\
**Post date:** [May 6, 2020, 7:33pm UTC](https://forums.suse.com/t/rancher-agent-force-public-external-ip/10360/5 "2020-05-06T19:33:13Z")

</div>

Hello,  
maybe these posts are old and not so actual as it was at the question time, but as I noticed it now and have a solution for this, wanted to share it here.  
So I’ve solved the issue by re-registering the node with these flags in the client token string sudo docker run -d --privileged --restart=unless-stopped --net=host -v …Long String and Token Here `--node-name $EXT_IP --address $EXT_IP --internal-address $EXT_IP` --worker

---

<div class="post-metadata">

**Author:** ![mguggi](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/mguggi/32/6661_2.png) [@mguggi](https://forums.suse.com/u/mguggi)\
**Post date:** [June 22, 2021, 6:59pm UTC](https://forums.suse.com/t/rancher-agent-force-public-external-ip/10360/6 "2021-06-22T18:59:53Z")

</div>

Hi,

What exactly you mean with re-registering. Just execute only the provided `docker run` command or delete the node (I mean in the the rancher ui) and re-register it?

Regards,  
Manuel