[Bug] lobe-chat-db使用compose线上部署，logto启动后自动退出（其他服务正常） #4009

[Silas-Xu]

📦 Environment

Docker

📌 Version

v1.36.33

💻 Operating System

Ubuntu

🌐 Browser

Edge

🐛 Bug Description

这个bug本来在 #4009 中解决，解决方案是指定Logto的版本为1.19.0，然而当我将lobe-chat-db更新到最新的v1.36.33后，即使采用指定版本的Logto，仍然无法正常启动Logto，异常信息与 #4009 相同。
是需要做一些额外的改动吗，如果改用casdoor的方案替换logto，能在部署文档中提供一下详细步骤吗？（部署文档中的域名模式只提供了Logto的配置方式，希望能增加casdoor的方式🙏）

📷 Recurrence Steps

No response

🚦 Expected Behavior

No response

📝 Additional Information

No response

[lobehubbot]

👀 @Silas-Xu

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot[bot]]

@Silas-Xu 你好！我是Dosu，我是一个可以帮助你解决bug、回答问题，并成为贡献者的机器人。我会在等待人类维护者的时候帮助你。期待和你一起解决问题！🤖

To address the issue with Logto not starting after updating lobe-chat-db to version v1.36.33, you might consider switching to Casdoor as an authentication provider. Here are the detailed steps for configuring Casdoor in your lobe-chat deployment:

1. Create a Casdoor Application:

   • Access your Casdoor WebUI (default is http://localhost:8000/) using the default credentials (admin / 123).
   • Go to Identity -> Applications.
   • Create a new application named LobeChat or modify the existing built-in application.
   • Set the following fields:
     • Name, Display Name: LobeChat
     • Redirect URLs:
       • Local Development: http://localhost:3210/api/auth/callback/casdoor
       • Local Network IP Deployment: http://your_server_ip:3210/api/auth/callback/casdoor
       • Public Network: https://lobe.example.com/api/auth/callback/casdoor
   • Optionally, set a Logo and Form CSS for a better user experience:
     • Logo: https://lobehub.com/icon-192x192.png
     • Form CSS:

       <style>
         .login-panel {
           padding: 40px 70px 0 70px;
           border-radius: 10px;
           background-color: #ffffff;
           box-shadow: rgba(17, 12, 46, 0.15) 0px 48px 100px 0px;
         }
         .panel-logo {
           width: 64px;
         }
         .login-logo-box {
           margin-top: 20px;
         }
         #parent-area > main > div > div.login-content > div.login-panel > div.login-form > div > div > button {
           box-shadow: none !important;
           border-radius: 10px !important;
           transition-property: all;
           transition-timing-function: cubic-bezier(0.4, 0, 0.2, 1);
           transition-duration: 150ms;
           border: 1px solid #eee !important;
         }
         @media (max-width: 640px) {
           .login-panel {
             padding: 40px 0 0 0;
             box-shadow: none;
           }
         }
       </style>

   • Copy the Client ID and Client Secret.

2. Configure Environment Variables:

   • Set the Client ID and Client Secret as AUTH_CASDOOR_ID and AUTH_CASDOOR_SECRET in your environment variables.
   • Configure AUTH_CASDOOR_ISSUER based on your environment:
     • Local Development: http://localhost:8000/
     • Local Network: http://your_server_ip:8000/
     • Public Network: https://lobe-auth-api.example.com/
   • Ensure these environment variables are set for LobeChat:
     • NEXT_AUTH_SECRET: Generate using openssl rand -base64 32.
     • NEXT_AUTH_SSO_PROVIDERS: Set to casdoor.
     • AUTH_CASDOOR_ID: The client ID from Casdoor.
     • AUTH_CASDOOR_SECRET: The client secret from Casdoor.
     • AUTH_CASDOOR_ISSUER: The OpenID Connect issuer.
     • NEXTAUTH_URL: The callback address for OAuth verification, e.g., https://lobe.example.com/api/auth.

