From d2815b87071d6b45098d19f039c2bef9212c20cd Mon Sep 17 00:00:00 2001 From: Petr Kovar Date: Thu, 26 Jun 2025 21:01:10 +0200 Subject: [PATCH] Update docs/troubleshooting/other-troubleshooting-tips/networking.md --- docs/troubleshooting/other-troubleshooting-tips/networking.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/troubleshooting/other-troubleshooting-tips/networking.md b/docs/troubleshooting/other-troubleshooting-tips/networking.md index 4c0efb72094..aaf3534d9a1 100644 --- a/docs/troubleshooting/other-troubleshooting-tips/networking.md +++ b/docs/troubleshooting/other-troubleshooting-tips/networking.md @@ -15,7 +15,9 @@ Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG Double check if all the [required ports](../../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/node-requirements-for-rancher-managed-clusters.md#networking-requirements) are opened in your (host) firewall. The overlay network uses UDP in comparison to all other required ports which are TCP. ## Check if your downstream node can communicate to Rancher Manager -Rancher components with HTTP endpoints generally contain a `ping` liveness probe which you can use to test connectivity. Replace the $RANCHER_URL as appropriate and run the following from a node to check that it has connectivity to Rancher Manager's servers in the `local` cluster. If successfully it should return `pong`. + +Rancher components with HTTP endpoints generally contain a `ping` liveness probe which you can use to test connectivity. Replace the `$RANCHER_URL` as appropriate and run the following from a node to check that it has connectivity to Rancher Manager's servers in the `local` cluster. If successful, it should return `pong`. + ``` curl -k https://$RANCHER_URL/ping ```