# Cluster api access is stuck on a missing node

**URL:** <https://forums.suse.com/t/cluster-api-access-is-stuck-on-a-missing-node/20904>\
**Category:** SUSE Rancher Prime\
**Created:** [August 12, 2021, 2:17am UTC](https://forums.suse.com/t/cluster-api-access-is-stuck-on-a-missing-node/20904 "2021-08-12T02:17:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![naorw](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/naorw/32/4953_2.png) [@naorw](https://forums.suse.com/u/naorw)\
**Post date:** [August 12, 2021, 2:17am UTC](https://forums.suse.com/t/cluster-api-access-is-stuck-on-a-missing-node/20904/1 "2021-08-12T02:17:49Z")

</div>

Hi guys. i lost one of the control plane nodes, unfortunately the leading one. so now i do not have access to what used to be apiEndpoint, say 222.222.232.232 but still have another control node. however when i try to access anything via kube api I’m getting “error trying to reach service:” 222.222.232.232 :52792: i/o timeout") has prevented the request from succeeding or similar because something is pointing to the old node. in gui note stuck in removing " Waiting on node-controller" and "This cluster is currently Error; areas that interact directly with it will not be available until the API is ready. im not sure how to proceed. is there a way to manually force usage of the other server to restore rancher connection to the cluster? thank you in advance.

---

<div class="post-metadata">

**Author:** ![KuosmTe81](https://avatars.discourse-cdn.com/v4/letter/k/5e9695/32.png) [@KuosmTe81](https://forums.suse.com/u/KuosmTe81)\
**Post date:** [August 17, 2021, 4:51am UTC](https://forums.suse.com/t/cluster-api-access-is-stuck-on-a-missing-node/20904/2 "2021-08-17T04:51:49Z")

</div>

Any possibility that your kube config file in .kube/config is pointing to missing node?

---

<div class="post-metadata">

**Author:** ![naorw](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/naorw/32/4953_2.png) [@naorw](https://forums.suse.com/u/naorw)\
**Post date:** [August 17, 2021, 7:40am UTC](https://forums.suse.com/t/cluster-api-access-is-stuck-on-a-missing-node/20904/3 "2021-08-17T07:40:03Z")

</div>

No, the problem is not in my local config but in rancher gui / api only. there is no problem accessing cluster directly.

---

<div class="post-metadata">

**Author:** ![JohnO](https://avatars.discourse-cdn.com/v4/letter/j/da6949/32.png) [@JohnO](https://forums.suse.com/u/JohnO)\
**Post date:** [April 15, 2022, 1:23pm UTC](https://forums.suse.com/t/cluster-api-access-is-stuck-on-a-missing-node/20904/4 "2022-04-15T13:23:37Z")

</div>

Did you ever solve your problem? I’m having the same issue.

---

<div class="post-metadata">

**Author:** ![wcoateRR](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/wcoaterr/32/8144_2.png) [@wcoateRR](https://forums.suse.com/u/wcoateRR)\
**Post date:** [April 15, 2022, 1:32pm UTC](https://forums.suse.com/t/cluster-api-access-is-stuck-on-a-missing-node/20904/5 "2022-04-15T13:32:25Z")

</div>

I’m having a different issue with downstream connectivity to Rancher (the downstream is badly horked and not connecting at all and just shows up as unavailable in Rancher UI).

When I tried to look on the Rancher side to see where it connected, I only got a Kubernetes local IP (10.43.0.1) which was also in local. When I asked about how that worked, a Rancher guy on Slack (Brad Davidson) told me that the way that Rancher knows what systems the downstream clusters are on is via the cattle-cluster-agent on the downstream clusters talking to Rancher (in my instance part of me being horked is DNS not working for the FQDN for Rancher that the cattle-cluster-agent is using so my downstream is marked as Unavailable).

Not quite what you’re asking, but hopefully helpful info to debug a bit further?