[SOLVED] Host shows wrong IP in certificate redoing certificate doesn't work

[Unbent3949]

Hello, so as the title says, one of my host machines in my cluster does not show its proper IP in the self signed cert that proxmox makes, and it affects my cluster because my Master in said cluster thinks the machine is offline even though it is not. I can connect to it without any problems to its internal IP and from the outside (I have a load balancer and use a Cloudflare proxy). I have tried unproxying the connection when redoing the cert, and that doesn't work. Any other help would be appreciated.

This is the cert on the slave


and this is the cert on the master

Clearly, the master knows its own internal IP, but the slave doesn't. I'm not sure why that is, and I have found nothing across the forums that has helped so far.

 

[fabian]

there are no masters or salves in PVE. could you check what the hostname resolves to on both nodes? probably something is set up wrong there.. (maybe a stray entry in /etc/hosts or DNS).

 

[Unbent3949]

This is a picture of the host file on the questioned machine. As of making this post, the node is available to be connected via web but i cannot login, but I can still connect via ssh on the master node, so I can get pings and connect, but the ip is still wrong.

Also, sorry for this late info, but I am using kernel 6.2 with all updates installed, if that helps

 

[fabian]

it will use the IP that the nodename resolved to (at startup of the pve-cluster service, so if you changed something, you probably need to restart that service, and then regenerate the certificate).

 

[Unbent3949]

i didn't change anything and the whole node has restarted several times these last couple days

 

[fabian]

well, if your name is resolved wrong you need to fix that first -> then restart and regenerate the certificate..

 

[Unbent3949]

according to the pings on the machine in question it is resolving to the proper IP uisng ping <FQDN> ping come back with the correct internal IP

 

[Unbent3949]

Alright, looks like it is working well now. For those using Cloudflare to host their domain and use a reverse proxy. Make sure you have a DNS server running where you can, and keep internal pings from the host inside the network instead of proxying Cloudflare's proxy server for their IP.