解决远程部署Hiclaw 并打通Element-Matrix的远程访问 || Solve the remote deployment of Hiclaw and open the remote access of Element-Matrix

### Bug Description

阿里的Hiclaw非常强大，但是前端这一块真的是一塌糊涂，远程部署更是噩梦，对于想在远程直接开发并部署到本地的用法非常不友好，经过一周多的测试，终于搞定了如何远程直接访问Element-Matrix的问题；

### 具体步骤如下：

1. 首先选择非本地安装，并且一定要选手动安装，不要选择快速开始，然后在网关设置里默认18080端口环节要手输8080，这是外网能访问聊天界面的关键；
2. 然后是选择域名，一定要用自己的域名。
3. 完成安装后通过公网访问 http://yourdomain.com:18088/ 点continue anyway，或直接点登录，
4. 这时候需要配置homeserver，在新的homeserver里填ip地址加端口的方式 http://123.123.123.123:8080/ 点提交。

5. 进入聊天界面给manager发消息，此时mananger会报错：

```
400
BadRequest不支持对方法 POST 的 API 调用，地址为 '/v1/chat/completions'/v1/chat/completions400
BadRequest不支持对方法 POST 的 API 调用，地址为 '/v1/chat/completions'/v1/chat/completions
```
这时候先去控制台证书管理里添加证书 [http://yourdomain.com:18001/tls-certificate ](http://yourdomain.com:18001/tls-certificate%C2%A0)如果没有证书可以去cloudflare里生成免费的；

证书添加好以后，去域名管理里绑定域名 http://yourdomain.com:18001/domain 并强制开启https ；

然后再给manager发信息，还是报错：LLM请求超时。

这时候需要去控制台修改域名 [http://yourdomain.com:18001/domain ](http://yourdomain.com:18001/domain%C2%A0) 将域名策略改为 http

然后再发消息就正常了

希望这篇文章能帮助到那些折腾hiclaw远程部署的人，也希望官方能早点修复部署问题和证书问题

### Steps to Reproduce

### 具体步骤如下：

1. 首先选择非本地安装，并且一定要选手动安装，不要选择快速开始，然后在网关设置里默认18080端口环节要手输8080，这是外网能访问聊天界面的关键；
2. 然后是选择域名，一定要用自己的域名。
3. 完成安装后通过公网访问 http://yourdomain.com:18088/ 点continue anyway，或直接点登录，
4. 这时候需要配置homeserver，在新的homeserver里填ip地址加端口的方式 http://123.123.123.123:8080/ 点提交。

5. 进入聊天界面给manager发消息，此时mananger会报错：

```
400
BadRequest不支持对方法 POST 的 API 调用，地址为 '/v1/chat/completions'/v1/chat/completions400
BadRequest不支持对方法 POST 的 API 调用，地址为 '/v1/chat/completions'/v1/chat/completions
```
这时候先去控制台证书管理里添加证书 [http://yourdomain.com:18001/tls-certificate ](http://yourdomain.com:18001/tls-certificate%C2%A0)如果没有证书可以去cloudflare里生成免费的；

证书添加好以后，去域名管理里绑定域名 http://yourdomain.com:18001/domain 并强制开启https ；

然后再给manager发信息，还是报错：LLM请求超时。

这时候需要去控制台修改域名 [http://yourdomain.com:18001/domain ](http://yourdomain.com:18001/domain%C2%A0) 将域名策略改为 http

然后再发消息就正常了

希望这篇文章能帮助到那些折腾hiclaw远程部署的人，也希望官方能早点修复部署问题和证书问题

### AI Analysis

_No response_

### Relevant Logs

```shell

```

### Component

Manager Agent

### Version / Commit

_No response_

---
### Bug Description

Alibaba's Hiclaw is very powerful, but the front-end is really a mess, and remote deployment is even more of a nightmare. It is very unfriendly to those who want to develop directly remotely and deploy it locally. After more than a week of testing, I finally solved the problem of how to directly access Element-Matrix remotely;

### The specific steps are as follows:

1. First choose non-local installation, and be sure to choose manual installation, do not choose quick start, and then enter 8080 manually in the default port 18080 in the gateway settings. This is the key to access the chat interface from the external network;
2. Then choose the domain name. Be sure to use your own domain name.
3. After completing the installation, visit http://yourdomain.com:18088/ through the public network and click continue anyway, or click login directly.
4. At this time, you need to configure the homeserver. Fill in the IP address and port in the new homeserver http://123.123.123.123:8080/ and click Submit.

5. Enter the chat interface and send a message to the manager. At this time, the manager will report an error:

```
400
BadRequestAPI call to method POST at address '/v1/chat/completions'/v1/chat/completions400
BadRequestAPI call to method POST at address '/v1/chat/completions'/v1/chat/completions
```
At this time, first go to the console certificate management to add the certificate [http://yourdomain.com:18001/tls-certificate](http://yourdomain.com:18001/tls-certificate%C2%A0). If there is no certificate, you can go to cloudflare to generate a free one;

After the certificate is added, go to domain name management to bind the domain name http://yourdomain.com:18001/domain and force https to be turned on;

Then I sent a message to the manager, but still got an error: LLM request timed out.

At this time, you need to go to the console to modify the domain name [http://yourdomain.com:18001/domain](http://yourdomain.com:18001/domain%C2%A0) and change the domain name policy to http

Then it will be normal if you send a message again

I hope this article can help those who are struggling with hiclaw remote deployment, and I also hope that the official can fix the deployment issues and certificate issues as soon as possible.

### Steps to Reproduce

### The specific steps are as follows:

1. First choose non-local installation, and be sure to choose manual installation, do not choose quick start, and then enter 8080 manually in the default port 18080 in the gateway settings. This is the key to access the chat interface from the external network;
2. Then choose the domain name. Be sure to use your own domain name.
3. After completing the installation, visit http://yourdomain.com:18088/ through the public network and click continue anyway, or click login directly.
4. At this time, you need to configure the homeserver. Fill in the IP address and port in the new homeserver http://123.123.123.123:8080/ and click Submit.

5. Enter the chat interface and send a message to the manager. At this time, the manager will report an error:

```
400
BadRequestAPI call to method POST at address '/v1/chat/completions'/v1/chat/completions400
BadRequestAPI call to method POST at address '/v1/chat/completions'/v1/chat/completions
```
At this time, first go to the console certificate management to add the certificate [http://yourdomain.com:18001/tls-certificate](http://yourdomain.com:18001/tls-certificate%C2%A0). If there is no certificate, you can go to cloudflare to generate a free one;

After the certificate is added, go to domain name management to bind the domain name http://yourdomain.com:18001/domain and force https to be turned on;

Then I sent a message to the manager, but still got an error: LLM request timed out.

At this time, you need to go to the console to modify the domain name [http://yourdomain.com:18001/domain](http://yourdomain.com:18001/domain%C2%A0) and change the domain name policy to http

Then it will be normal if you send a message again

I hope this article can help those who are struggling with hiclaw remote deployment, and I also hope that the official can fix the deployment issues and certificate issues as soon as possible.

### AI Analysis

_No response_

### Relevant Logs

```shell

```

### Component

Manager Agent

### Version/Commit

_No response_