---
name: satellite-ts-cluster-ocdebug
title: Why can't I log in to my worker nodes or debug them with `oc debug` command?
description: Resolve issues logging in to worker nodes or running the `oc debug` command in your Satellite cluster.
last-updated: 2026-08-17
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/satellite?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why can't I log in to my worker nodes or debug them with `oc debug` command?
{: #ts-cluster-ocdebug}

Resolve issues logging in to worker nodes or running the `oc debug` command in your Satellite cluster.
{: shortdesc}

When you log in to the terminal of a worker node or run the `oc debug node` command from the CLI, you receive the following error.
{: tsSymptoms}


```sh
oc debug node/10.200.0.00
Starting pod/10200000-debug ...

To use host binaries, run chroot /host
Pod IP: 10.200.0.10
If you don't see a command prompt, try pressing enter.

Removing debug pod ...
Error from server: error dialing backend: dial tcp 10.200.0.00:12345: connect: connection timed out
```
{: screen}

A faulty node is causing DNS issues in the cluster.
{: tsCauses}

To resolve this issue, determine which node is causing the error. Then, stop that node and try running `oc debug node`. See [Debugging clusters](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-clusters-debug&format=markdown).
{: tsResolve}

If you cannot determine which node is causing the issue, [reboot your Satellite location control plane hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-host-update-location&format=markdown) one at a time and try running `oc debug node`. If you are still receiving the error, then [reboot one worker node at a time](https://cloud.ibm.com/docs/satellite?topic=satellite-host-update-workers&format=markdown).

If you can determine that a particular worker node is causing the problem and the `oc debug node` command is successful on other worker nodes, then replace the host where the `oc debug node` command fails.