# Harvester Management VIP and Node IP not accessible (HTTPS/SSH/PING)

**URL:** <https://forums.suse.com/t/harvester-management-vip-and-node-ip-not-accessible-https-ssh-ping/44310>\
**Category:** SUSE Virtualization\
**Created:** [October 15, 2024, 11:01am UTC](https://forums.suse.com/t/harvester-management-vip-and-node-ip-not-accessible-https-ssh-ping/44310 "2024-10-15T11:01:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ibn](https://avatars.discourse-cdn.com/v4/letter/i/838e76/32.png) [@Ibn](https://forums.suse.com/u/Ibn)\
**Post date:** [October 15, 2024, 11:01am UTC](https://forums.suse.com/t/harvester-management-vip-and-node-ip-not-accessible-https-ssh-ping/44310/1 "2024-10-15T11:01:26Z")

</div>

Good morning all since yesterday I’m facing to an issue after deploying my Harvester 1.3.

I followed well the installation but after all I can’ t ping my gateway (got from my firewall), then node IP not accessible also the VIP from everywhere.

for the moment my cluster have only one node. (we want to deploy it with 03 nodes)

Can anyone help me to resolve this issue please ?

---

<div class="post-metadata">

**Author:** ![ronaldsierra](https://avatars.discourse-cdn.com/v4/letter/r/eada6e/32.png) [@ronaldsierra](https://forums.suse.com/u/ronaldsierra)\
**Post date:** [October 23, 2024, 5:33pm UTC](https://forums.suse.com/t/harvester-management-vip-and-node-ip-not-accessible-https-ssh-ping/44310/2 "2024-10-23T17:33:50Z")

</div>

buen dia,

revisa en consola la salida del comando “ip a” se debe mostrar tu ip asignada luego revisa respuesta de ping a tu gateway, de lo contrario ajusta en /etc/sysconfig/network  
cambia el gateway en el archivo “ifroute-mgmt-br”  
cambia tu ip en el archivo “ifcfg-mgmt-br”

para unir los nodos te recomiendo revise el certificado del VIP o logs del comando “journalctl -f”

> <https://github.com/harvester/harvester/issues/4603>
>
> \*\*Is your enhancement related to a problem? Please describe.\*\*
> 
> 
> Users can't joi…n new nodes into Harvester clusters with configured custom certificates. The Rancher System Agent that bootstraps the node will suffer from the "certificate signed by unknown authority" issue. We need a way to add the CA to the trust list of newly joined nodes.
> 
> \*\*Describe the solution you'd like\*\*
> 
> 
> Since Rancherd will be brought up before the Rancher System Agent, injecting the CA into the system when Rancherd is processing the joining Plan is a good point in time. We already have the relevant code snippet in Rancherd, which \[fetches the CA cert provided by the embedded Rancher Manager\](https://github.com/rancher/rancherd/blob/f70e187c319d259058411e39d6dee7e036491693/pkg/cacerts/cacerts.go#L107). Adding the CA cert into the system's trust list with a few file and instruction in the joining Plan should be easy.
> 
> \*\*Describe alternatives you've considered\*\*
> 
> 
> Let users manually provide the CA during node installation. That means users must find a place to serve the CA file and fill in the URL in the \`harvester-installer\`, which is a bit cumbersome regarding user experience.
> 
> \*\*Additional context\*\*
> 
> 
> This is a follow-up issue for #4511. We only documented the workaround there.