This message was deleted.

The errors regarding the sync of the chart repos are not related to the login into Rancher and can be ignored for now. What do you exactly mean by you can't login? Can you access the UI? Does it say "Password incorrect when trying to log in? Do you receive an output from "kubectl get secret..."-command?

@modern-winter-77378: 1. rancher.local login ui was accessible a. username: admin b. password: admin using --set bootstrapPassword=admin via helm install rancher rancher-latest/rancher --namespace cattle-system --set hostname=rancher.local --set replicas=1 ~*--*~set bootstrapPassword=admin 2. Using kubectl get secret --namespace cattle-system bootstrap-secret -o go-template='{{.data.bootstrapPassword|base64decode}}{{ "\n" }}' showed the same password: admin 3. Still unable to log into Rancher UI using admin/admin 4. Long and short, I rolled back the RKE2 VMs and reinstalled Rancher v2.9.0 without the --set.bootstrapPassword=admin option and was able to log into Rancher UI 5. Not sure if it matters but all of these VMs are running on my local MBP M3Max w/ 64 GB RAM. We also have RKE2 v1.28.2 on 3 worker nodes with 80 ARM64 cores + 512 GB RAM each and Rancher v2.9 on a 40 AMD cores + 256 GB RAM. We are looking to run both RKE2 v1.28.2 + Rancher 2.9 on the 80 ARM64 core/512GB RAM machines in the lab...and if feasible, roll out to our multiple global data centers w/ Rancher/RKE2 support licenses.