Closed wujood closed 4 years ago
Figured it out! The problem was, that rancher was run with a wrong certificate. If someone one day has this error: Look into your *.pem files and make sure that:
Figured it out! The problem was, that rancher was run with a wrong certificate. If someone one day has this error: Look into your *.pem files and make sure that:
- ... there is no empty line at the end of the file
- ... you read the instructions for certificate volumes word by word! https://rancher.com/docs/rancher/v2.x/en/installation/single-node/#2-choose-an-ssl-option-and-install-rancher
I am facing this same issue:
Question: Where are the *.pem files that you're referencing?
Ran into the problem, it was indeed caused by a newline at the end of my private CA cert.
While installing rancher on hetzner i tried to use this driver to provision the servers for a new cluster. My rancher installation is brand new and the version is the newest out there.
I created a node template for the cx21 type and created a simple cluster with one etcd/controlplane/worker, but i got the same error with bigger clusters. After creating the cluster rancher starts normally to provision the servers and in hetzner cloud i can see the new nodes beeing created, but then it gets stuck and shows
on the rancher ui. I looked into the logs of the rancher container (single node installation) and found these lines:
( I am new to writing issues and also new to hetzner cloud. if i explained the issue not enough, please tell me and i will try my best to provide more information)