These steps will help you configure Casdoor as an authentication provider for LobeChat ^[1][2][3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[arvinxx]

大概率跟 LobeChat 没关系，建议检查下 logto 的版本和配置

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

It most likely has nothing to do with LobeChat. It is recommended to check the configuration of logto.

[SpeedupMaster]

先退回之前的版本，看下能不能正常启动，然后进入logto容器手动更新数据库。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

First return to the previous version to see if it can start normally, and then enter the logto container to manually update the database.

[Silas-Xu]

logto版本用1.19.0和latest都没成功。
更新前：logto==1.19.0, lobe==1.36.22 可以启动成功
更新后：logto==1.19.0, lobe==1.36.33 无法启动成功
更新时没有对配置做任何更改。
（已暂时回退到更新前的版本了）

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Logto versions 1.19.0 and latest were unsuccessful.
Before update: logto==1.19.0, lobe==1.36.22 can be started successfully
After update: logto==1.19.0, lobe==1.36.33 failed to start successfully
No configuration changes were made during the update.
(Has been temporarily rolled back to the pre-update version)

[SpeedupMaster]

casdoor可以参考这个

services:
  postgresql:
    image: pgvector/pgvector:pg16
    container_name: lobe-postgres
    ports:
      - 5432:5432
    volumes:
      - ./data:/var/lib/postgresql/data
    environment:
      - POSTGRES_DB=lobe
      - POSTGRES_PASSWORD=b750e83ac80f7261513axxxxxxxxx
    healthcheck:
      test:
        - CMD-SHELL
        - pg_isready -U postgres
      interval: 5s
      timeout: 5s
      retries: 5
    restart: always

  minio:
    image: minio/minio
    container_name: lobe-minio
    ports:
      - 9000:9000
      - 9001:9001
    volumes:
      - ./s3_data:/etc/minio/data
    environment:
      - MINIO_ROOT_USER=
      - MINIO_ROOT_PASSWORD=
      - MINIO_DOMAIN=
      - MINIO_API_CORS_ALLOW_ORIGIN=
    restart: always
    command: |
      server /etc/minio/data --address ":9000" --console-address ":9001"

  casdoor:
    image: casbin/casdoor:latest
    container_name: lobe-casdoor
    ports:
      - 8000:8000
    depends_on:
      postgresql:
        condition: service_healthy
    environment:
      - RUNNING_IN_DOCKER=true
      - driverName=postgres
      - dataSourceName=postgres://postgres:b750e83ac80f7261513axxxxxxxxx@postgresql:5432/casdoor?sslmode=disable
    volumes:
      - ./files:/files
    entrypoint:
      - /bin/sh
      - -c
      - ./server --createDatabase=true
      
  lobe:
    image: lobehub/lobe-chat-database
    container_name: lobe-database
    ports:
      - 3210:3210
    depends_on:
      - postgresql
      - minio
      - casdoor
    env_file:
      - .env
    restart: always
volumes:
  data:
    driver: local
  s3_data:
    driver: local
networks: {}

[Silas-Xu]

casdoor可以参考这个

services:
...

感恩，我用的域名模式，做了反向代理，可能需要登陆做一些配置啥的，只改docker-compsoe.yml的话不知道行不行，我回去试试。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Casdoor can refer to this

services:
...

Thank you. I used the domain name mode and made a reverse proxy. I may need to log in and do some configuration. I don’t know if it will work if I just change docker-compsoe.yml. I will go back and try.

[SpeedupMaster]

logto版本用1.19.0和latest都没成功。 更新前：logto==1.19.0, lobe==1.36.22 可以启动成功 更新后：logto==1.19.0, lobe==1.36.33 无法启动成功 更新时没有对配置做任何更改。 （已暂时回退到更新前的版本了）

进入logto容器运行logto db alteration deploy更新数据库，然后再用最新版的logto试试。最好先备份下logto的数据库文件

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Logto version 1.19.0 and latest have no success. Before the update: logto==1.19.0, lobe==1.36.22 can be started successfully. After the update: logto==1.19.0, lobe==1.36.33 cannot be started successfully. No changes were made to the configuration during the update. (Has been temporarily rolled back to the pre-update version)

Enter the logto container and run logto db alteration deploy to update the database, and then try with the latest version of logto. It is best to back up the logto database file first.

[SpeedupMaster]

casdoor可以参考这个

services:
...

感恩，我用的域名模式，做了反向代理，可能需要登陆做一些配置啥的，只改docker-compsoe.yml的话不知道行不行，我回去试试。

和logto部署基本上一样的，就只是把logto换成casdoor

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Casdoor can refer to this

services:
...

Thanks, I used the domain name mode and made a reverse proxy. I may need to log in and do some configuration. I don’t know if it will work if I just change docker-compsoe.yml. I will go back and try.

It is basically the same as logto deployment, just replace logto with casdoor

[Silas-Xu]

谢谢大佬，已解决。

---

解决过程：
先备份目录，然后进入logto容器内，执行命令：

# 位于容器内的/etc/logto目录下
npm run alteration deploy

输出信息为：

> alteration
> logto db alt deploy

info Found 0 alteration to deploy

然后停止容器，将docker-compose.yml中的lobe-chat-db指定到最新版本，logto仍然指定1.19.0版本，docker-compose up -d重新启动容器。成功🎉

[lobehubbot]

✅ @Silas-Xu

This issue is closed, If you have any questions, you can comment and reply.
此问题已经关闭。如果您有任何问题，可以留言并回复。

[charIeszhao]

Try to specify the target version on DB alteration. E.g.

logto db alt deploy 1.20.0

[fivestrong]

升级到logto 1.22，修改了 docker-compose.yml 中
environment:
- 'TRUST_PROXY_HEADER=1'
- 'DATABASE_CONNECTION_TIMEOUT=60000' # 新增
entrypoint: ['sh', '-c', 'npm run cli db alteration deploy 1.22.0 && npm run cli db seed -- --swe && npm start'] # 替换原来的

lobe-chat-db v1.39.0 logto 1.22.0 正常启用