With SSL enabled (recommended)

https://<IP-CON-GUIONES>.sslip.io/

‍

Example: if your VM has the IP address 200.25.101.125:

https://200-25-101-125.sslip.io/

‍

Without SSL

http://<VM_IP>/

‍

Access credentials

When opening the URL for the first time, Rancher requests the Bootstrap Password to set up the administrator account.

‍

‍

After entering the bootstrap password, Rancher will ask you to define a permanent password for the admin user.

# View the Rancher pod
`kubectl get pods -A | grep rancher`

# View the installation log
`tail -f /var/log/cuemby/bootstrap.log`

# Check the health endpoint
`curl -k https://<VM_IP>/healthz`

‍

Expected output

ok

‍

Expected pod output:

NAME                       READY   STATUS    RESTARTS
rancher-xxxxxxxxx-xxxxx    1/1     Running   0        ← Running ✓

‍

ℹ️ Even if the pod is in Running mode, Rancher may take several additional minutes to initialize all its internal controllers. Wait until /healthz responds ok before accessing the UI.

‍

⚠️ Set RANCHER_HOSTNAME before deployment if you plan to use your own domain. Changing it afterward requires manual certificate reconfiguration and may break existing registered clusters.

1. Open the URL, enter the Bootstrap Password, and set your permanent admin password.
2. Rancher automatically detects the local k3s cluster. Click on Local to manage it.
3. Explore namespaces, workloads, services, and volumes from the Cluster Management menu.
4. Connect additional clusters from Cluster Management → Create or Import Existing

💡 Tip: Rancher automatically manages the k3s cluster where it's installed as a local cluster. It's the starting point for exploring all the Cuemby Marketplace resources deployed on the same VM, offering a more comprehensive view than Portainer for multi-cluster operations.