# Upgraded master node to 1.24.2 but now cannot connect

**URL:** <https://discuss.kubernetes.io/t/upgraded-master-node-to-1-24-2-but-now-cannot-connect/20472>\
**Category:** General Discussions\
**Created:** [June 30, 2022, 1:30am UTC](https://discuss.kubernetes.io/t/upgraded-master-node-to-1-24-2-but-now-cannot-connect/20472 "2022-06-30T01:30:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tdubb123](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/tdubb123/32/10357_2.png) [@tdubb123](https://discuss.kubernetes.io/u/tdubb123)\
**Post date:** [June 30, 2022, 1:30am UTC](https://discuss.kubernetes.io/t/upgraded-master-node-to-1-24-2-but-now-cannot-connect/20472/1 "2022-06-30T01:30:32Z")

</div>

Asking for help? Comment out what you need so we can get more information to help you!

### Cluster information:

Kubernetes version: 1.24.2  
Cloud being used: (put bare-metal if not on a public cloud) baremetal  
Installation method: kubeadm  
Host OS: ubuntu 20.04  
CNI and version: weave  
CRI and version: docker

I upgraded my kubernetes on my master control node to 1.24.2 but now kubectl will not connect.

kubectl cluster-info shows

To further debug and diagnose cluster problems, use ‘kubectl cluster-info dump’.  
The connection to the server localhost:8080 was refused - did you specify the right host or port?

root@kubemaster:~# kubectl version -o json  
{  
“clientVersion”: {  
“major”: “1”,  
“minor”: “24”,  
“gitVersion”: “v1.24.2”,  
“gitCommit”: “f66044f4361b9f1f96f0053dd46cb7dce5e990a8”,  
“gitTreeState”: “clean”,  
“buildDate”: “2022-06-15T14:22:29Z”,  
“goVersion”: “go1.18.3”,  
“compiler”: “gc”,  
“platform”: “linux/amd64”  
},  
“kustomizeVersion”: “v4.5.4”  
}  
The connection to the server localhost:8080 was refused - did you specify the right host or port?

also docker ps | grep kube-apiserver does not look like its running

---

<div class="post-metadata">

**Author:** ![said678](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/said678/32/10365_2.png) [@said678](https://discuss.kubernetes.io/u/said678)\
**Post date:** [July 1, 2022, 11:16am UTC](https://discuss.kubernetes.io/t/upgraded-master-node-to-1-24-2-but-now-cannot-connect/20472/2 "2022-07-01T11:16:44Z")

</div>

Hello,

I had the same issue and it was kubelet upgraded to 1.24.1 that was not starting. (stuck in activating status and keeps restarting)  
A workarround that worked for me is to to downgrade kubelet to 1.23.8.

Regards,

---

<div class="post-metadata">

**Author:** ![mrbobbytables](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/mrbobbytables/32/7_2.png) [@mrbobbytables](https://discuss.kubernetes.io/u/mrbobbytables)\
**Post date:** [July 2, 2022, 3:53am UTC](https://discuss.kubernetes.io/t/upgraded-master-node-to-1-24-2-but-now-cannot-connect/20472/3 "2022-07-02T03:53:09Z")

</div>

1.24 dropped support for dockershim, if you want to continue to use docker, you need to use [GitHub - Mirantis/cri-dockerd](https://github.com/Mirantis/cri-dockerd) or switch to another container runtime. More info here: [https://kubernetes.io/blog/2022/02/17/dockershim-faq/](https://k8s.io/dockershim)