Rancher Web UI Connection Refused

Hi All,
I m new to Rancher. Trying a POC.

Followed: Helm CLI Quick Start

Install successful on a Bastion host.
Upon Opening the rancher url in web browser or curl

Error:
xxx.xxx.60.139.sslip.io refused to connect

Step:
[opc@wlsoke-bastion ~]$ helm install rancher rancher-latest/rancher \

–namespace cattle-system
–set hostname=xxxx.sslip.io
–set replicas=1
–set bootstrapPassword=xxxxxxxxxxx

WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/opc/.kube/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/opc/.kube/config
NAME: rancher
LAST DEPLOYED: Tue Aug 15 14:26:29 2023
NAMESPACE: cattle-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Rancher Server has been installed.

NOTE: Rancher may take several minutes to fully initialize. Please standby while Certificates are being issued, Containers are started and the Ingress rule comes up.

Any idea what could be wrong ?

Firewall is disabled and Ingress rules are verified for 443 and 80 for machine’s subnet.

Thank you in advance
Gururaj

@gururaj0 Hi and welcome to the Forum :smile:

Did you check k3s is running and all the pods were created/running etc?

@malcolmlewis1 Thank you. I didn’t install any K3s as it never worked. Not sure if this is needed ? If so, pls explain why it is needed and clear instruction please.

curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=1.26+k3s1 sh -s - server --cluster-init
This didn’t do anything. I m on Red Hat Enterprise Linux Server release 7.9 (Maipo)

[opc@wlsoke-bastion ~]$ kubectl get ingress -n cattle-system
NAME CLASS HOSTS ADDRESS PORTS AGE
rancher xxx.xxx.xx.xxx.sslip.io 80, 443 11h

[opc@wlsoke-bastion ~]$ kubectl get svc -n cattle-system
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
rancher ClusterIP 10.96.159.215 80/TCP,443/TCP 12h
rancher-webhook ClusterIP 10.96.130.52 443/TCP 12h
webhook-service ClusterIP 10.96.18.150 443/TCP 12h

[opc@wlsoke-bastion ~]$ kubectl get pods -n cattle-system
NAME READY STATUS RESTARTS AGE
rancher-f774856cc-lxlwc 1/1 Running 0 73m
rancher-webhook-788c48b988-ff6f7 1/1 Running 0 12h

Regards
Gururaj

Just to clarify, I m installing Rancher on an existing kubernetes cluster.

@gururaj0 Ahh ok. So is the version of k3s running supported by Rancher.

https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-7-5/

1 Like

@malcolmlewis1 Yes k3s was the issue. The documentation wasn’t great as how to install it. Anyways now it is working. One question I was wondering how in the world without any dns entry the rancher url is working on the browser ?

Ref: Now if you navigate to <IP_OF_LINUX_NODE>.sslip.io in a web browser, you should see the Rancher UI.

Regards
Gururaj

@gururaj0 sslip.io will resolve to your ip, see https://sslip.io/

I use local dns and hosts files here.

1 Like

@malcolmlewis1 Malcom, that answers ! Thank you.