> For the complete documentation index, see [llms.txt](https://docs.clore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clore.ai/clore.ai/clore.ai-eng-es/para-hosts/server-offline-on-clore.ai.md).

# Solución de problemas

***

**Problema:** El servidor está en línea en HiveOS, pero aparece sin conexión en Clore.ai.\
**Síntoma:** El servidor aparece como en línea en HiveOS, pero permanece sin conexión en la plataforma Clore.

***

#### 1. Compruebe el estado del servicio Clore:

Ejecuta el comando:

```
systemctl status clore-hosting.service
```

Si la respuesta es`Activo: inactivo (muerto)` — el servicio no se está ejecutando y no está habilitado al inicio.

2. Habilite el inicio automático e inicie el servicio:

```
systemctl enable clore-hosting.service
systemctl start clore-hosting.service
```

Compruebe de nuevo:

```
systemctl status clore-hosting.service
```

Si el estado del servicio es`activo (en ejecución)` — el servidor debería aparecer en línea en la plataforma Clore.

3. Para evitar problemas después del reinicio, asegúrese de añadir todos los componentes necesarios al inicio automático:

```
systemctl enable clore-hosting.service
systemctl enable docker.service
systemctl enable docker.socket
```

4. Compruebe la funcionalidad después del reinicio:

```
reboot
```

Después del reinicio, el servidor debería iniciarse automáticamente y aparecer en línea.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.clore.ai/clore.ai/clore.ai-eng-es/para-hosts/server-offline-on-clore.ai.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.