> 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-zh/mian-xiang-zhu-ji-fang/server-offline-on-clore.ai.md).

# 故障排除

***

**问题：** 服务器在 HiveOS 中显示在线，但在 Clore.ai 上看起来离线。\
**症状：** 服务器在 HiveOS 中显示在线，但在 Clore 平台上仍然离线。

***

#### 1. 检查 Clore 服务的状态：

运行以下命令：

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

如果返回结果为`Active: inactive (dead)` — 说明服务未运行，且未设置为开机启动。

2. 启用自启动并启动该服务：

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

再次检查：

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

如果服务状态是`active (running)` — 服务器应当会在 Clore 平台上显示在线。

3. 为避免重启后出现问题，请确保将所有必要组件添加到开机自启动：

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

4. 重启后检查功能：

```
reboot
```

重启后，服务器应自动启动并显示在线。


---

# 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-zh/mian-xiang-zhu-ji-fang/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.