This message was deleted.
# harvester
a
This message was deleted.
r
Hi @high-lunch-88646, What did you put in the
Management address
field when installing those two joining nodes? Is it the VIP address or something else?
h
Hello i put the VIP i use to access the Harvester interface
I double checked in the rancherd config file and the management address matches the VIP declared on the first node
r
What’s the output of the following command?
Copy code
curl -ik https://<VIP>/cacerts
Does it show the PEM-format certificate?
h
The following command does output the pem certificates (i ran it on my joining nodes)
Some additional informations, i am not using any kind of custom certifiacte and my nodes can curl the VIp without issue
r
This is weird. Does rancherd continue retrying? Could you generate a support bundle (it’s fine that the cluster only has one node)? I’d like to see what happened.
h
rancherd does continue retrying, please find the support bundle attached. Thanks for your help 🙂
r
Is it an air-gapped environment?
I saw some logs indicating the in-cluster dns server is misbehaving. There are a bunch of error logs in the coredns pod
h
it is not an air-gapped environnement but my firewall might not be setup properly for DNS requests, i will check and come back to you. Thanks 🙂