This message was deleted.

There is also a rancher-agent with the command "--no-register --only-write-certs" in a crashing loop. It looks like they both depend on each other. Rancher:

2022/11/21 14:01:56 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6443/version?timeout=15m0s>": dial tcp 127.0.0.1:6443: connect: connection refused
exit status 1

Rancher-Agent:

INFO: Arguments: --no-register --only-write-certs --node-name prod-kubernetes-rancher --server <https://DOMAIN1:8443> --token REDACTED --ca-checksum ...
INFO: Environment: CATTLE_ADDRESS=IP1 CATTLE_AGENT_CONNECT=true CATTLE_INTERNAL_ADDRESS= CATTLE_NODE_NAME=prod-kubernetes-rancher CATTLE_SERVER=<https://DOMAIN1:8443> CATTLE_TOKEN=REDACTED CATTLE_WRITE_CERT_ONLY=true
INFO: Using resolv.conf: nameserver 127.0.0.53 options edns0
WARN: Loopback address found in /etc/resolv.conf, please refer to the documentation how to configure your cluster to resolve DNS properly
ERROR: <https://DOMAIN1:8443/ping> is not accessible (Failed to connect to DOMAIN1 port 8443: Connection refused)

Where

Domain1:8443

is the rancher host that requires the rancher container to run

Instructions to update the Rancher cert: https://docs.ranchermanager.rancher.io/v2.6/getting-started/installation-and-upgrade/resources/update-rancher-certificate