# Adding Nodes to a Cluster fails with "skipped caching discovery info due to Get "https\://\<node\_IP>:4

## Problem

While adding nodes to the cluster you can see Nodes fail at step 11 with the following error

{% tabs %}
{% tab title="Bash" %}

```bash
skipped caching discovery info due to Get "https://<node_IP>:443/api?timeout=32s": dial tcp <node_IP>:443: connect: no route to host"
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed Kubernetes - All Versions

## Cause

This error usually points to a routing issue between the master nodes and the worker nodes. The nodes are unable to reach the Kube API Server which is required for a functioning cluster.

## Resolution

1. Verify that your environment satisfies all the [Networking Prerequisites.](https://platform9.com/docs/kubernetes/on-premise-kubernetes-pre-requisites#networking-pre-requisites)
2. If you are running a CentOs or RedHat distribution disable the firewalld service temporarily to verify if the required connections are being blocked - `systemctl stop firewalld`

{% hint style="warning" %}
**Warning**

Do Not disable the Firewall in a Production Environment. If you are testing internally you can temporarily disable it to determine the root cause and continue to use the product.

For production and other sensitive workloads please work with your Networking team to fulfilll the Networking Prerequisites linked above.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://platform9.com/kb/pmk/solutions/adding-nodes-to-a-cluster-fails-with-skipped-caching-discovery.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.