---
name: satellite-ts-hosts-login
title: Debugging host connectivity issues
description: To debug a host issue further, log in to your host machine by following the steps in this topic.
last-updated: 2026-08-25
---

> ## 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.

# Debugging host connectivity issues
{: #ts-hosts-login}

To debug a host issue further, log in to your host machine by following the steps in this topic.
{: shortdesc}

You can SSH into the host machine if you did not assign the host to a cluster, or if the assignment failed. Otherwise, Satellite disables the ability to log in to the host by using SSH for security purposes. You can [remove the host](https://cloud.ibm.com/docs/satellite?topic=satellite-host-remove&format=markdown) and reload the operating system to restore the ability to SSH into the host machine.
{: note}

Log in to your host by completing the following steps for your host type and and host assignment status.

- [Enabling non-root SSH on RHCOS hosts before assignment](https://cloud.ibm.com/docs/satellite?topic=satellite-enabling-ssh-on-hosts&format=markdown#non-root-ssh-before-coreos).
- [Enabling non-root SSH on RHEL hosts before assignment](https://cloud.ibm.com/docs/satellite?topic=satellite-enabling-ssh-on-hosts&format=markdown#non-root-ssh-before-rhel).
- [Enabling root SSH on hosts after assignment](https://cloud.ibm.com/docs/satellite?topic=satellite-enabling-ssh-on-hosts&format=markdown#root-ssh-after-assignemnt).



## First boot did not complete successfully
{: #ts-hosts-login-first-boot}

You receive output similar to the following messages.

```sh
export HOME=/root
HOME=/root
'[' '!' -f /var/log/firstboot.flag ']'
~
```
{: codeblock}

The first boot did not complete successfully. Check the `/tmp/bootstrap/bootstrap_base.log` file and continue looking for errors.

## Host registration script fails
{: #ts-hosts-login-host-script}

You receive output similar to the following messages. The package name in the output varies depending on your environment.

```sh
No package matching '\''container-selinux'\'' found available, installed or updated
No package rh-python36 available. Error: Nothing to do
```
{: codeblock}

For more information about these messages, see [Host registration script fails](https://cloud.ibm.com/docs/satellite?topic=satellite-host-registration-script-fails&format=markdown).


## Host is attempting to register with the location
{: #ts-hosts-login-host-register}

You receive output similar to the following message.

```sh
kubectl --kubeconfig=/tmp/bootstrap/priveledgedcertdir/privledged-kubeconfig
```
{: codeblock}

The host is attempting to register with the location.

1. Find the Satellite control plane endpoint.

    ```sh
    ibmcloud sat location get --location LOCATION_ID
    ```
    {: pre}
    
2. Find the **Public Service Endpoint URL** field, for example, `https://c103-e.containers.cloud.ibm.com:12345`.
3. Confirm your connection exists by running `nc -z -v <ENDPOINT>` from your host. For example,
    
    ```sh
    nc -z -v c103-e.containers.cloud.ibm.com 12345
    ```
    {: pre}
    
4. Repeat the previous step to verify that your host can connect to each of the required outbound [hostnames for your region](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network-outbound&format=markdown).

## RHCOS Machine cannot be reached on the network
{: #ts-hosts-login-cannot-reach-rhcos}

[RHCOS]{: tag-red}

You receive output similar to the following messages.

```sh
curl: (6) Could not resolve host
```
{: codeblock}

The machine cannot be reached on the network. Check that your machine meets the [minimum requirements for network connectivity](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs&format=markdown), [remove the host](https://cloud.ibm.com/docs/satellite?topic=satellite-host-remove&format=markdown), and try to [add](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts&format=markdown) and [assign](https://cloud.ibm.com/docs/satellite?topic=satellite-assigning-hosts&format=markdown) the host again. 

Alternatively, the infrastructure provider network has connectivity issues, such as a failed connection. Consult the infrastructure provider documentation for further debugging steps.

## RHEL machine cannot be reached on the network
{: #ts-hosts-login-cannot-reach}

[RHEL]{: tag-warm-gray}

You receive output similar to the following messages.

```sh
curl: (6) Could not resolve host: <URL>.com; Unknown error
tar -xvf bootstrap.tar
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
[[ -n ‘’ ]]
echo ‘Failed to untar bootstrap.tar’
Failed to untar bootstrap.tar` \n `+ rm -rf /tmp/bootstrap
```
{: codeblock}

The machine cannot be reached on the network. Check that your machine meets the [minimum requirements for network connectivity](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs&format=markdown), [remove the host](https://cloud.ibm.com/docs/satellite?topic=satellite-host-remove&format=markdown), and try to [add](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts&format=markdown) and [assign](https://cloud.ibm.com/docs/satellite?topic=satellite-assigning-hosts&format=markdown) the host again. Alternatively, the infrastructure provider network has connectivity issues, such as a failed connection. Consult the infrastructure provider documentation for further debugging steps.