Closed ruohki closed 3 years ago
@ruohki running into same issue today. at my case my rancher server wasn´t part of the private network as described in readme.
Hmm have to try that ~ was running Rancher on WSL2 on my machine
this does indeed solve the issue
@tgruenert @ruohki Hi guys, what did you use as server-url when you installed Rancher in the same private network? I tried using Rancher's private IP but then the nodes couldn't connect to Rancher anyway because https://10.0.0.2 (Rancher's private IP) wasn't configured in the ingress resource when installing Rancher.
The public ip / public fqdn
@ruohki yeah that seems to work. Thanks
Hey there,
i try to deploy a very small cluster and getting stuck at: Waiting for SSH to be available...
machines and keys get created.
Running latest stuff that is available