You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My k3s agent failed to join the server with "ERRO[0020] CA cert validation failed: Get "https://127.0.0.1:6444/cacerts": context deadline exceeded (Client. Timeout exceeded while awaiting headers)".
The server IP in my cluster is 192.168.137.2, and the k3s server has successfully run on it.
Then I execute "k3s agent -s https://192.168.137.2:6443 -t <token from server> --with-node-id 1", get the error.
I don't understand why the load-balancer was trying to curl 127.0.0.1:6444 ? Below is the screen print.
Before I give this issue, I searched for this error on Google and tried the following:
Double-check the server IP and I can confirm the server IP and port number are right
make sure the content of /etc/rancher/node/password is the same for both server and agent
The logs show that the server is advertising its address as 192.168.1.121, which is not reachable by the agent. Did you need to set --node-ip on the server to have it select the correct address?
My k3s agent failed to join the server with "ERRO[0020] CA cert validation failed: Get "https://127.0.0.1:6444/cacerts": context deadline exceeded (Client. Timeout exceeded while awaiting headers)".
The server IP in my cluster is 192.168.137.2, and the k3s server has successfully run on it.
Then I execute "k3s agent -s https://192.168.137.2:6443 -t <token from server> --with-node-id 1", get the error.
I don't understand why the load-balancer was trying to curl 127.0.0.1:6444 ? Below is the screen print.
![1713526368274](https://private-user-images.githubusercontent.com/72024759/323941685-1b5fae65-e680-4727-973d-45dc0f9111a3.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjI1MzEzMDMsIm5iZiI6MTcyMjUzMTAwMywicGF0aCI6Ii83MjAyNDc1OS8zMjM5NDE2ODUtMWI1ZmFlNjUtZTY4MC00NzI3LTk3M2QtNDVkYzBmOTExMWEzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MDElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODAxVDE2NTAwM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPThlZTIzY2NiYTBlNDExOGMyNjA2MWNlNDExYjkzYzMxNGI5YjE0NTM1ZjZjZGQ3ZDI5NmJhOGFmZDQ3NWQ4MzkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.tz0FAj4wekX9L9QAhROXrPkJ9WSJTG0KIpzmAj-0PVE)
Before I give this issue, I searched for this error on Google and tried the following:
However, all of these cannot solve my problem. I'm really confused.
My server's OS is Ubuntu 22.04 with Linux 5.10.110, and the agent's OS is OpenEuler 22.03 with Linux 5.10. Both of them are Arm platforms.
The text was updated successfully, but these errors were encountered: