This message was deleted.

Hi, Jonas. I have experienced a similar issue before. I have found that removing the

certificate-authority-data

information from the KUBECONFIG file that you are using generally resolves this (make a backup first). Let me know if this works or not.

mmh i not sure if that helps - it fails also inside the cluster for example in the rancher ui

Does it work if you tell the client to ignore if certificate is valid?

The SAN is correctly configured inside of /etc/rancher/rke2/config.yaml - it seems it use an another certificate for that - and the Rancher UI Client has nothing todo with the local kubeconfig. I already rotated all certificates-