Difference between revisions of "Rancher Login Page Blank"
From Peter Pap's Technowiki
(Created page with "So, the Rancher login page is loading blank. You log into one of the Rancher nodes and see this: # kubectl get node E0627 01:17:45.898377 2181261 memcache.go:265] couldn'...") |
(No difference)
|
Revision as of 03:09, 27 June 2025
So, the Rancher login page is loading blank. You log into one of the Rancher nodes and see this:
# kubectl get node
E0627 01:17:45.898377 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.899229 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.901039 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.901660 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.903403 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
Error from server (InternalError): an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
You run the following command:
# openssl s_client -connect 127.0.0.1:443 -showcerts </dev/null | openssl x509 -noout -text
Can't use SSL_get_servername
depth=0 O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
verify error:num=18:self-signed certificate
verify return:1
depth=0 O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
verify error:num=10:certificate has expired
notAfter=Jun 26 01:04:33 2025 GMT
verify return:1
depth=0 O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
notAfter=Jun 26 01:04:33 2025 GMT
verify return:1
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
82:a2:22:9a:7f:ff:06:e3:cd:4e:1f:23:a6:16:fc:05
Signature Algorithm: sha256WithRSAEncryption
Issuer: O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
Validity
Not Before: Jun 26 01:04:33 2024 GMT
Not After : Jun 26 01:04:33 2025 GMT
The last line above tells you that "Kubernetes Ingress Controller Fake Certificate" has expired! To make it renew, reboot the node. Wait for it to come back up, then reboot the next node etc.