-
-
Notifications
You must be signed in to change notification settings - Fork 1k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?" #9
Comments
Did you get latest? Also are you sure you are using the right interface name in your variables? Can you show them here? |
THX for your tutorials and help. Yes, i got the latest, Interface is eth0 k3s_version: v1.23.4+k3s1 interface which will be used for flannelflannel_iface: "eth0" apiserver_endpoint is virtual ip-address which will be configured on each masterapiserver_endpoint: "192.168.0.190" k3s_token is required masters can talk together securelythis token should be alpha numeric onlyk3s_token: "++++++++++" extra_server_args: "--no-deploy servicelb --no-deploy traefik --write-kubeconfig-mode 644 default-not-ready-toleration-seconds=30 --kube-apiserver-arg default-unreachable-toleration-seconds=30 --kube-controller-arg node-monitor-period=20s --kube-controller-arg node-monitor-grace-period=20s --kubelet-arg node-status-update-frequency=5s" change these to your liking, the only required one is--no-deploy servicelb#extra_server_args: "--no-deploy servicelb --no-deploy traefik" image tag for kube-vipkube_vip_tag_version: "v0.4.2" image tag for metal lbmetal_lb_speaker_tag_version: "v0.12.1" metallb ip range for load balancermetal_lb_ip_range: "192.168.0.180-192.168.0.189" |
I don't see anything odd. I would try removing all server args except required, reset, and try it again |
Expand your hard disks... On all nodes... Probably should make a note Tim. You do say this in the video! |
Before doing this I actually switched my Ubuntu template to the prior video that Tim did and made sure that the both username/password and SSH keys are consistent across all VMs. |
Do all machines have the same time zones, same ssh keys, and are able to communicate with each other? Are you using passwordless sudo? If if not you might have to pass in additional flags like |
I am encountering the same issue on a setup provisioned with vagrant. Here is the stacktrace in verbose mode
|
How big should the hard disk be? ATM it is 86% free?`
Yes, yes, yes, yes. I have tried it with only the first do neccessary args and run into the same issue again. |
can you please paste your |
Ok, so I was able to solve my issue. I have also done a reset and verified that the old token was causing the issue. After some digging in logs I found this error line. So I was a bit unlucky with the token I had set:
|
Finally, note that in this current state, I can reach the active node directly at |
Regarding my issue running on Raspberry Pi OS Lite 64 bit. |
@yankeeinlondon please try without all of the args and be sure you have enough disk space on these nodes |
Also, this is turning more into a discussion rather than to report bugs :) |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hello!
First of all thank you for this guide!
Learn so many new things, but now i am stucked and do not know how to proceed.
I try to get it up and running on rasperry pi's, 3 Masters, and 4 Workers.
Error message after lunching the playbook:
What can I do? Where do I have to search? what could the error be?
Thanks for any help that you can give me.
The text was updated successfully, but these errors were encountered: