cloudreve安装（docker）

[javencpdd]

Describe the bug docker安装后，配置信息中的ssl和socket要怎么配置呀 版本 V3.8.3

[javencpdd]

---

/ \ | ___ _ _ | | __ _____ _____ / / | |/ _ | | | |/ _ | '/ _ \ \ / / _
/ /| | () | || | (| | | | _/\ V / / _/||_/ _,|_,|_| _| _/ ___|

V3.8.3 Commit #88409cc Pro=false

[Info] 2023-10-26 00:45:35 Initializing database connection... [Info] 2023-10-26 00:45:35 Database version fulfilled, skip schema migration. [Info] 2023-10-26 00:45:35 Initialize task queue with WorkerNum = 10 [Info] 2023-10-26 00:45:35 Initialize crontab jobs... [Info] 2023-10-26 00:45:35 Current running mode: Master. [Info] 2023-10-26 00:45:35 Listening to ":443" [Error] 2023-10-26 00:45:35 Failed to listen to ":443": open C:\Users\i\Documents\fullchain.pem: no such file or directory [Info] 2023-10-26 00:45:54 Signal terminated received, shutting down server... [Warning] 2023-10-26 00:45:54 Failed to persist cache: open temp/cache_persist.bin: no such file or directory

[charlieJ107]

首先请确认你是否需要启用SSL

如果你只是在内网部署来玩玩，没有打算放在公网下供大家访问，亦或者你信任从你自己的设备到cloudreve服务器的连接是安全的，那么你可以不需要启用SSL，因而直接在每一行前面加一个英文的分号';'注释掉这部分即可。

如果你需要SSL，那么请确认你是否需要让Cloudreve来处理SSL的部分

如果你的cloudreve在反向代理后面，包括但不限于nginx, IIS等，那么你可能需要使用这些反向代理来启用SSL，而非利用cloudreve自带的SSL功能。处理的方式与前面一样，直接在每一行前面加一个英文的分号';'注释掉这部分即可。

如果你需要让Cloudreve来处理SSL，那么请确认你是否准备好了SSL证书

假设你知道这是什么，你需要从受信任的CA获取或自签名一个SSL证书，并将其存储到一个安全的目录下，将这两个配置指向证书即可。如果你不知道这是什么，建议先去搜索一些相关的资料再来配置。

[chiwos]

Hi, @javencpdd

The other day I installed Cloudreve for the first time and chose Docker just like you.

I used the docker-compose.yml configuration and in the cloudreve component under the volumes section I added 2 paths to the keys so that docker can access them on the host:

- /etc/letsencrypt/live/your.host.name/fullchain.pem:/etc/letsencrypt/live/your.host.name/fullchain.pem
- /etc/letsencrypt/live/your.host.name/privkey.pem:/etc/letsencrypt/live/your.host.name/privkey.pem

I think in your case you can set it as:

- c:\users\i\documents\fullchain.pem:/etc/cert/fullchain.pem
- c:\users\i\documents\privkey.pem:/etc/cert/privkey.pem

The Cloudereve configuration in my case states:

[SSL]
Listen = :443
CertPath = /etc/letsencrypt/live/your.host.name/fullchain.pem
KeyPath = /etc/letsencrypt/live/your.host.name/privkey.pem

In your case:

[SSL]
Listen = :443
CertPath = /etc/cert/fullchain.pem
KeyPath = /etc/cert/privkey.pem

Don't forget to change the ports in docker-compose.yml to 443:443 for cloudreve. And be sure to restart the Cloudreve container with the commands:

docker compose down cloudreve
docker compose up -d

The "down" command will delete the container, and the "up" command will recreate it with new settings.

I hope this information will be useful.