The connection to the server x.x.x.x:6443 was refused – did you specify the right host or port?

Whenever I start my VMs(ubuntu master and worker running on Virtualbox) and run kubectl get nodes, this is the error I see
The connection to the server x.x.x.x:6443 was refused – did you specify the right host or port?
I tried re joining after kubeadm reset but I lose all my lab progress by doing so. Kindly suggest a fix for this.
Comments
-
I'd recommend checking to make sure your IPs in your VMs aren't changing. I was using vmware workstation and using NAT, and you can actually set a static ip for your lab nodes. I'm not sure what the process is for virtualbox, but I'm sure there is an equivalent.
Something to check, anyway--might not be your issue.
0 -
Hi @skatakam,
Aside form assigning static IP addresses to your vbox hosts, I'd also recommend that you modify the default IP subnet of vbox to prevent overlapping with the Pod IP network 192.168.0.0/16 managed by calico. Such an overlap will cause cluster DNS issues.
Regards,
-Chris0 -
I too keep getting below.. I have tried all solutions provided by google, but nothing worked. I am using aws ec2
The connection to the server ...:6443 was refused - did you specify the right host or port?
0 -
Hi @hemant1405,
It sounds to be a networking related issue, such as a firewall blocking access to a port.
When provisioning the EC2 instances, did you happen to follow the set up video guide from the intro chapter? It provides step by step instructions on how to configure VM resources, and most importantly networking and firewalls.Regards,
-Chris0 -
Hello,
Could you let us know what command you were running when you got the error? Were you on the control plane, or trying to access from a different system?
I noticed someone mentioned kubeadm reset. This would cause the cluster to be destroyed. It does not destroy the .kube/config file. So after you built a new cluster you may have an issue with TLS keys causing a lack of access, even if the IP address is the same.
Regards,
0 -
Hi, this has happened to me. In VM you must turn off swap: "sudo swapoff -a"
0 -
Hello,
This is happening to me as well.
I am also running an AWS EC2 instance, and I did follow all the steps in the setup guide.
I get the message after running the following command.kubectl apply -f calico.yaml
I have already ran swapoff -a, and I already checked the .yaml files for errors and could not find any.
0 -
Please perform the below steps on the master node. It works like charm.
1.sudo -i
2.swapoff -a
3. remove theswap.img
from root directoryrm -rf /swap.img
, if using swap partition exists.
4.exit
5.strace -eopenat kubectl version
Then wait for a few minutes so that all the pods get in running states.
2 -
@alihasanahmedk said:
Please perform the below steps on the master node. It works like charm.
1.sudo -i
2.swapoff -a
3. remove theswap.img
from root directoryrm -rf /swap.img
, if using swap partition exists.
4.exit
5.strace -eopenat kubectl version
Then wait for a few minutes so that all the pods get in running states.
Thank you for your input.
Unfortunately that did not work.
I had seen something similar in my search for a solution.
Most of the answers I run across center around SWAP, but I currently don't even have SWAP spaces set up my EC2 instance.0 -
kubectl apply -f calico.yaml
- strace -eopenat kubectl version
When I run both of the above commands, I still get the connection refused message, and they both yield and exit code of 1
0 -
No problem @soramaru . I can view your issue on call If you want to. Because that's works for me pretty much fine.
1 -
That would be great. What is the best way, and time to get a hold of you ?
0 -
@soramaru mail me your free slots. I will let you know then.
[email protected]0 -
I am usually free from 1800-2200 on weekdays; however, I am currently located in Japan and operating on GMT +9 time zone. I can also be reached at [email protected]
0 -
@soramaru
I am located in Pakistan and Japan is 4 hours ahead of Pakistan. I will be available from 1900 to onwards PKT which will be 2300 JST time. Let me know you want to do this on weekends or on weekdays.0 -
@alihasanahmedk
I sent you a message to [email protected]0 -
@soramaru
sure.0 -
Hi @soramaru,
Have you created a custom VPC with one SG to allow ingress traffic from all sources, all protocols, and to all ports?
Also, if the cluster happened to be re-initialized, did you manage to copy again the
/etc/kubernetes/admin.conf
file to your$HOME/.kube
directory as instructed by step 16 of Exercise 3.1?Regards,
-Chris0 -
Your first suggestion may have been the cause to my problem.
I ended up terminating my EC2 instance and starting a new one, and everything worked fine.
I must have made a mistake when setting up my EC2 instance.
0
Categories
- All Categories
- 50 LFX Mentorship
- 103 LFX Mentorship: Linux Kernel
- 575 Linux Foundation IT Professional Programs
- 304 Cloud Engineer IT Professional Program
- 124 Advanced Cloud Engineer IT Professional Program
- 53 DevOps Engineer IT Professional Program
- 61 Cloud Native Developer IT Professional Program
- 5 Express Training Courses
- 5 Express Courses - Discussion Forum
- 2K Training Courses
- 19 LFC110 Class Forum
- 7 LFC131 Class Forum
- 27 LFD102 Class Forum
- 157 LFD103 Class Forum
- 20 LFD121 Class Forum
- 1 LFD137 Class Forum
- 61 LFD201 Class Forum
- 1 LFD210 Class Forum
- LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 611 LFD259 Class Forum
- 105 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFD273 Class Forum
- 2 LFS145 Class Forum
- 24 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 11 LFS203 Class Forum
- 75 LFS207 Class Forum
- 300 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 11 LFS244 Class Forum
- 36 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 140 LFS253 Class Forum
- LFS254 Class Forum
- 1.1K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 93 LFS260 Class Forum
- 132 LFS261 Class Forum
- 33 LFS262 Class Forum
- 80 LFS263 Class Forum
- 15 LFS264 Class Forum
- 11 LFS266 Class Forum
- 18 LFS267 Class Forum
- 17 LFS268 Class Forum
- 23 LFS269 Class Forum
- 203 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- LFS281 Class Forum
- 234 LFW211 Class Forum
- 172 LFW212 Class Forum
- 7 SKF100 Class Forum
- SKF200 Class Forum
- 902 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 209 Networking
- 101 Printers & Scanners
- 85 Storage
- 763 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 142 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 357 Ubuntu
- 479 Linux System Administration
- 41 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 78 Network Management
- 108 System Management
- 49 Web Management
- 68 Mobile Computing
- 23 Android
- 30 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 537 Off Topic
- 131 Introductions
- 217 Small Talk
- 21 Study Material
- 826 Programming and Development
- 278 Kernel Development
- 514 Software Development
- 928 Software
- 260 Applications
- 184 Command Line
- 3 Compiling/Installing
- 76 Games
- 316 Installation
- 62 All In Program
- 62 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)