Hello everyone, I’m currently migrating my Rancher instance from my home server to a VPS. I followed the steps outlined here and successfully completed the migration. Previously, I had a single node with all roles, but now I want to configure the VPS as the master node and my home machine as the worker node. To connect all the nodes without exposing them to the WAN, I use WireGuard, which results in ip changes. I ran the script to add the master node to the cluster, but the master is trying to access the worker’s RKE2 server, which it currently can’t reach. I’m not sure what’s going wrong, it seems like Rancher hasn’t recognized the new IP address. I'm not sure if this is the appropriate channel because it seems like a rancher issue, let me know rke2-server on the master node:

Aug 28 13:15:37 vps-ea6c09db sh[327929]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
Aug 28 13:15:37 vps-ea6c09db rke2[327936]: time="2024-08-28T13:15:37Z" level=warning msg="not running in CIS mode"
Aug 28 13:15:37 vps-ea6c09db rke2[327936]: time="2024-08-28T13:15:37Z" level=info msg="Applying Pod Security Admission Configuration"
Aug 28 13:15:37 vps-ea6c09db rke2[327936]: time="2024-08-28T13:15:37Z" level=info msg="Starting rke2 v1.28.10+rke2r1 (b0d0d687d98f4fa015e7b30aaf2807b50edcc5d7)"
Aug 28 13:15:43 vps-ea6c09db rke2[327936]: time="2024-08-28T13:15:43Z" level=fatal msg="starting kubernetes: preparing server: failed to get CA certs: Get \"https://[2001:******]:9345/cacerts\": dial tcp [2001:*******]:9345: connect: no route to host"
Aug 28 13:15:43 vps-ea6c09db systemd[1]: rke2-server.service: Main process exited, code=exited, status=1/FAILURE