This message was deleted.

Rancher will still need 'cert-manager' for internal communications. You probably need to add the '--set tls=external' option to your helm install. See: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/installation-references/helm-chart-options#external-tls-termination

Thanks, @acoustic-addition-45641 - installing

cert-manager

seems to have resolved the issue. The command line used was:

helm install \
  cert-manager jetstack/cert-manager \
  --namespace cert-manager \
  --create-namespace \
  --version v1.13.3 \
  --set installCRDs=true \
  --kubeconfig /etc/rancher/k3s/k3s.yaml