# RKE2 HA not working

**URL:** <https://forums.suse.com/t/rke2-ha-not-working/40122>\
**Category:** General\
**Created:** [February 27, 2023, 2:00pm UTC](https://forums.suse.com/t/rke2-ha-not-working/40122 "2023-02-27T14:00:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![PaulR](https://avatars.discourse-cdn.com/v4/letter/p/c4cdca/32.png) [@PaulR](https://forums.suse.com/u/PaulR)\
**Post date:** [February 27, 2023, 2:00pm UTC](https://forums.suse.com/t/rke2-ha-not-working/40122/1 "2023-02-27T14:00:53Z")

</div>

Hello all -

I installed RKE2 v1.26.1, three master nodes and two workers. Install and “normal” operation are working as expected. However, wherever I reboot any one of the three master nodes, kubectl command do not function until all the masters are up. I see the following in my /var/log/messages:

```auto
Feb 21 14:11:36 kubehost-02 rke2[1434]: time="2023-02-21T14:11:36-05:00" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp 192.168.222.178:9345: connect: connection refused"
Feb 21 14:11:36 kubehost-02 rke2[1434]: time="2023-02-21T14:11:36-05:00" level=error msg="Remotedialer proxy error" error="dial tcp 192.168.222.178:9345: connect: connection refused"
Feb 21 14:11:41 kubehost-02 rke2[1434]: time="2023-02-21T14:11:41-05:00" level=info msg="Connecting to proxy" url="wss://192.168.222.178:9345/v1-rke2/connect"
Feb 21 14:11:41 kubehost-02 rke2[1434]: time="2023-02-21T14:11:41-05:00" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp 192.168.222.178:9345: connect: connection refused"
Feb 21 14:11:41 kubehost-02 rke2[1434]: time="2023-02-21T14:11:41-05:00" level=error msg="Remotedialer proxy error" error="dial tcp 192.168.222.178:9345: connect: connection refused"
Feb 21 14:11:46 kubehost-02 rke2[1434]: time="2023-02-21T14:11:46-05:00" level=info msg="Connecting to proxy" url="wss://192.168.222.178:9345/v1-rke2/connect"

```

I’m completely confused as to what’s going on here. My .kube/config (on each master) is set to connect to [https://127.0.0.1:6443](https://127.0.0.1:6443). RKE2 seems to have inserted itself somethere between kubectl and my cluster…?

- What is this “proxy” mentioned in the above logs?
- Why does the proxy not work if any one of my three masters is down?
- How can I fix this so it works as expected (commands continue to work even if one master is down)?

Thanks!