Hello guys. Everything was working on a kubernetes cluster with a master and three nodes. After a restart in all machines I started receiving this error when trying to run any kubectl command. #> kubectl version Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c…

hi,maybe you can check this topic [Jeroen Jacobs] Why disable swap on kubernetes kubernetes, swap asked by Jeroen Jacobs on 01:22PM - 02 Nov 17 UTC

Hi, Thanks for the replay and suggested topic clears my doubt.

Hi, I I’m facing the same problem and I’m pretty sure @changec ’s way does not work (there is no swap partition It there another solution?

Hi, I have the same problem and listed above solution did not help me. My system runs on VMware Workstation 15 Player: denis@ubuntu:~/dev$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic When I try to execute kubec…

Hello, after increasing disc space the problem was solved. Unfortunately, in the logs I did not see the records related to the problem of disk space. Five days were spent on finding out the cause, since it is not obvious.

azzaka , thank you for answer, but “cube get nodes” was useless for my case, cause cluster did not start properly (all main modules as apiserver, etcd etc was not run). So I was getting “connection refused,” as mentioned in the first post.

I have the hit the same issue on CentOS 7 even after disabling the swap. But i managed to run kubectl get nodes by explicitly passing --kubeconfig parameter. This is not as per the kubernetes docs I have set KUBECONFIG file but kubectl does care about that parameter.

I had the exact same error today…and after some investigating(and trying the swapoff thing), I found that my /tmp directory was filling up and was at 100%. I grew that directory and it solved it…may look into cleaning up /tmp more frequently if it continues to be a problem.

Hi, I had exactly the same issue, and I was able to resolve the issue using command below: export KUBECONFIG=/etc/kubernetes/kubelet.conf Sometimes it affects master node as well, but in that case - another issue appears, somethings like: unable to connect to the server: x509: certificate signed…

The connection to the server <host>:6443 was refused - did you specify the right host or port?

General Discussions

azzaka February 7, 2019, 1:54pm 16

kubectl get nodes

may have shown the node has diskpressure. Something i didn’t see in your post.

Topic		Replies	Views
The connection to the server 192.168.1.2:6443 was refused - did you specify the right host or port? General Discussions	9	46634	May 2, 2025
The connection to the server localhost:8080 was refused - did you specify the right host or port? General Discussions	76	839880	August 6, 2025
The connection to the server 10.4.4.20:6443 was refused - did you specify the right host or port? i run command sudo swapoff -a i also put .kube/config file in home directory of user still facing issue General Discussions development	0	172	January 9, 2024
The connection to the server Master_IP:6443 was refused - did you specify the right host or port? General Discussions development , security , network , kubernetes-custom-resources	0	1631	June 3, 2024
After server reboot - Error getting node err=node ... not found General Discussions	3	11051	December 13, 2023

The connection to the server <host>:6443 was refused - did you specify the right host or port?

Related topics