Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 #3852

Closed
zhangleijun111 opened this issue Sep 9, 2024 · 257 comments
Closed

[Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 #3852

zhangleijun111 opened this issue Sep 9, 2024 · 257 comments
Labels
🐛 Bug Something isn't working | 缺陷

Comments

@zhangleijun111
Copy link

📦 Environment

Docker

📌 Version

centos

💻 Operating System

Windows

🌐 Browser

Chrome

🐛 Bug Description

docker-compose
services:
postgresql:
image: registry.us-west-1.aliyuncs.com/jg-images/pgvector:pg16
container_name: lobe-postgres
ports:
- '5432:5432'
volumes:
- './data:/var/lib/postgresql/data'
environment:
- 'POSTGRES_DB=lobe'
- 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC'
healthcheck:
test: ['CMD-SHELL', 'pg_isready -U postgres']
interval: 5s
timeout: 5s
retries: 5
restart: always

minio:
image: registry.us-west-1.aliyuncs.com/jg-images/minio:latest
container_name: lobe-minio
ports:
- '9000:9000'
- '9001:9001'
volumes:
- './s3_data:/etc/minio/data'
environment:
- 'MINIO_ROOT_USER=minioadmin'
- 'MINIO_ROOT_PASSWORD=minioadmin'
- 'MINIO_DOMAIN=lobe-s3-api.msftconnecttest.com'
- 'MINIO_API_CORS_ALLOW_ORIGIN=https://lobe.msftconnecttest.com' # Your LobeChat's domain name.
restart: always
command: >
server /etc/minio/data --address ":9000" --console-address ":9001"

logto:
image: registry.us-west-1.aliyuncs.com/jg-images/logto:latest
container_name: lobe-logto
ports:
- '3001:3001'
- '3002:3002'
depends_on:
postgresql:
condition: service_healthy
environment:
- 'TRUST_PROXY_HEADER=1'
- 'DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/logto'
- 'ENDPOINT=https://lobe-auth-api.msftconnecttest.com'
- 'ADMIN_ENDPOINT=https://lobe-auth-ui.msftconnecttest.com'
entrypoint: ['sh', '-c', 'npm run cli db seed -- --swe && npm start']

lobe:
image: registry.us-west-1.aliyuncs.com/jg-images/lobe-chat-database
container_name: lobe-database
ports:
- '3210:3210'
depends_on:
- postgresql
- minio
- logto
env_file:
- .env
restart: always

volumes:
data:
driver: local
s3_data:
driver: local

env
APP_URL=https://lobe.msftconnecttest.com/
KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
DATABASE_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/lobe
NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg
NEXT_AUTH_SSO_PROVIDERS=logto
NEXTAUTH_URL=https://lobe.msftconnecttest.com/api/auth
LOGTO_CLIENT_ID=YOUR_LOGTO_CLIENT_ID
LOGTO_CLIENT_SECRET=YOUR_LOGTO_CLIENT_SECRET
LOGTO_ISSUER=https://lobe-auth-api.msftconnecttest.com/oidc
S3_ACCESS_KEY_ID=YOUR_S3_ACCESS_KEY_ID
S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY
S3_ENDPOINT=https://lobe-s3-api.msftconnecttest.com
S3_BUCKET=lobe
S3_PUBLIC_DOMAIN=https://lobe-s3-api.msftconnecttest.com
S3_ENABLE_PATH_STYLE=1

📷 Recurrence Steps

我的nginx
server {
listen 443 ssl;
server_name lobe-auth-api.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; 
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; 

location / {
    proxy_pass http://localhost:3001;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

}

server {
listen 443 ssl;
server_name lobe-auth-ui.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; 
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; 

location / {
    proxy_pass http://localhost:3002;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

}

🚦 Expected Behavior

报错截图
8d045343fd19e7b3b66846f93f1a899

📝 Additional Information

No response
@zhangleijun111 zhangleijun111 added the 🐛 Bug Something isn't working | 缺陷 label Sep 9, 2024
@lobehubbot
Copy link
Member

👀 @zhangleijun111

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 DosuBot
Copy link

dosubot bot commented Sep 9, 2024

I found some similar discussions and issues that might help with your Logto login problem:

  1. logto登录提示HTTPS错误[Bug] - This discussion suggests using the following flags to bypass certificate errors temporarily: 
    --ignore-certificate-errors --unsafely-treat-insecure-origin-as-secure=http://192.168.31.11:3002
  2. 使用 Docker Compose 部署 LobeChat 服务端数据库版本时候遇到Logto 404的错误 - This discussion recommends adding an Nginx configuration to handle HTTPS properly.

To troubleshoot your issue, follow these steps:

  1. Check Docker Logs:

    docker logs -f lobe-logto
docker logs -f lobe-database
docker logs -f lobe-minio

  2. Verify Environment Variables:
    Ensure that the environment variables in your .env file are correctly set, especially for Logto:

    LOGTO_CLIENT_ID=YOUR_LOGTO_CLIENT_ID
LOGTO_CLIENT_SECRET=YOUR_LOGTO_CLIENT_SECRET
LOGTO_ISSUER=https://lobe-auth-api.msftconnecttest.com/oidc

  3. Nginx Configuration:
    Ensure that your Nginx configuration correctly reverse proxies the Logto API and UI services:

    server {
    listen 443 ssl;
    server_name lobe-auth-api.msftconnecttest.com;

    ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; 
    ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; 

    location / {
        proxy_pass http://localhost:3001;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

server {
    listen 443 ssl;
    server_name lobe-auth-ui.msftconnecttest.com;

    ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; 
    ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; 

    location / {
        proxy_pass http://localhost:3002;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

  4. CORS Configuration:
    Ensure that CORS settings are correctly configured for Logto to allow requests from your LobeChat domain:

    # In Logto configuration
CORS allowed origins: https://lobe.msftconnecttest.com

  5. Restart Services:
    After making any changes, restart the Docker services to apply the new configurations:

    docker compose up -d

  6. Check for Errors:
    Look for any errors in the logs that might indicate what is going wrong.

By following these steps, you should be able to resolve the Logto login issue. If you still encounter problems, please provide specific error messages or logs for further assistance [1][2].

To continue talking to Dosu, mention @dosu.

@BiFangKNT
Copy link
Contributor

📦 Environment

Docker

📌 Version

centos

💻 Operating System

Windows

🌐 Browser

Chrome

🐛 Bug Description

docker-compose services: postgresql: image: registry.us-west-1.aliyuncs.com/jg-images/pgvector:pg16 container_name: lobe-postgres ports: - '5432:5432' volumes: - './data:/var/lib/postgresql/data' environment: - 'POSTGRES_DB=lobe' - 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC' healthcheck: test: ['CMD-SHELL', 'pg_isready -U postgres'] interval: 5s timeout: 5s retries: 5 restart: always

minio: image: registry.us-west-1.aliyuncs.com/jg-images/minio:latest container_name: lobe-minio ports: - '9000:9000' - '9001:9001' volumes: - './s3_data:/etc/minio/data' environment: - 'MINIO_ROOT_USER=minioadmin' - 'MINIO_ROOT_PASSWORD=minioadmin' - 'MINIO_DOMAIN=lobe-s3-api.msftconnecttest.com' - 'MINIO_API_CORS_ALLOW_ORIGIN=https://lobe.msftconnecttest.com' # Your LobeChat's domain name. restart: always command: > server /etc/minio/data --address ":9000" --console-address ":9001"

logto: image: registry.us-west-1.aliyuncs.com/jg-images/logto:latest container_name: lobe-logto ports: - '3001:3001' - '3002:3002' depends_on: postgresql: condition: service_healthy environment: - 'TRUST_PROXY_HEADER=1' - 'DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/logto' - 'ENDPOINT=https://lobe-auth-api.msftconnecttest.com' - 'ADMIN_ENDPOINT=https://lobe-auth-ui.msftconnecttest.com' entrypoint: ['sh', '-c', 'npm run cli db seed -- --swe && npm start']

lobe: image: registry.us-west-1.aliyuncs.com/jg-images/lobe-chat-database container_name: lobe-database ports: - '3210:3210' depends_on: - postgresql - minio - logto env_file: - .env restart: always

volumes: data: driver: local s3_data: driver: local

env APP_URL=https://lobe.msftconnecttest.com/ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ= DATABASE_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/lobe NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg NEXT_AUTH_SSO_PROVIDERS=logto NEXTAUTH_URL=https://lobe.msftconnecttest.com/api/auth LOGTO_CLIENT_ID=YOUR_LOGTO_CLIENT_ID LOGTO_CLIENT_SECRET=YOUR_LOGTO_CLIENT_SECRET LOGTO_ISSUER=https://lobe-auth-api.msftconnecttest.com/oidc S3_ACCESS_KEY_ID=YOUR_S3_ACCESS_KEY_ID S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY S3_ENDPOINT=https://lobe-s3-api.msftconnecttest.com S3_BUCKET=lobe S3_PUBLIC_DOMAIN=https://lobe-s3-api.msftconnecttest.com S3_ENABLE_PATH_STYLE=1

📷 Recurrence Steps

我的nginx server { listen 443 ssl; server_name lobe-auth-api.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; 
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; 

location / {
    proxy_pass http://localhost:3001;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

}

server { listen 443 ssl; server_name lobe-auth-ui.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; 
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; 

location / {
    proxy_pass http://localhost:3002;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

}

🚦 Expected Behavior

报错截图 8d045343fd19e7b3b66846f93f1a899

📝 Additional Information

No response

logto的DB_URL改成@lobe-postgres，因为你是在同一个compose里的，所以不能用服务名称而应该用容器名称

@zhangleijun111
Copy link
Author

📦 环境

码头工人

📌 版本

CentOS 操作系统

💻 操作系统

窗户

🌐 浏览器

铬

🐛 Bug 描述

docker-compose 服务： PostgreSQL： 映像： registry.us-west-1.aliyuncs.com/jg-images/pgvector:pg16 container_name： lobe-postgres 端口： - '5432：5432' 卷： - './data：/var/lib/postgresql/data' 环境： - 'POSTGRES_DB=lobe' - 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC' healthcheck： test： ['CMD-SHELL'， 'pg_isready -U postgres'] 间隔： 5s 超时： 5s 重试： 5 重启： 始终
minio： image： registry.us-west-1.aliyuncs.com/jg-images/minio:latest container_name： lobe-minio ports： - '9000：9000' - '9001：9001' 卷： - './s3_data：/etc/minio/data' 环境： - 'MINIO_ROOT_USER=minioadmin' - 'MINIO_ROOT_PASSWORD=minioadmin' - 'MINIO_DOMAIN=lobe-s3-api.msftconnecttest.com' - 'MINIO_API_CORS_ALLOW_ORIGIN=https://lobe.msftconnecttest.com' # 您的 LobeChat 的域名。重启：始终命令：>服务器 /etc/minio/data --address “：9000” --console-address “：9001”
logto： image： registry.us-west-1.aliyuncs.com/jg-images/logto:latest container_name： lobe-logto ports： - '3001：3001' - '3002：3002' depends_on： PostgreSQL： 条件： service_healthy 环境： - 'TRUST_PROXY_HEADER=1' - 'DB_URL=postgresql：//postgres：uWNZugjBqixf8dxC@postgresql：5432/logto' - 'ENDPOINT=https://lobe-auth-api.msftconnecttest.com' - 'ADMIN_ENDPOINT=https://lobe-auth-ui.msftconnecttest.com' 入口点： ['sh'， '-c'， 'npm run cli db seed -- --swe & npm start']
lobe： image： registry.us-west-1.aliyuncs.com/jg-images/lobe-chat-database container_name： lobe-database ports： - '3210：3210' depends_on： - PostgreSQL - minio - logto env_file： - .env restart： always
卷： 数据： 驱动程序： 本地 s3_data： 驱动程序： 本地
env APP_URL=https://lobe.msftconnecttest.com/ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ= DATABASE_URL=postgresql：//postgres：uWNZugjBqixf8dxC@postgresql：5432/lobe NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg NEXT_AUTH_SSO_PROVIDERS=logto NEXTAUTH_URL=https://lobe.msftconnecttest.com/api/auth LOGTO_CLIENT_ID=YOUR_LOGTO_CLIENT_ID LOGTO_CLIENT_SECRET=YOUR_LOGTO_CLIENT_SECRET LOGTO_ISSUER=https://lobe-auth-api.msftconnecttest.com/oidc S3_ACCESS_KEY_ID=YOUR_S3_ACCESS_KEY_ID S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY S3_ENDPOINT=https://lobe-s3-api.msftconnecttest.com S3_BUCKET=叶 S3_PUBLIC_DOMAIN=https://lobe-s3-api.msftconnecttest.com S3_ENABLE_PATH_STYLE=1

📷 重复步骤

我的nginx server { listen 443 ssl; server_name lobe-auth-api.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; 
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; 

location / {
    proxy_pass http://localhost:3001;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

}
服务器 { listen 443 ssl; server_name lobe-auth-ui.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; 
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; 

location / {
    proxy_pass http://localhost:3002;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

}

🚦 预期行为

报错截图 8d045343fd19e7b3b66846f93f1a899

📝 其他信息

无响应

logto的改成，因为你是在同一个compose里的，所以不能用服务名称而应该用容器名称DB_URL``@lobe-postgres

DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@lobe-postgres:5432/logto 这样是吗，databaseurl 需要修改吗

@lobehubbot
Copy link
Member

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

📦 Environment

Dockers

📌 version

CentOS operating system

💻 Operating System

windows

🌐 Browser

Chrome

🐛 Bug Description

docker-compose service: PostgreSQL: image: registry.us-west-1.aliyuncs.com/jg-images/pgvector:pg16 container_name: lobe-postgres port: - '5432:5432' volume: - './data :/var/lib/postgresql/data' environment: - 'POSTGRES_DB=lobe' - 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC' healthcheck: test: ['CMD-SHELL', 'pg_isready -U postgres'] interval: 5s timeout: 5s retry :5 Reboot: Always
minio: image: registry.us-west-1.aliyuncs.com/jg-images/minio:latest container_name: lobe-minio ports: - '9000:9000' - '9001:9001' volumes: - './ s3_data:/etc/minio/data' Environment: - 'MINIO_ROOT_USER=minioadmin' - 'MINIO_ROOT_PASSWORD=minioadmin' - 'MINIO_DOMAIN=lobe-s3-api.msftconnecttest.com' - 'MINIO_API_CORS_ALLOW_ORIGIN=https://lobe.msftconnecttest.com ' # The domain name of your LobeChat. Restart: always command:>server /etc/minio/data --address ":9000" --console-address ":9001"
logto: image: registry.us-west-1.aliyuncs.com/jg-images/logto:latest container_name: lobe-logto ports: - '3001:3001' - '3002:3002' depends_on: PostgreSQL: Conditions: service_healthy environment: - 'TRUST_PROXY_HEADER=1' - 'DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/logto' - 'ENDPOINT=https://lobe-auth-api.msftconnecttest.com' - 'ADMIN_ENDPOINT=https ://lobe-auth-ui.msftconnecttest.com' Entry point: ['sh', '-c', 'npm run cli db seed -- --swe & npm start']
lobe: image: registry.us-west-1.aliyuncs.com/jg-images/lobe-chat-database container_name: lobe-database ports: - '3210:3210' depends_on: - PostgreSQL - minio - logto env_file: - .env restart: always
volumes: data: driver: local s3_data: driver: local
env APP_URL=https://lobe.msftconnecttest.com/ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ= DATABASE_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/lobe NEXT_ AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg NEXT_AUTH_SSO_PROVIDERS=logto NEXTAUTH_URL=https://lobe. msftconnecttest.com/api/auth LOGTO_CLIENT_ID=YOUR_LOGTO_CLIENT_ID LOGTO_CLIENT_SECRET=YOUR_LOGTO_CLIENT_SECRET LOGTO_ISSUER=https://lobe-auth-api.msftconnecttest.com/oidc S3_ACCESS_KEY_ID=YOUR_S3_ACCESS_KEY_ID S3_SECRET_ACCESS_KEY =YOUR_S3_SECRET_ACCESS_KEY S3_ENDPOINT=https://lobe-s3-api.msftconnecttest. com S3_BUCKET=ye S3_PUBLIC_DOMAIN=https://lobe-s3-api.msftconnecttest.com S3_ENABLE_PATH_STYLE=1

📷 Repeat steps

My nginx server { listen 443 ssl; server_name lobe-auth-api.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt;
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key;

location/{
proxy_pass http://localhost:3001;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}

}
Server { listen 443 ssl; server_name lobe-auth-ui.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt;
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key;

location/{
proxy_pass http://localhost:3002;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}

}

🚦 expected behavior

Error screenshot ![8d045343fd19e7b3b66846f93f1a899](https://private-user-images.githubusercontent.com/169867372/365583046-58888cba-f91c-42bd-b3c3-b4496dff65a9.png?jwt =eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoi cmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU4NzQ1MzE sIm5iZiI6MTcyNTg3NDIzMSwicGF0aCI6Ii8xNjk4NjczNzIvMzY1NTgzMDQ2LTU4ODg4Y2JhLWY5MWMtNDJiZC1iM2MzLWI0NDk2ZGZmNjVhOS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQ tSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwM jQwOTA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDk wOVQwOTMwMzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT00ZGY1MWVlYzMwZmE5NjFlNjc3NjRjNDFiNmQ0MDU5MjJkNGI3YmUyM2I1MzJkNzk1YmE5MTI5Y2F kZWI1ODZhJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.oib8NA7Neo3m-1 -K5XNbrrT_3kGI6Em1f_vmjfEEArc)

📝 Other information

No response

Change logto to, because you are in the same compose, you cannot use the service name but the container name DB_URL``@lobe-postgres

DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@lobe-postgres:5432/logto Is this true? Does the databaseurl need to be modified?

@BiFangKNT
Copy link
Contributor

📦 环境

码头工人

📌 版本

CentOS 操作系统

💻 操作系统

窗户

🌐 浏览器

铬

🐛 Bug 描述

docker-compose 服务： PostgreSQL： 映像： registry.us-west-1.aliyuncs.com/jg-images/pgvector:pg16 container_name： lobe-postgres 端口： - '5432：5432' 卷： - './data：/var/lib/postgresql/data' 环境： - 'POSTGRES_DB=lobe' - 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC' healthcheck： test： ['CMD-SHELL'， 'pg_isready -U postgres'] 间隔： 5s 超时： 5s 重试： 5 重启： 始终
minio： image： registry.us-west-1.aliyuncs.com/jg-images/minio:latest container_name： lobe-minio ports： - '9000：9000' - '9001：9001' 卷： - './s3_data：/etc/minio/data' 环境： - 'MINIO_ROOT_USER=minioadmin' - 'MINIO_ROOT_PASSWORD=minioadmin' - 'MINIO_DOMAIN=lobe-s3-api.msftconnecttest.com' - 'MINIO_API_CORS_ALLOW_ORIGIN=https://lobe.msftconnecttest.com' # 您的 LobeChat 的域名。重启：始终命令：>服务器 /etc/minio/data --address “：9000” --console-address “：9001”
logto： image： registry.us-west-1.aliyuncs.com/jg-images/logto:latest container_name： lobe-logto ports： - '3001：3001' - '3002：3002' depends_on： PostgreSQL： 条件： service_healthy 环境： - 'TRUST_PROXY_HEADER=1' - 'DB_URL=postgresql：//postgres：uWNZugjBqixf8dxC@postgresql：5432/logto' - 'ENDPOINT=https://lobe-auth-api.msftconnecttest.com' - 'ADMIN_ENDPOINT=https://lobe-auth-ui.msftconnecttest.com' 入口点： ['sh'， '-c'， 'npm run cli db seed -- --swe & npm start']
lobe： image： registry.us-west-1.aliyuncs.com/jg-images/lobe-chat-database container_name： lobe-database ports： - '3210：3210' depends_on： - PostgreSQL - minio - logto env_file： - .env restart： always
卷： 数据： 驱动程序： 本地 s3_data： 驱动程序： 本地
env APP_URL=https://lobe.msftconnecttest.com/ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ= DATABASE_URL=postgresql：//postgres：uWNZugjBqixf8dxC@postgresql：5432/lobe NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg NEXT_AUTH_SSO_PROVIDERS=logto NEXTAUTH_URL=https://lobe.msftconnecttest.com/api/auth LOGTO_CLIENT_ID=YOUR_LOGTO_CLIENT_ID LOGTO_CLIENT_SECRET=YOUR_LOGTO_CLIENT_SECRET LOGTO_ISSUER=https://lobe-auth-api.msftconnecttest.com/oidc S3_ACCESS_KEY_ID=YOUR_S3_ACCESS_KEY_ID S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY S3_ENDPOINT=https://lobe-s3-api.msftconnecttest.com S3_BUCKET=叶 S3_PUBLIC_DOMAIN=https://lobe-s3-api.msftconnecttest.com S3_ENABLE_PATH_STYLE=1

📷 重复步骤

我的nginx server { listen 443 ssl; server_name lobe-auth-api.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; 
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; 

location / {
    proxy_pass http://localhost:3001;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

}
服务器 { listen 443 ssl; server_name lobe-auth-ui.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; 
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; 

location / {
    proxy_pass http://localhost:3002;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

}

🚦 预期行为

报错截图 8d045343fd19e7b3b66846f93f1a899

📝 其他信息

无响应

logto的改成，因为你是在同一个compose里的，所以不能用服务名称而应该用容器名称 DB_URL@lobe-postgres ``

DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@lobe-postgres:5432/logto 这样是吗，databaseurl 需要修改吗

要的

@lobehubbot
Copy link
Member

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

📦 Environment

Dockers

📌 version

CentOS operating system

💻 Operating System

windows

🌐 Browser

Chromium

🐛 Bug Description

docker-compose service: PostgreSQL: image: registry.us-west-1.aliyuncs.com/jg-images/pgvector:pg16 container_name: lobe-postgres port: - '5432:5432' volume: - './ data:/var/lib/postgresql/data' environment: - 'POSTGRES_DB=lobe' - 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC' healthcheck: test: ['CMD-SHELL', 'pg_isready -U postgres'] interval: 5s timeout: 5s repeat Try: 5 Restart: Always
minio: image: registry.us-west-1.aliyuncs.com/jg-images/minio:latest container_name: lobe-minio ports: - '9000:9000' - '9001:9001' volumes: - '. /s3_data:/etc/minio/data' Environment: - 'MINIO_ROOT_USER=minioadmin' - 'MINIO_ROOT_PASSWORD=minioadmin' - 'MINIO_DOMAIN=lobe-s3-api.msftconnecttest.com' - 'MINIO_API_CORS_ALLOW_ORIGIN=https://lobe.msftconnecttest. com' # The domain name of your LobeChat. Restart: always command:>server /etc/minio/data --address ":9000" --console-address ":9001"
logto: image: registry.us-west-1.aliyuncs.com/jg-images/logto:latest container_name: lobe-logto ports: - '3001:3001' - '3002:3002' depends_on: PostgreSQL: condition : service_healthy environment: - 'TRUST_PROXY_HEADER=1' - 'DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/logto' - 'ENDPOINT=https://lobe-auth-api.msftconnecttest.com' - 'ADMIN_ENDPOINT= https://lobe-auth-ui.msftconnecttest.com' Entry point: ['sh', '-c', 'npm run cli db seed -- --swe & npm start']
lobe: image: registry.us-west-1.aliyuncs.com/jg-images/lobe-chat-database container_name: lobe-database ports: - '3210:3210' depends_on: - PostgreSQL - minio - logto env_file : - .env restart: always
volumes: data: driver: local s3_data: driver: local
env APP_URL=https://lobe.msftconnecttest.com/ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ= DATABASE_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/lobe NEXT _AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg NEXT_AUTH_SSO_PROVIDERS=logto NEXTAUTH_URL=https://lobe .msftconnecttest.com/api/auth LOGTO_CLIENT_ID=YOUR_LOGTO_CLIENT_ID LOGTO_CLIENT_SECRET=YOUR_LOGTO_CLIENT_SECRET LOGTO_ISSUER=https://lobe-auth-api.msftconnecttest.com/oidc S3_ACCESS_KEY_ID=YOUR_S3_ACCESS_KEY_ID S3_SECRET_ACCESS_K EY=YOUR_S3_SECRET_ACCESS_KEY S3_ENDPOINT=https://lobe-s3-api.msftconnecttest .com S3_BUCKET=ye S3_PUBLIC_DOMAIN=https://lobe-s3-api.msftconnecttest.com S3_ENABLE_PATH_STYLE=1

📷 Repeat steps

My nginx server { listen 443 ssl; server_name lobe-auth-api.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt;
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key;

location/{
proxy_pass http://localhost:3001;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}

}
Server { listen 443 ssl; server_name lobe-auth-ui.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt;
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key;

location/{
proxy_pass http://localhost:3002;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}

}

🚦 expected behavior

Report an error screenshot ! [8D45343FD19E7B3B66846F93F1A899] (https://private- user-sages.githubusercontent.com/169867372/36558888888888888888888888888CBA-F91C-4 2BD-B3C3-B4496DFF65A9.png? JWT = Eyjhbgcioijiiji1niisinr5CCI6IKPXVCJ9.EYJPC3MIOJNAXRODWIUY29TIIWIYXVKICMF3LMDGH1YNVZZXJJJJJJJJJJJJ B250ZW50LMNVBSISIMTLESI6IMTLETUILCJLEHAIOJE3MJU4NZQ1MZESIM5IZII 6Mtcyntg3ndizMSWACI6II8XNZNTGZMDQ2LTU4Y2j hlwy5mwmtndjizc1im2mzlwi0ndk2zgzmnjvhos5WBMC_WC1BBXOTQWXNB3JPD GHTPUFXQTSE1BQY1TSEEYMWC1bbxotq3JLZUDGLHBS0LBVKNPRFL MU0E1M1BRSZRAQSUYRJIWMJQWOTA5JTJGDXMTZWFZDC0XJTJGCZHD3M0X 3JLCXVLC3QMWC1BBXOTRGF0ZT0MDKWOTMWMZFAJLGTQW16LUV4CGL YZXM9MZAWJLGJLGQW16LVNPZ25HDHVYZT00ZGY1MWVLYZMWZMWZME5NJC3NJRJNDFINMQ0MDU5MJJKNGI3ymuym2i1MTI5Y2FKZWI1ODZHJLGTQW111 6LVNPZ25LZEHLYWRLCNM9AG9ZDCZHY3RVCL9PZD0WJMTL 1-K5XNbrrT_3kGI6Em1f_vmjfEEArc)

📝 Other information

No response

Change logto to, because you are in the same compose, you cannot use the service name but the container name DB_URL @lobe-postgres ``

DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@lobe-postgres:5432/logto Is this true? Does the databaseurl need to be modified?

want

@BiFangKNT
Copy link
Contributor

📦 环境

码头工人

📌 版本

CentOS 操作系统

💻 操作系统

窗户

🌐 浏览器

铬

🐛 Bug 描述

docker-compose 服务： PostgreSQL： 映像： registry.us-west-1.aliyuncs.com/jg-images/pgvector:pg16 container_name： lobe-postgres 端口： - '5432：5432' 卷： - './data：/var/lib/postgresql/data' 环境： - 'POSTGRES_DB=lobe' - 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC' healthcheck： test： ['CMD-SHELL'， 'pg_isready -U postgres'] 间隔： 5s 超时： 5s 重试： 5 重启： 始终
minio： image： registry.us-west-1.aliyuncs.com/jg-images/minio:latest container_name： lobe-minio ports： - '9000：9000' - '9001：9001' 卷： - './s3_data：/etc/minio/data' 环境： - 'MINIO_ROOT_USER=minioadmin' - 'MINIO_ROOT_PASSWORD=minioadmin' - 'MINIO_DOMAIN=lobe-s3-api.msftconnecttest.com' - 'MINIO_API_CORS_ALLOW_ORIGIN=https://lobe.msftconnecttest.com' # 您的 LobeChat 的域名。重启：始终命令：>服务器 /etc/minio/data --address “：9000” --console-address “：9001”
logto： image： registry.us-west-1.aliyuncs.com/jg-images/logto:latest container_name： lobe-logto ports： - '3001：3001' - '3002：3002' depends_on： PostgreSQL： 条件： service_healthy 环境： - 'TRUST_PROXY_HEADER=1' - 'DB_URL=postgresql：//postgres：uWNZugjBqixf8dxC@postgresql：5432/logto' - 'ENDPOINT=https://lobe-auth-api.msftconnecttest.com' - 'ADMIN_ENDPOINT=https://lobe-auth-ui.msftconnecttest.com' 入口点： ['sh'， '-c'， 'npm run cli db seed -- --swe & npm start']
lobe： image： registry.us-west-1.aliyuncs.com/jg-images/lobe-chat-database container_name： lobe-database ports： - '3210：3210' depends_on： - PostgreSQL - minio - logto env_file： - .env restart： always
卷： 数据： 驱动程序： 本地 s3_data： 驱动程序： 本地
env APP_URL=https://lobe.msftconnecttest.com/ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ= DATABASE_URL=postgresql：//postgres：uWNZugjBqixf8dxC@postgresql：5432/lobe NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg NEXT_AUTH_SSO_PROVIDERS=logto NEXTAUTH_URL=https://lobe.msftconnecttest.com/api/auth LOGTO_CLIENT_ID=YOUR_LOGTO_CLIENT_ID LOGTO_CLIENT_SECRET=YOUR_LOGTO_CLIENT_SECRET LOGTO_ISSUER=https://lobe-auth-api.msftconnecttest.com/oidc S3_ACCESS_KEY_ID=YOUR_S3_ACCESS_KEY_ID S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY S3_ENDPOINT=https://lobe-s3-api.msftconnecttest.com S3_BUCKET=叶 S3_PUBLIC_DOMAIN=https://lobe-s3-api.msftconnecttest.com S3_ENABLE_PATH_STYLE=1

📷 重复步骤

我的nginx server { listen 443 ssl; server_name lobe-auth-api.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; 
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; 

location / {
    proxy_pass http://localhost:3001;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

}
服务器 { listen 443 ssl; server_name lobe-auth-ui.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; 
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; 

location / {
    proxy_pass http://localhost:3002;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

}

🚦 预期行为

报错截图 8d045343fd19e7b3b66846f93f1a899

📝 其他信息

无响应

logto的改成，因为你是在同一个compose里的，所以不能用服务名称而应该用容器名称 DB_URL@lobe-postgres ``

DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@lobe-postgres:5432/logto 这样是吗，databaseurl 需要修改吗

听说最新版本修复了这个bug，你试试

@lobehubbot
Copy link
Member

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

📦 Environment

Dockers

📌 Version

CentOS operating system

💻 Operating system

windows

🌐 Browser

Chromium

🐛 Bug Description

docker-compose service: PostgreSQL: image: registry.us-west-1.aliyuncs.com/jg-images/pgvector:pg16 container_name: lobe-postgres port: - '5432:5432' volume: - './ data:/var/lib/postgresql/data' environment: - 'POSTGRES_DB=lobe' - 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC' healthcheck: test: ['CMD-SHELL', 'pg_isready -U postgres'] interval: 5s timeout: 5s repeat Try: 5 Restart: Always
minio: image: registry.us-west-1.aliyuncs.com/jg-images/minio:latest container_name: lobe-minio ports: - '9000:9000' - '9001:9001' volumes: - '. /s3_data:/etc/minio/data' Environment: - 'MINIO_ROOT_USER=minioadmin' - 'MINIO_ROOT_PASSWORD=minioadmin' - 'MINIO_DOMAIN=lobe-s3-api.msftconnecttest.com' - 'MINIO_API_CORS_ALLOW_ORIGIN=https://lobe.msftconnecttest. com' # The domain name of your LobeChat. Restart: always command:>server /etc/minio/data --address ":9000" --console-address ":9001"
logto: image: registry.us-west-1.aliyuncs.com/jg-images/logto:latest container_name: lobe-logto ports: - '3001:3001' - '3002:3002' depends_on: PostgreSQL: condition : service_healthy environment: - 'TRUST_PROXY_HEADER=1' - 'DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/logto' - 'ENDPOINT=https://lobe-auth-api.msftconnecttest.com' - 'ADMIN_ENDPOINT= https://lobe-auth-ui.msftconnecttest.com' Entry point: ['sh', '-c', 'npm run cli db seed -- --swe & npm start']
lobe: image: registry.us-west-1.aliyuncs.com/jg-images/lobe-chat-database container_name: lobe-database ports: - '3210:3210' depends_on: - PostgreSQL - minio - logto env_file : - .env restart: always
volumes: data: driver: local s3_data: driver: local
env APP_URL=https://lobe.msftconnecttest.com/ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ= DATABASE_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/lobe NEXT _AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg NEXT_AUTH_SSO_PROVIDERS=logto NEXTAUTH_URL=https://lobe .msftconnecttest.com/api/auth LOGTO_CLIENT_ID=YOUR_LOGTO_CLIENT_ID LOGTO_CLIENT_SECRET=YOUR_LOGTO_CLIENT_SECRET LOGTO_ISSUER=https://lobe-auth-api.msftconnecttest.com/oidc S3_ACCESS_KEY_ID=YOUR_S3_ACCESS_KEY_ID S3_SECRET_ACCESS_K EY=YOUR_S3_SECRET_ACCESS_KEY S3_ENDPOINT=https://lobe-s3-api.msftconnecttest .com S3_BUCKET=ye S3_PUBLIC_DOMAIN=https://lobe-s3-api.msftconnecttest.com S3_ENABLE_PATH_STYLE=1

📷 Repeat steps

My nginx server { listen 443 ssl; server_name lobe-auth-api.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt;
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key;

location/{
proxy_pass http://localhost:3001;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}

}
Server { listen 443 ssl; server_name lobe-auth-ui.msftconnecttest.com;

ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt;
ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key;

location/{
proxy_pass http://localhost:3002;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}

}

🚦 expected behavior

Report an error screenshot ! [8D45343FD19E7B3B66846F93F1A899] (https://private- user-sages.githubusercontent.com/169867372/36558888888888888888888888888CBA-F91C-4 2BD-B3C3-B4496DFF65A9.png? JWT = Eyjhbgcioijiiji1niisinr5CCI6IKPXVCJ9.EYJPC3MIOJNAXRODWIUY29TIIWIYXVKICMF3LMDGH1YNVZZXJJJJJJJJJJJJ B250ZW50LMNVBSISIMTLESI6IMTLETUILCJLEHAIOJE3MJU4NZQ1MZESIM5IZII 6Mtcyntg3ndizMSWACI6II8XNZNTGZMDQ2LTU4Y2j hlwy5mwmtndjizc1im2mzlwi0ndk2zgzmnjvhos5WBMC_WC1BBXOTQWXNB3JPD GHTPUFXQTSE1BQY1TSEEYMWC1bbxotq3JLZUDGLHBS0LBVKNPRFL MU0E1M1BRSZRAQSUYRJIWMJQWOTA5JTJGDXMTZWFZDC0XJTJGCZHD3M0X 3JLCXVLC3QMWC1BBXOTRGF0ZT0MDKWOTMWMZFAJLGTQW16LUV4CGL YZXM9MZAWJLGJLGQW16LVNPZ25HDHVYZT00ZGY1MWVLYZMWZMWZME5NJC3NJRJNDFINMQ0MDU5MJJKNGI3ymuym2i1MTI5Y2FKZWI1ODZHJLGTQW111 6LVNPZ25LZEHLYWRLCNM9AG9ZDCZHY3RVCL9PZD0WJMTL 1-K5XNbrrT_3kGI6Em1f_vmjfEEArc)

📝 Other information

No response

Change logto to, because you are in the same compose, you cannot use the service name but the container name DB_URL @lobe-postgres ``

DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@lobe-postgres:5432/logto Is this true? Does the databaseurl need to be modified?

I heard that the latest version fixes this bug, please try it

@zhangleijun111
Copy link
Author

zhangleijun111 commented Sep 9, 2024 via email

@lobehubbot
Copy link
Member

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

I tried it last week and it doesn't seem to work. Don't close the issue and I'll try it tomorrow.

Sent from my iPhone

------------------ Original email ------------------
Sender: Bifang @.>
Sent time: September 9, 2024 17:48
Recipient: lobehub/lobe-chat @.>
CC: zhangleijun111 @.>, Mention @.>
Topic: Re: [lobehub/lobe-chat] [Bug] I still want to ask about the issue of logto login. Can you help me check it out? The specific configuration is provided below (Issue #3852)

📦 Environment

docker

📌 Version

CentOS operating system

💻 Operating System

window

🌐 Browser

chromium

🐛 Bug Description

docker-compose service: PostgreSQL: image: registry.us-west-1.aliyuncs.com/jg-images/pgvector:pg16 container_name: lobe-postgres port: - '5432:5432' volume: - './data:/ var/lib/postgresql/data' environment: - 'POSTGRES_DB=lobe' - 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC' healthcheck: test: ['CMD-SHELL', 'pg_isready -U postgres'] interval: 5s timeout: 5s retry: 5 Restart: Always
minio: image: registry.us-west-1.aliyuncs.com/jg-images/minio:latest container_name: lobe-minio ports: - '9000:9000' - '9001:9001' volumes: - './s3_data: /etc/minio/data' environment: - 'MINIO_ROOT_USER=minioadmin' - 'MINIO_ROOT_PASSWORD=minioadmin' - 'MINIO_DOMAIN=lobe-s3-api.msftconnecttest.com' - 'MINIO_API_CORS_ALLOW_ORIGIN=https://lobe.msftconnecttest.com' # The domain name of your LobeChat. Restart: always command:>server /etc/minio/data --address ":9000" --console-address ":9001"
logto: image: registry.us-west-1.aliyuncs.com/jg-images/logto:latest container_name: lobe-logto ports: - '3001:3001' - '3002:3002' depends_on: PostgreSQL: condition: service_healthy environment : - 'TRUST_PROXY_HEADER=1' - @.:5432/logto' - 'ENDPOINT=https://lobe-auth-api.msftconnecttest.com' - 'ADMIN_ENDPOINT=https:// lobe-auth-ui.msftconnecttest.com' entry point: ['sh', '-c', 'npm run cli db seed -- --swe & npm start']
lobe: image: registry.us-west-1.aliyuncs.com/jg-images/lobe-chat-database container_name: lobe-database ports: - '3210:3210' depends_on: - PostgreSQL - minio - logto env_file: - . env restart: always
volume: data: driver: local s3_data: driver: local
env APP_URL=https://lobe.msftconnecttest.com/ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ= @.：5432/lobe NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg NEXT_ AUTH_SSO_PROVIDERS=logto NEXTAUTH_URL=https://lobe.msftconnecttest. com/api/auth logging 3_SECRET_ACCESS_KEY S3_ENDPOINT=https://lobe-s3-api.msftconnecttest.com S3_BUCKET =ye S3_PUBLIC_DOMAIN=https://lobe-s3-api.msftconnecttest.com S3_ENABLE_PATH_STYLE=1

📷 Repeat steps

My nginx server { listen 443 ssl; server_name lobe-auth-api.msftconnecttest.com;
ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; location / { proxy_pass http://localhost:3001; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; }
}
Server { listen 443 ssl; server_name lobe-auth-ui.msftconnecttest.com;
ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; location / { proxy_pass http://localhost:3002; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; }
}

🚦 Expected behavior

Error screenshot

📝 Other information

No response

Change logto to, because you are in the same compose, you cannot use the service name but the container name @.*** ``

@.***:5432/logto Is this true? Does the databaseurl need to be modified?

I heard that the latest version fixes this bug, please try it

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@BiFangKNT
Copy link
Contributor

上周试过貌似不行，issue别关明天我试下 发自我的iPhone
…
------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月9日 17:48 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 📦 环境 码头工人 📌 版本 CentOS 操作系统 💻 操作系统 窗户 🌐 浏览器 铬 🐛 Bug 描述 docker-compose 服务： PostgreSQL： 映像： registry.us-west-1.aliyuncs.com/jg-images/pgvector:pg16 container_name： lobe-postgres 端口： - '5432：5432' 卷： - './data：/var/lib/postgresql/data' 环境： - 'POSTGRES_DB=lobe' - 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC' healthcheck： test： ['CMD-SHELL'， 'pg_isready -U postgres'] 间隔： 5s 超时： 5s 重试： 5 重启： 始终 minio： image： registry.us-west-1.aliyuncs.com/jg-images/minio:latest container_name： lobe-minio ports： - '9000：9000' - '9001：9001' 卷： - './s3_data：/etc/minio/data' 环境： - 'MINIO_ROOT_USER=minioadmin' - 'MINIO_ROOT_PASSWORD=minioadmin' - 'MINIO_DOMAIN=lobe-s3-api.msftconnecttest.com' - 'MINIO_API_CORS_ALLOW_ORIGIN=https://lobe.msftconnecttest.com' # 您的 LobeChat 的域名。重启：始终命令：>服务器 /etc/minio/data --address “：9000” --console-address “：9001” logto： image： registry.us-west-1.aliyuncs.com/jg-images/logto:latest container_name： lobe-logto ports： - '3001：3001' - '3002：3002' depends_on： PostgreSQL： 条件： service_healthy 环境： - 'TRUST_PROXY_HEADER=1' - @.：5432/logto' - 'ENDPOINT=https://lobe-auth-api.msftconnecttest.com' - 'ADMIN_ENDPOINT=https://lobe-auth-ui.msftconnecttest.com' 入口点： ['sh'， '-c'， 'npm run cli db seed -- --swe & npm start'] lobe： image： registry.us-west-1.aliyuncs.com/jg-images/lobe-chat-database container_name： lobe-database ports： - '3210：3210' depends_on： - PostgreSQL - minio - logto env_file： - .env restart： always 卷： 数据： 驱动程序： 本地 s3_data： 驱动程序： 本地 env APP_URL=https://lobe.msftconnecttest.com/ KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ= @.：5432/lobe NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg NEXT_AUTH_SSO_PROVIDERS=logto NEXTAUTH_URL=https://lobe.msftconnecttest.com/api/auth LOGTO_CLIENT_ID=YOUR_LOGTO_CLIENT_ID LOGTO_CLIENT_SECRET=YOUR_LOGTO_CLIENT_SECRET LOGTO_ISSUER=https://lobe-auth-api.msftconnecttest.com/oidc S3_ACCESS_KEY_ID=YOUR_S3_ACCESS_KEY_ID S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY S3_ENDPOINT=https://lobe-s3-api.msftconnecttest.com S3_BUCKET=叶 S3_PUBLIC_DOMAIN=https://lobe-s3-api.msftconnecttest.com S3_ENABLE_PATH_STYLE=1 📷 重复步骤 我的nginx server { listen 443 ssl; server_name lobe-auth-api.msftconnecttest.com; ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; location / { proxy_pass http://localhost:3001; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } } 服务器 { listen 443 ssl; server_name lobe-auth-ui.msftconnecttest.com; ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; ssl_certificate_key /etc/nginx/ssl/ai.jiu-guang.com.key; location / { proxy_pass http://localhost:3002; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } } 🚦 预期行为 报错截图 📝 其他信息 无响应 logto的改成，因为你是在同一个compose里的，所以不能用服务名称而应该用容器名称 @.*** `` @.:5432/logto 这样是吗，databaseurl 需要修改吗 听说最新版本修复了这个bug，你试试 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

今天更新了两版啊

@lobehubbot
Copy link
Member

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

I tried it last week and it doesn’t seem to work. Don’t close the issue and I’ll try it tomorrow. Sent from my iPhone
…
------------------ Original email ------------------ Sender: Fang @ .> Sent time: 17:48, September 9, 2024 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @ .>, Mention @.> Topic: Re: [lobehub/lobe-chat] [Bug] I still want to ask about the problem of logto login. Can you help me check it out? The following is provided Detailed configuration (Issue #3852) 📦 Environment Docker 📌 Version CentOS OS 💻 OS Windows 🌐 Chrome Browser 🐛 Bug Description docker-compose Service: PostgreSQL: Image: registry.us-west-1.aliyuncs.com/ jg-images/pgvector:pg16 container_name: lobe-postgres Port: - '5432:5432' Volume: - './data:/var/lib/postgresql/data' Environment: - 'POSTGRES_DB=lobe' - 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC ' healthcheck: test: ['CMD-SHELL', 'pg_isready -U postgres'] interval: 5s timeout: 5s retry: 5 restart: always minio: image: registry.us-west-1.aliyuncs.com/jg- images/minio:latest container_name: lobe-minio ports: - '9000:9000' - '9001:9001' Volume: - './s3_data:/etc/minio/data' Environment: - 'MINIO_ROOT_USER=minioadmin' - 'MINIO_ROOT_PASSWORD =minioadmin' - 'MINIO_DOMAIN=lobe-s3-api.msftconnecttest.com' - 'MINIO_API_CORS_ALLOW_ORIGIN=https://lobe.msftconnecttest.com' # The domain name of your LobeChat. Restart: always command:> server /etc/minio/data --address ":9000" --console-address ":9001" logto: image: registry.us-west-1.aliyuncs.com/jg-images/logto :latest container_name: lobe-logto ports: - '3001:3001' - '3002:3002' depends_on: PostgreSQL: Condition: service_healthy environment: - 'TRUST_PROXY_HEADER=1' - @.:5432 /logto' - 'ENDPOINT=https://lobe-auth-api.msftconnecttest.com' - 'ADMIN_ENDPOINT=https://lobe-auth-ui.msftconnecttest.com' Entry points: ['sh', '-c ', 'npm run cli db seed -- --swe & npm start'] lobe: image: registry.us-west-1.aliyuncs.com/jg-images/lobe-chat-database container_name: lobe-database ports: - '3210:3210' depends_on: - PostgreSQL - minio - logto env_file: - .env restart: always volumes: data: driver: local s3_data: driver: local env APP_URL=https://lobe.msftconnecttest.com/ KEY_VAULTS_SECRET =Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ= @.:5432/lobe NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg NEXT_AUTH_SSO_PROVIDERS=logto NEXTAUTH_URL=https://lobe.msftconnecttest. com/api/auth LOGTO_CLIENT_ID=YOUR_LOGTO_CLIENT_ID LOGTO_CLIENT_SECRET=YOUR_LOGTO_CLIENT_SECRET LOGTO_ISSUER=https ://lobe-auth-api.msftconnecttest.com/oidc S3_ACCESS_KEY_ID=YOUR_S3_ACCESS_KEY_ID S3_SECRET_ACCESS_KEY=YOUR_S3_SECRET_ACCESS_KEY S3_ENDPOINT=https://lobe-s3-api.msftconnecttest.com S3_BUCKET=叶S3_PUBLIC_DOMAIN=https://lobe-s3- api. msftconnecttest.com S3_ENABLE_PATH_STYLE=1 📷 Repeat the steps for my nginx server { listen 443 ssl; server_name lobe-auth-api.msftconnecttest.com; ssl_certificate /etc/nginx/ssl/ai.jiu-guang.com.crt; ssl_certificate_key /etc /nginx/ssl/ai.jiu-guang.com.key; location / { proxy_pass http://localhost:3001; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header nginx/ssl/ai.jiu-guang.com.key; location / { proxy_pass http://localhost:3002; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } } 🚦 Expected behavior error report screenshot 📝 Other information no response logto change, because you are in the same compose, so you cannot use the service name but the container name @ . `` @.:5432/logto Is this true? Does the databaseurl need to be modified? I heard that the latest version has fixed this bug. Please try it. Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

Two versions were updated today

@zhangleijun111
Copy link
Author

zhangleijun111 commented Sep 9, 2024 via email

@lobehubbot
Copy link
Member

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

Is docker-compose

Sent from my iPhone

------------------ Original email ------------------
Sender: Bifang @.>
Sent time: September 9, 2024 18:33
Recipient: lobehub/lobe-chat @.>
CC: zhangleijun111 @.>, Mention @.>
Topic: Re: [lobehub/lobe-chat] [Bug] I still want to ask about the issue of logto login. Can you help me check it out? The specific configuration is provided below (Issue #3852)

@BiFangKNT
Copy link
Contributor

docker-compose是吗 发自我的iPhone
…
------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月9日 18:33 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852)

哦不对，定睛一看是六版

@lobehubbot
Copy link
Member

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

Is docker-compose? Sent from my iPhone
…
------------------ Original email ------------------ Sender: Fang @ .> Sent time: 18:33 on September 9, 2024 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @ .>, Mention @.**> Topic: Re: [lobehub/lobe-chat] [Bug] I still want to ask about the problem of logto login. Can you help me check it out? The following is provided specific configuration (Issue #3852)

Oh no, I looked closely and saw that it was page six.

@BiFangKNT
Copy link
Contributor

作者

昨天的版本是要这么改的，但是最新版本改了网络相关的，现在这么写不行了，我还在琢磨 #3814

@lobehubbot
Copy link
Member

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

Author

Yesterday's version was changed like this, but the latest version changed network-related things. Now it doesn't work like this. I'm still thinking about it #3814

@zhangleijun111
Copy link
Author

zhangleijun111 commented Sep 9, 2024 via email

@baihuyan
Copy link

兄弟交流交流 ，我跟你一样的情况啊

@lobehubbot
Copy link
Member

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

Brothers, let’s talk. I’m in the same situation as you.

@BiFangKNT
Copy link
Contributor

好的，那我nginx这段还要修改吗 发自我的iPhone
…
------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月9日 19:10 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852)

目前改用cloudflare了，logto感觉问题很多，官方都打算改成别的方案了 #3814

@BiFangKNT
Copy link
Contributor

兄弟交流交流 ，我跟你一样的情况啊

同上

@lobehubbot
Copy link
Member

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

Brothers, let’s talk. I’m in the same situation as you.

Same as above

@baihuyan
Copy link

cloudflare
logto登录后台3002那个端口的后台就会出现Internal server error.
容器日志显示域名无法解析，3001端口对应的那个域名就是404

@lobehubbot
Copy link
Member

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

cloudflare
When logto logs in to the backend on port 3002, an Internal server error will appear.
The container log shows that the domain name cannot be resolved, and the domain name corresponding to port 3001 is 404.

@zhangleijun111
Copy link
Author

作者

昨天的版本是要这么改的，但是最新版本改了网络相关的，现在这么写不行了，我还在琢磨 #3814

我试试看最新版本不是用logto了是吗

@lobehubbot
Copy link
Member

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

Author

Yesterday’s version was supposed to be changed like this, but the latest version changed network-related things. Now it doesn’t work like this. I’m still thinking about it #3814

I'll give it a try and see if the latest version uses logto, right?

@zhangleijun111
Copy link
Author

zhangleijun111 commented Sep 22, 2024 via email

@BiFangKNT
Copy link
Contributor

BiFangKNT commented Sep 22, 2024 •
edited
Loading

我用本地部署成功的，你说我看明白没哈哈，我是生产不行呀 发自我的iPhone
…
------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:54 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 首先部署lobedatabase这台机器肯定是要通外网的呀，这个我么问题，我只是说内网的其他pc访问lobe又不需要通外网，只是借助lobe访问大模型，就是典型的cs架构啊兄弟 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:40 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 我这太内网服务器通外网的呀 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:35 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 不我的域名都是内部的dns做的，不存在这个问题ipv6的问题 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 06:42 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) @zhangleijun111 我发现了一个问题：你容器的网络的驱动程序是bridge吧？bridge默认是关闭ipv6的。你的域名所对应的ip是云服务器吗？如果不是的话应该没有公网v4 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 不是哥们？你到底进入容器nslookup过没？再说了你以为你这个域名不用开放到公网？大模型怎么读你minio里的文件？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 听不懂你什么意思 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 有没有一种可能，大模型需要访问minio api域名，才能读取图片和文件？你到底看明白文档没？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

所谓的本地快捷部署和生产部署完全是两码事，前者使用的是云鉴权，根本没有后者那么麻烦（主要麻烦点是logto）

@zhangleijun111
Copy link
Author

zhangleijun111 commented Sep 22, 2024 via email

@BiFangKNT
Copy link
Contributor

BiFangKNT commented Sep 22, 2024 •
edited
Loading

我用本地部署成功的，你说我看明白没哈哈，我是生产不行呀 发自我的iPhone
…
------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:54 收件人: lobehub/lobe-chat _@**._> 抄送: zhangleijun111 _@.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 首先部署lobedatabase这台机器肯定是要通外网的呀，这个我么问题，我只是说内网的其他pc访问lobe又不需要通外网，只是借助lobe访问大模型，就是典型的cs架构啊兄弟 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:40 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 我这太内网服务器通外网的呀 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:35 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 不我的域名都是内部的dns做的，不存在这个问题ipv6的问题 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 06:42 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) @zhangleijun111 我发现了一个问题：你容器的网络的驱动程序是bridge吧？bridge默认是关闭ipv6的。你的域名所对应的ip是云服务器吗？如果不是的话应该没有公网v4 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 不是哥们？你到底进入容器nslookup过没？再说了你以为你这个域名不用开放到公网？大模型怎么读你minio里的文件？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 听不懂你什么意思 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 有没有一种可能，大模型需要访问minio api域名，才能读取图片和文件？你到底看明白文档没？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.**_>

所谓的本地快捷部署和生产部署完全是两码事，前者使用的是云鉴权，根本没有后者那么麻烦（主要麻烦点是logto）

哦我记错了，前者也是本地鉴权，但是使用的是局域网访问，不过问题还是那个问题，既然你使用了域名，那么我的说法也完全成立。你得确认你的三个服务之间能不能通过域名通信，而不是想当然 @zhangleijun111

@BiFangKNT
Copy link
Contributor

不是啊兄弟，你说的我都回答了我也觉得是dns的问题 发自我的iPhone
…
------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:58 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 而且我看csdoor出了我下周试试这个不过份吧 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:53 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 首先部署lobedatabase这台机器肯定是要通外网的呀，这个我么问题，我只是说内网的其他pc访问lobe又不需要通外网，只是借助lobe访问大模型，就是典型的cs架构啊兄弟 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:40 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 我这太内网服务器通外网的呀 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:35 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 不我的域名都是内部的dns做的，不存在这个问题ipv6的问题 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 06:42 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) @zhangleijun111 我发现了一个问题：你容器的网络的驱动程序是bridge吧？bridge默认是关闭ipv6的。你的域名所对应的ip是云服务器吗？如果不是的话应该没有公网v4 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 不是哥们？你到底进入容器nslookup过没？再说了你以为你这个域名不用开放到公网？大模型怎么读你minio里的文件？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 听不懂你什么意思 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 有没有一种可能，需要？至少logto需要。你到底进容器测过没，没测过你说得这么斩钉截铁？lobe、minio、logto必须能够互相通过域名访问对方，有一个访问不了都会有问题。你到底试过没？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 这语气怎么说得好像我求你测似的，我现在不是在帮你排查问题吗？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

dns问题是一个很宽泛的问题，你这服务不走局域网ip，而是通过域名访问对方，你的这个域名在公共dns上解析了吗？假如你只在本地dns服务器（假设你有）上解析，那么你的容器dns配置文件把这个dns服务器写上了吗？如果你没写，那么你必然解析不了

@zhangleijun111
Copy link
Author

zhangleijun111 commented Sep 22, 2024 via email

@BiFangKNT
Copy link
Contributor

不是啊兄弟，你说的我都回答了我也觉得是dns的问题 发自我的iPhone
…
------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:58 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 而且我看csdoor出了我下周试试这个不过份吧 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:53 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 首先部署lobedatabase这台机器肯定是要通外网的呀，这个我么问题，我只是说内网的其他pc访问lobe又不需要通外网，只是借助lobe访问大模型，就是典型的cs架构啊兄弟 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:40 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 我这太内网服务器通外网的呀 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:35 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 不我的域名都是内部的dns做的，不存在这个问题ipv6的问题 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 06:42 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) @zhangleijun111 我发现了一个问题：你容器的网络的驱动程序是bridge吧？bridge默认是关闭ipv6的。你的域名所对应的ip是云服务器吗？如果不是的话应该没有公网v4 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 不是哥们？你到底进入容器nslookup过没？再说了你以为你这个域名不用开放到公网？大模型怎么读你minio里的文件？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 听不懂你什么意思 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 有没有一种可能，需要？至少logto需要。你到底进容器测过没，没测过你说得这么斩钉截铁？lobe、minio、logto必须能够互相通过域名访问对方，有一个访问不了都会有问题。你到底试过没？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 这语气怎么说得好像我求你测似的，我现在不是在帮你排查问题吗？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

所以这里有三个问题：

  1. 你有在本地dns服务器解析这个域名吗？
  2. 你确认此dns服务器的ip了吗？
  3. 你的容器的dns配置文件里指向了此dns服务器吗？

@BiFangKNT
Copy link
Contributor

我懂你的意思但我现在做的是想把logto和s3都放在内网而不是云端 发自我的iPhone
…
------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 18:05 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 我用本地部署成功的，你说我看明白没哈哈，我是生产不行呀 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:54 收件人: lobehub/lobe-chat @**.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 首先部署lobedatabase这台机器肯定是要通外网的呀，这个我么问题，我只是说内网的其他pc访问lobe又不需要通外网，只是借助lobe访问大模型，就是典型的cs架构啊兄弟 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:40 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 我这太内网服务器通外网的呀 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:35 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 不我的域名都是内部的dns做的，不存在这个问题ipv6的问题 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 06:42 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) @zhangleijun111 我发现了一个问题：你容器的网络的驱动程序是bridge吧？bridge默认是关闭ipv6的。你的域名所对应的ip是云服务器吗？如果不是的话应该没有公网v4 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 不是哥们？你到底进入容器nslookup过没？再说了你以为你这个域名不用开放到公网？大模型怎么读你minio里的文件？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 听不懂你什么意思 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 有没有一种可能，大模型需要访问minio api域名，才能读取图片和文件？你到底看明白文档没？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @._> 所谓的本地快捷部署和生产部署完全是两码事，前者使用的是云鉴权，根本没有后者那么麻烦（主要麻烦点是logto） 哦我记错了，前者也是本地鉴权，但是使用的是局域网访问，不过问题还是那个问题，既然你使用了域名，那么我的说法也完全成立。你得确认你的三个服务直接能不能通过域名通信，而不是想当然 @zhangleijun111 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.**>

不，你没懂。建议再把我的评论看一遍。

@zhangleijun111
Copy link
Author

zhangleijun111 commented Sep 22, 2024 via email

@zhangleijun111
Copy link
Author

zhangleijun111 commented Sep 22, 2024 via email

@BiFangKNT
Copy link
Contributor

是的我都做了都能pin通 发自我的iPhone
…
------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 18:10 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 不是啊兄弟，你说的我都回答了我也觉得是dns的问题 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:58 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 而且我看csdoor出了我下周试试这个不过份吧 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:53 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 首先部署lobedatabase这台机器肯定是要通外网的呀，这个我么问题，我只是说内网的其他pc访问lobe又不需要通外网，只是借助lobe访问大模型，就是典型的cs架构啊兄弟 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:40 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 我这太内网服务器通外网的呀 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:35 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 不我的域名都是内部的dns做的，不存在这个问题ipv6的问题 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 06:42 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) @zhangleijun111 我发现了一个问题：你容器的网络的驱动程序是bridge吧？bridge默认是关闭ipv6的。你的域名所对应的ip是云服务器吗？如果不是的话应该没有公网v4 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 不是哥们？你到底进入容器nslookup过没？再说了你以为你这个域名不用开放到公网？大模型怎么读你minio里的文件？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 听不懂你什么意思 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 有没有一种可能，需要？至少logto需要。你到底进容器测过没，没测过你说得这么斩钉截铁？lobe、minio、logto必须能够互相通过域名访问对方，有一个访问不了都会有问题。你到底试过没？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 这语气怎么说得好像我求你测似的，我现在不是在帮你排查问题吗？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 所以这里有三个问题： 你有在本地dns服务器解析这个域名吗？ 你确认此dns服务器的ip了吗？ 你的容器的dns配置文件里指向了此dns服务器吗？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

你确认你进入容器内“ping”通了？可是事实是，某个容器不支持ping命令，你知道吗？

@zhangleijun111
Copy link
Author

zhangleijun111 commented Sep 22, 2024 via email

@BiFangKNT
Copy link
Contributor

logto这个容器是吧 发自我的iPhone
…
------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 18:12 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 是的我都做了都能pin通 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 18:10 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 不是啊兄弟，你说的我都回答了我也觉得是dns的问题 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:58 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 而且我看csdoor出了我下周试试这个不过份吧 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:53 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 首先部署lobedatabase这台机器肯定是要通外网的呀，这个我么问题，我只是说内网的其他pc访问lobe又不需要通外网，只是借助lobe访问大模型，就是典型的cs架构啊兄弟 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:40 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 我这太内网服务器通外网的呀 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:35 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 不我的域名都是内部的dns做的，不存在这个问题ipv6的问题 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 06:42 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) @zhangleijun111 我发现了一个问题：你容器的网络的驱动程序是bridge吧？bridge默认是关闭ipv6的。你的域名所对应的ip是云服务器吗？如果不是的话应该没有公网v4 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 不是哥们？你到底进入容器nslookup过没？再说了你以为你这个域名不用开放到公网？大模型怎么读你minio里的文件？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 听不懂你什么意思 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 有没有一种可能，需要？至少logto需要。你到底进容器测过没，没测过你说得这么斩钉截铁？lobe、minio、logto必须能够互相通过域名访问对方，有一个访问不了都会有问题。你到底试过没？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 这语气怎么说得好像我求你测似的，我现在不是在帮你排查问题吗？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 所以这里有三个问题： 你有在本地dns服务器解析这个域名吗？ 你确认此dns服务器的ip了吗？ 你的容器的dns配置文件里指向了此dns服务器吗？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 你确认你进入容器内“ping”通了？可是事实是，某个容器不支持ping命令，你知道吗？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

logto我因为现在没有部署了，所以没试过，我试的是minio和lobe，你有没有想过它们无法通过域名连接对方？

@BiFangKNT
Copy link
Contributor

logto这个容器是吧 发自我的iPhone
…
------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 18:12 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 是的我都做了都能pin通 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 18:10 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 不是啊兄弟，你说的我都回答了我也觉得是dns的问题 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:58 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 而且我看csdoor出了我下周试试这个不过份吧 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:53 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 首先部署lobedatabase这台机器肯定是要通外网的呀，这个我么问题，我只是说内网的其他pc访问lobe又不需要通外网，只是借助lobe访问大模型，就是典型的cs架构啊兄弟 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:40 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 我这太内网服务器通外网的呀 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:35 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 不我的域名都是内部的dns做的，不存在这个问题ipv6的问题 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 06:42 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) @zhangleijun111 我发现了一个问题：你容器的网络的驱动程序是bridge吧？bridge默认是关闭ipv6的。你的域名所对应的ip是云服务器吗？如果不是的话应该没有公网v4 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 不是哥们？你到底进入容器nslookup过没？再说了你以为你这个域名不用开放到公网？大模型怎么读你minio里的文件？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 听不懂你什么意思 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 有没有一种可能，需要？至少logto需要。你到底进容器测过没，没测过你说得这么斩钉截铁？lobe、minio、logto必须能够互相通过域名访问对方，有一个访问不了都会有问题。你到底试过没？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 这语气怎么说得好像我求你测似的，我现在不是在帮你排查问题吗？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 所以这里有三个问题： 你有在本地dns服务器解析这个域名吗？ 你确认此dns服务器的ip了吗？ 你的容器的dns配置文件里指向了此dns服务器吗？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 你确认你进入容器内“ping”通了？可是事实是，某个容器不支持ping命令，你知道吗？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

logto你也再试试进去连接lobe吧，一起测

@zhangleijun111
Copy link
Author

zhangleijun111 commented Sep 22, 2024 via email

@lobehubbot
Copy link
Member

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

I can't create an application using logto. I haven't tested the connection between mino and lobe yet, and it got stuck in the first step.

Sent from my iPhone

------------------ Original email ------------------
Sender: Bifang @.>
Sent time: September 22, 2024 18:17
Recipient: lobehub/lobe-chat @.>
CC: zhangleijun111 @.>, Mention @.>
Topic: Re: [lobehub/lobe-chat] [Bug] I still want to ask about the issue of logto login. Can you help me check it out? The specific configuration is provided below (Issue #3852)

Logto is a container, right? Sent from my iPhone
…
------------------ Original email ------------------ Sender: Bifang@.> Sent time: 2024 September 22, 18:12 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [Bug] I still want to ask Question: I have a problem with logto login. Can you help me check it out? The specific configuration is provided below (Issue #3852) Yes, I have done everything and I can pin it to my iPhone...------------- -----Original email------------------ Sender: Bifang@.> Sent time: 18:10, September 22, 2024 Recipient: lobehub /lobe-chat @.> CC: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [Bug] I still want to ask a question about the logto login problem. Can you help me check it out? The following is provided The specific configuration (Issue #3852) No, brother, I have answered everything you said. I also think it is a dns problem from my iPhone... ------------------ Original email ------------------ Sender: Bifang@.> Sent time: 17:58, September 22, 2024 Recipient: lobehub/lobe-chat @ .> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [Bug] I still want to ask a question about logto login. Can you help me check it out? The specific configuration is provided below ( Issue #3852) And I saw it on csdoor. I’ll give it a try next week. It’s not too much. Sent from my iPhone... ------------------ Original email ------ ------------ Sender: Bifang@.> Sent time: September 22, 2024 17:53 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @. >, Mention @.> Topic: Re: [lobehub/lobe-chat] [Bug] I still want to ask about the problem of logto login. Can you help me? The specific configuration is provided below (Issue #3852) First deploy lobedatabase. Each machine must be connected to the external network. This is my problem. I just mean that other PCs on the internal network do not need to connect to the external network to access the lobe. They only use the lobe to access the large model. It is a typical CS architecture. Brother sent me this iPhone… ------------------Original email------------------ Sender: Bifang@.> Sent time : September 22, 2024 17:40 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [Bug] I still I would like to ask about the problem of logto login. Can you help me? The specific configuration is provided below (Issue #3852) My internal network server is connected to the external network. I sent this message from my iPhone ----------- -------Original email------------------ Sender: Bifang@.> Sent time: 17:35, September 22, 2024 Recipient : lobehub/lobe-chat @.> CC: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [Bug] I still want to ask a question about logto login. Can you help me? The specific configuration is provided below (Issue #3852) No, my domain names are all made by internal dns, there is no such problem. The ipv6 problem comes from my iPhone ---------------- --Original email------------------ Sender: Bifang@.> Sent time: 06:42, September 22, 2024 Recipient: lobehub/lobe- chat @.> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [Bug] I still want to ask a question about logto login. Can you help me? The specific instructions are provided below. Configuration (Issue #3852) @zhangleijun111 I found a problem: the network driver of your container is bridge, right? Bridge turns off ipv6 by default. Is the IP corresponding to your domain name a cloud server? If not, there should be no public network v4 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> Not a buddy? Have you ever entered the container nslookup? Besides, do you think your domain name doesn’t need to be opened to the public network? How does the big model read the files in your minio? — Reply to this email directly, view it on GitHub, or unsubscribe. . You are receiving this because you were mentioned.Message ID: @.> Is there a possibility, need? At least logto requires it. Have you ever tested it in a container? You are so categorical in saying that you have not tested it? Lobe, minio, and logto must be able to access each other through domain names. If one of them cannot be accessed, there will be problems. Have you tried it? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> Why does this sound like I am begging you to test it? I am not helping you troubleshoot now. Problem? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> So here are three questions: Do you have a local DNS server to resolve this domain name? Have you confirmed the ip of this dns server? Does your container's dns configuration file point to this dns server? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> Are you sure you can "ping" into the container? But the fact is that a certain container does not support the ping command, did you know? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

Logto, you can also try to connect to lobe and test it together.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@BiFangKNT
Copy link
Contributor

我logto无法创建应用，还没测试mino和lobe的连接，第一步就卡死了 发自我的iPhone
…
------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 18:17 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) logto这个容器是吧 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 18:12 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 是的我都做了都能pin通 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 18:10 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 不是啊兄弟，你说的我都回答了我也觉得是dns的问题 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:58 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 而且我看csdoor出了我下周试试这个不过份吧 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:53 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 首先部署lobedatabase这台机器肯定是要通外网的呀，这个我么问题，我只是说内网的其他pc访问lobe又不需要通外网，只是借助lobe访问大模型，就是典型的cs架构啊兄弟 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:40 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 我这太内网服务器通外网的呀 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 17:35 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) 不我的域名都是内部的dns做的，不存在这个问题ipv6的问题 发自我的iPhone ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月22日 06:42 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题，可否帮忙看下，下面提供了具体的配置 (Issue #3852) @zhangleijun111 我发现了一个问题：你容器的网络的驱动程序是bridge吧？bridge默认是关闭ipv6的。你的域名所对应的ip是云服务器吗？如果不是的话应该没有公网v4 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 不是哥们？你到底进入容器nslookup过没？再说了你以为你这个域名不用开放到公网？大模型怎么读你minio里的文件？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 听不懂你什么意思 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 有没有一种可能，需要？至少logto需要。你到底进容器测过没，没测过你说得这么斩钉截铁？lobe、minio、logto必须能够互相通过域名访问对方，有一个访问不了都会有问题。你到底试过没？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 这语气怎么说得好像我求你测似的，我现在不是在帮你排查问题吗？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 所以这里有三个问题： 你有在本地dns服务器解析这个域名吗？ 你确认此dns服务器的ip了吗？ 你的容器的dns配置文件里指向了此dns服务器吗？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> 你确认你进入容器内“ping”通了？可是事实是，某个容器不支持ping命令，你知道吗？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> logto你也再试试进去连接lobe吧，一起测 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

我知道你应用无法创建，所以更应该确认三者之间的连通性啊。最好三者之间都能够互相联通，也就是6次连接都成功。

@lobehubbot
Copy link
Member

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

My logto cannot create an application. I haven’t tested the connection between mino and lobe yet, and it got stuck in the first step. Sent from my iPhone
…
------------------ Original email ------------------ Sender: Fang @ .> Sent time: 18:17, September 22, 2024 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @ .>, Mention @.> Topic: Re: [lobehub/lobe-chat] [Bug] I still want to ask about the problem of logto login. Can you help me check it out? The following is provided The specific configuration (Issue #3852) The logto container is sent from my iPhone... ------------------ Original email---------- ------- Sender: Bifang@.> Sent time: September 22, 2024 18:12 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @. > Topic: Re: [lobehub/lobe-chat] [Bug] I still want to ask about the issue of logto login. Can you help me check it out? The specific configuration is provided below (Issue #3852) Yes, I can pin it after doing it. Sent to my iPhone... ------------------Original email------------------Sender: Fang@ .> Sent time: 18:10 on September 22, 2024 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [ Bug] I still want to ask about the issue of logto login. Can you help me? The specific configuration is provided below (Issue #3852) No, brother, I have answered everything you said. I also think it is a dns problem. The issue is from my iPhone. … ------------------ Original email ------------------ Sender: Bifang@.> Sent time: September 22, 2024 17:58 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [Bug] I still want to Please ask about the problem of logto login. Can you help me check it out? The specific configuration is provided below (Issue #3852) and I saw that csdoor has it. I will try this next week. It is not too much. I sent it to my iPhone... ------- ---------- Original email ------------------ Sender: Bifang@.> Sent time: September 22, 2024 at 17:00 53 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [Bug] I still want to ask a question about logto login, is it possible? Please help, the specific configuration is provided below (Issue #3852) First of all, the machine to deploy lobedatabase must have access to the external network. This is my problem. I just mean that other PCs on the internal network do not need to access the external network to access lobe. Network, just use lobe to access large models, it is a typical CS architecture. Brother sent it to my iPhone... ------------------ Original email--------- --------- Sender: Bifang@.> Sent time: September 22, 2024 17:40 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @.> Topic: Re: [lobehub/lobe-chat] [Bug] I still want to ask about the problem of logto login. Can you help me? The specific configuration is provided below (Issue #3852) My intranet server is connected. From the Internet, sent from my iPhone ------------------ Original email ------------------ Sender: The other side @.> Sent time: September 22, 2024 17:35 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat ] [Bug] I still want to ask about the problem of logto login. Can you help me? The specific configuration is provided below (Issue #3852). No, my domain names are all made by internal dns. There is no such problem. IPv6 issues. My iPhone ------------------Original email------------------ Sender: Bifang@.> Send Time: September 22, 2024 06:42 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [Bug] Me I still want to ask about the logto login issue. Can you help me take a look? The specific configuration is provided below (Issue #3852) @zhangleijun111 I found a question: Is the network driver of your container a bridge? Bridge turns off ipv6 by default. Is the IP corresponding to your domain name a cloud server? If not, there should be no public network v4 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> Not a buddy? Have you ever entered the container nslookup? Besides, do you think your domain name doesn’t need to be opened to the public network? How does the big model read the files in your minio? — Reply to this email directly, view it on GitHub, or unsubscribe. . You are receiving this because you were mentioned.Message ID: @.> Is there a possibility, need? At least logto requires it. Have you ever tested it in a container? Are you so categorical about not testing it? Lobe, minio, and logto must be able to access each other through domain names. If one of them cannot be accessed, there will be problems. Have you tried it? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> Why does this sound like I am begging you to test it? I am not helping you troubleshoot now. Problem? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> So here are three questions: Do you have a local DNS server to resolve this domain name? Have you confirmed the ip of this dns server? Does your container's dns configuration file point to this dns server? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> Are you sure you can "ping" into the container? But the fact is that a certain container does not support the ping command, did you know? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> logtoYou can try connecting to lobe again and test it together — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.**>

I know that your application cannot be created, so you should confirm the connectivity between the three. It is best if all three can communicate with each other, that is, all 6 connections are successful.

@zhangleijun111
Copy link
Author

zhangleijun111 commented Sep 22, 2024 via email

@lobehubbot
Copy link
Member

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

Okay, let's check it out tomorrow.

Sent from my iPhone

------------------ Original email ------------------
Sender: Bifang @.>
Sent time: September 22, 2024 18:23
Recipient: lobehub/lobe-chat @.>
CC: zhangleijun111 @.>, Mention @.>
Topic: Re: [lobehub/lobe-chat] [Bug] I still want to ask about the issue of logto login. Can you help me check it out? The specific configuration is provided below (Issue #3852)

I can't create an application with logto. I haven't tested the connection between mino and lobe yet, and it got stuck in the first step. Sent from my iPhone
…
------------------ Original email ------------------ Sender: Bifang@.> Sent time: 2024 September 22, 18:17 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [Bug] I still want to ask Question: I have a problem with logto login. Can you help me? The specific configuration is provided below (Issue #3852) The logto container is sent from my iPhone... ------------------ Original email ------------------ Sender: Bifang@.> Sent time: 18:12, September 22, 2024 Recipient: lobehub/lobe-chat @ .> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [Bug] I still want to ask a question about logto login. Can you help me check it out? The specific configuration is provided below ( Issue #3852) Yes, I have done everything and can pin it to my iPhone... ------------------ Original email---------- ------- Sender: Bifang@.> Sent time: 18:10 on September 22, 2024 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @. > Topic: Re: [lobehub/lobe-chat] [Bug] I still want to ask about the issue of logto login. Can you help me check it out? The specific configuration is provided below (Issue #3852) No, brother, I have everything you said. Answered. I also think it is a DNS problem. Sent from my iPhone... ------------------ Original email---------------- -- Sender: Bifang@.> Sent time: September 22, 2024 17:58 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [Bug] I still want to ask about the issue of logto login. Can you help me? The specific configuration is provided below (Issue #3852) and I see that csdoor is out. I will try this next week. Send it to my iPhone... ------------------Original email------------------Sender: Bifang@ .> Sent time: 17:53 on September 22, 2024 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [ Bug] I still want to ask about the problem of logto login. Can you help me? The specific configuration is provided below (Issue #3852). First of all, the machine where lobedatabase is deployed must have access to the external network. This is my problem. I just It is said that other PCs on the intranet do not need to access the external network to access the Lobe. They only use the Lobe to access the large model. It is a typical CS architecture. Brother sent this to my iPhone...---------------- --Original email------------------ Sender: Bifang@.> Sent time: 17:40, September 22, 2024 Recipient: lobehub/lobe- chat @.> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [Bug] I still want to ask a question about logto login. Can you help me? The specific instructions are provided below. Configuration (Issue #3852) My internal network server is connected to the external network. Sent from my iPhone ------------------ Original email--------- --------- Sender: Bifang@.> Sent time: September 22, 2024 17:35 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @.> Topic: Re: [lobehub/lobe-chat] [Bug] I still want to ask about the problem of logto login. Can you help me? The specific configuration is provided below (Issue #3852) No, my domain names are all internal DNS is done, there is no such problem. The problem of ipv6 is sent from my iPhone ------------------ Original email-------------- ---- Sender: Bifang@.> Sent time: September 22, 2024 06:42 Recipient: lobehub/lobe-chat @.> Cc: zhangleijun111 @.>, Mention @.> Subject: Re: [lobehub/lobe-chat] [Bug] I still want to ask about the problem of logto login. Can you help me? The specific configuration is provided below (Issue #3852) @zhangleijun111 I found a problem: the network of your container The driver is bridge, right? Bridge turns off ipv6 by default. Is the IP corresponding to your domain name a cloud server? If not, there should be no public network v4 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> Not a buddy? Have you ever entered the container nslookup? Besides, do you think your domain name doesn’t need to be opened to the public network? How does the big model read the files in your minio? — Reply to this email directly, view it on GitHub, or unsubscribe. . You are receiving this because you were mentioned.Message ID: @.> Is there a possibility, need? At least logto requires it. Have you ever tested it in a container? You are so categorical in saying that you have not tested it? Lobe, minio, and logto must be able to access each other through domain names. If one of them cannot be accessed, there will be problems. Have you tried it? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> Why does this sound like I am begging you to test it? I am not helping you troubleshoot now. Problem? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> So here are three questions: Do you have a local DNS server to resolve this domain name? Have you confirmed the ip of this dns server? Does your container's dns configuration file point to this dns server? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> Are you sure you can "ping" into the container? But the fact is that a certain container does not support the ping command, did you know? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> logtoYou can try connecting to lobe again and test it together — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

I know that your application cannot be created, so you should confirm the connectivity between the three. It is best if all three can communicate with each other, that is, all 6 connections are successful.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@BiFangKNT
Copy link
Contributor

BiFangKNT commented Sep 22, 2024 •
edited
Loading

？请确认该环境是 docker swarm 集群还是单机 docker 如果是集群 请使用docker service ls

我是用dockercompose 部署的呀，单机都没好怎么会用swarm，我觉得我还是logto这里有点有问题

但是你的 logto 的容器已经停止运行了 你能否使用代码块 在不改变排版的情况下把日志发出来？

你可否教学一下使用代码块 在不改变排版的情况下把日志发出来如何这样操作？？？？？

选中你要显示的代码块，点击这个
image
显示效果：
code

@lobehubbot
Copy link
Member

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

? Please confirm whether the environment is a docker swarm cluster or a stand-alone docker. If it is a cluster, please use docker service ls

I deployed it using dockercompose. How can I use swarm if the single machine is not good? I think there is something wrong with logto.

But your logto container has stopped running. Can you use code blocks to send the log out without changing the layout?

Can you teach me how to use code blocks to send out logs without changing the layout? ? ? ? ?

Select the code block you want to display and click this
image
code

@BiFangKNT
Copy link
Contributor

BiFangKNT commented Sep 22, 2024 •
edited
Loading

@zhangleijun111 你之前发的配置的可读性太差了，麻烦到时候把你现在的docker-compose.yml配置文件、lobe的.env文件及nginx内做的反代和dns解析配置用上面提到的代码块的形式重新发一次

另外听你之前的描述，你似乎把反代当做dns解析用了，你并没有在dns服务器上做域名解析，是吗？这里我必须强调一下：

nginx不是dns服务器，反代不能当dns解析用。

如果你在 Nginx 中配置了反向代理规则，比如：

server {
    listen 80;
    server_name example.local;

    location / {
        proxy_pass http://192.168.1.100;
    }
}

这种配置只是告诉 Nginx 如何将 example.local 的请求转发到 192.168.1.100。但是，局域网内其他服务（如客户端浏览器、其他服务器）要能够访问 example.local，它们需要能够通过 DNS 解析到该域名。

解决方案

要让局域网内的其他服务能够解析 example.local 这个域名，可以考虑以下几种方法：

  1. 修改客户端的 hosts 文件：

在需要解析 example.local 的每台客户端的 hosts 文件（通常是 /etc/hosts ）中添加：
192.168.1.100 example.local
这种方法适用于少量客户端。

  1. 搭建局域网 DNS 服务器：

在局域网内部搭建一个 DNS 服务器（如 BIND、dnsmasq 等），然后在 DNS 服务器中配置 example.local 的解析记录。
example.local IN A 192.168.1.100
然后将局域网内所有客户端的 DNS 设置指向该内部 DNS 服务器。

  1. 通过 DHCP 分发自定义 DNS 设置：

如果局域网使用 DHCP 分配 IP 地址，可以通过 DHCP 服务器分发自定义的 DNS 设置，让所有客户端都使用该内部 DNS 服务器。

而针对现在你的这个场景，我推荐使用第二种方法，并且是借助docker内置dns功能而不是另外搭建dns服务器。

Docker Compose 配置示例

假设你有 4 个服务：Nginx、服务A、服务B 和 服务C。服务A、B、C 需要通过域名互相访问，但这些域名不需要对外部网络可见。

你可以通过如下 Docker Compose 文件实现这个需求：

version: '3.8'

services:
  nginx:
    image: nginx:latest
    container_name: nginx
    ports:
      - "80:80"
    networks:
      - my_network
    depends_on:
      - service_a
      - service_b
      - service_c
    extra_hosts:
      - "service_a.local:service_a"
      - "service_b.local:service_b"
      - "service_c.local:service_c"

  service_a:
    image: my_service_a_image
    container_name: service_a
    networks:
      - my_network
    extra_hosts:
      - "service_b.local:service_b"
      - "service_c.local:service_c"

  service_b:
    image: my_service_b_image
    container_name: service_b
    networks:
      - my_network
    extra_hosts:
      - "service_a.local:service_a"
      - "service_c.local:service_c"

  service_c:
    image: my_service_c_image
    container_name: service_c
    networks:
      - my_network
    extra_hosts:
      - "service_a.local:service_a"
      - "service_b.local:service_b"

networks:
  my_network:
    driver: bridge

如果你需要打开ipv6功能，除了更改bridge默认设置外，还可以在此compose文件内独立设置：

networks:
  my_network:
    driver: bridge
    enable_ipv6: true
    ipam:
      driver: default
      config:
        - subnet: "fd00:good:lobe::/64"

注意：在做完以上配置修改后，你需要删除compose并重新构建才能生效

@lobehubbot
Copy link
Member

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

@zhangleijun111 The readability of the configuration you posted before is too poor. Please upload your current docker-compose.yml configuration file, lobe's .env file, and the anti-generation and dns resolution configuration in nginx. Repost it in the form of the code block mentioned above

In addition, from your previous description, it seems that you used reverse generation as DNS resolution. You did not perform domain name resolution on the DNS server, right? I must emphasize here:

_nginx is not a dns server, and reverse generation cannot be used for dns resolution. _

If you configure reverse proxy rules in Nginx, such as:

server {
    listen 80;
    server_name example.local;

    location/{
        proxy_pass http://192.168.1.100;
    }
}

This configuration just tells Nginx how to forward requests for example.local to 192.168.1.100. However, for other services within the LAN (such as client browsers, other servers) to be able to access example.local, they need to be able to resolve the domain name through DNS.

Solution

To allow other services in the LAN to resolve the domain name example.local, you can consider the following methods:

  1. Modify the client’s hosts file:

In the hosts file (usually /etc/hosts ) of each client that needs to resolve example.local, add:
192.168.1.100 example.local
This approach works well for a small number of clients.

  1. Set up a LAN DNS server:

Set up a DNS server (such as BIND, dnsmasq, etc.) within the LAN, and then configure the resolution record of example.local in the DNS server.
example.local IN A 192.168.1.100
Then point the DNS settings of all clients on the LAN to this internal DNS server.

  1. Distribute custom DNS settings via DHCP:

If your LAN uses DHCP to assign IP addresses, you can distribute custom DNS settings through a DHCP server so that all clients use that internal DNS server.

**For your current scenario, I recommend using the second method, and using docker's built-in dns function instead of building another dns server. **

Docker Compose configuration example

Suppose you have 4 services: Nginx, Service A, Service B and Service C. Services A, B, and C need to access each other through domain names, but these domain names do not need to be visible to the external network.

You can achieve this requirement through the following Docker Compose file:

version: '3'
services:
  nginx:
    image: nginx:latest
    container_name: nginx
    ports:
      - "80:80"
    networks:
      - my_network
    depends_on:
      - service_a
      - service_b
      - service_c

  service_a:
    image: my_service_a_image
    container_name: service_a
    networks:
      -my_network
    environment:
      - SERVICE_HOSTNAME=service_a.local

  service_b:
    image: my_service_b_image
    container_name: service_b
    networks:
      - my_network
    environment:
      - SERVICE_HOSTNAME=service_b.local

  service_c:
    image: my_service_c_image
    container_name: service_c
    networks:
      - my_network
    environment:
      - SERVICE_HOSTNAME=service_c.local

networks:
  my_network:
    driver: bridge

If you need to turn on the ipv6 function, in addition to changing the bridge default settings, you can also set it independently in this compose file:

networks:
  my_network:
    driver:bridge
    enable_ipv6: true
    ipam:
      driver:default
      config:
        - subnet: "fd00:good:lobe::/64"

@BiFangKNT
Copy link
Contributor

BiFangKNT commented Sep 22, 2024 •
edited
Loading

并且我这个方案能完全实现的前提是lobe-database本身不需要在公网上开放域名，或者你在公共dns上做了解析。我目前还不清楚前者是否为真，我倾向于认为其为真。

@lobehubbot
Copy link
Member

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

And the premise that my solution can be fully realized is that lobe-database itself does not need to open the domain name on the public Internet, or you have to perform resolution on the public dns. It's unclear to me whether the former is true.

@BiFangKNT
Copy link
Contributor

@zhangleijun111 另外别的服务我不清楚，但是logto对ssl很严格，它不承认自签名证书，需要CA证书，而外部CA不会给你这个不在外部dns上解析的域名颁发证书的。至于内部CA，，我不太清楚，下面是我搜到的示例，你可以试一下：

1. Smallstep CA 简介

Smallstep CA 提供一个非常方便的方式来生成内部证书，它可以通过 Docker 部署，并能与其他服务进行集成，实现 HTTPS 支持。以下是如何将 Smallstep CA 与 Nginx 反向代理集成，以实现 HTTPS 通信的完整 Docker Compose 例子。

2. Docker Compose 文件（包含内部 CA）

version: '3.8'

services:
  step-ca:
    image: smallstep/step-ca:latest
    container_name: step-ca
    environment:
      - DOCKER_NETWORK=my_network
    volumes:
      - ./ca-data:/home/step
    networks:
      - my_network
    ports:
      - "9000:9000" # CA Web UI
    command: ["step-ca", "--password-file=/home/step/secrets/password"]

  nginx:
    image: nginx:latest
    container_name: nginx
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf
      - ./ssl:/etc/nginx/ssl
    networks:
      - my_network
    depends_on:
      - step-ca
      - service_a
      - service_b
      - service_c

  service_a:
    image: my_service_a_image
    container_name: service_a
    networks:
      - my_network
    extra_hosts:
      - "service_a.local:service_a"
      - "service_b.local:service_b"
      - "service_c.local:service_c"

  service_b:
    image: my_service_b_image
    container_name: service_b
    networks:
      - my_network
    extra_hosts:
      - "service_a.local:service_a"
      - "service_c.local:service_c"

  service_c:
    image: my_service_c_image
    container_name: service_c
    networks:
      - my_network
    extra_hosts:
      - "service_a.local:service_a"
      - "service_b.local:service_b"

networks:
  my_network:
    driver: bridge

3. Step CA 组件解析

  • step-ca 服务：Smallstep CA 是用于内部证书颁发的。它的 Docker 镜像为 smallstep/step-ca，用于内部管理和自动化签发证书。
  • volumes：CA 的配置和密钥被持久化存储在 ./ca-data 目录中，防止每次重启 CA 时丢失密钥。
  • ports：CA 的 Web UI 通过端口 9000 暴露，可以在浏览器中访问以管理和查看颁发的证书。

4. 生成和签发证书

使用 Smallstep CA 来为你的服务（例如 service_a、service_b）签发 SSL 证书。

初始化 Step CA

第一次运行 Step CA 时，需要初始化它：

docker exec -it step-ca step ca init --name "Internal CA" \
  --dns "step-ca" --address ":9000" \
  --provisioner "[email protected]"

这将初始化 CA，并生成初始的 CA 根证书和密钥。CA 的配置和数据将保存在 ./ca-data 目录下。

颁发证书

通过以下命令为每个服务（如 service_a）生成证书：

docker exec -it step-ca step ca certificate "service_a.local" \
  ./ssl/service_a.local.crt ./ssl/service_a.local.key

这将使用内部 CA 为 service_a.local 域名生成证书，并将其保存在 ./ssl 目录下，Nginx 会使用这些证书为 HTTPS 反向代理提供服务。

5. Nginx 配置

Nginx 的 HTTPS 配置将引用 Smallstep CA 签发的证书，类似如下：

server {
    listen 443 ssl;
    server_name service_a.local;

    ssl_certificate /etc/nginx/ssl/service_a.local.crt;
    ssl_certificate_key /etc/nginx/ssl/service_a.local.key;

    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers HIGH:!aNULL:!MD5;

    location / {
        proxy_pass http://service_a;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;
    }
}

server {
    listen 80;
    server_name service_a.local;

    # 将 HTTP 请求重定向到 HTTPS
    return 301 https://$host$request_uri;
}

6. Docker Compose 完整流程

  1. Step CA 初始化：当 Docker Compose 启动时，Step CA 会作为内部 CA 服务运行。
  2. 签发证书：使用 Smallstep CA 签发每个服务的 SSL 证书，并将这些证书保存在 Nginx 容器的挂载目录中（./ssl）。
  3. Nginx 使用 SSL 证书：Nginx 使用这些证书来处理 HTTPS 请求，将 HTTPS 请求代理到相应的服务（例如 service_a）。
  4. HTTP 重定向到 HTTPS：Nginx 同时监听 80 端口，将所有 HTTP 请求重定向到 HTTPS。

上面一切的前提是，lobe-database本身的域名不需要暴露到公网中。但是模型读取你的图片和文件，是需要访问你的域名的。

@lobehubbot
Copy link
Member

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

@zhangleijun111 I don’t know about other services, but logto is very strict about SSL. It does not recognize self-signed certificates and requires a CA certificate. The external CA will not issue a certificate to you for a domain name that is not resolved on the external dns. As for the internal CA, I'm not sure. Here are the examples I found. You can try it:

1. Smallstep CA Introduction

Smallstep CA provides a very convenient way to generate internal certificates, which can be deployed through Docker and integrated with other services to implement HTTPS support. Here is a complete Docker Compose example of how to integrate Smallstep CA with Nginx reverse proxy for HTTPS communication.

2. Docker Compose file (contains internal CA)

version: '3.8'

services:
  step-ca:
    image: smallstep/step-ca:latest
    container_name: step-ca
    environment:
      - DOCKER_NETWORK=my_network
    volumes:
      - ./ca-data:/home/step
    networks:
      - my_network
    ports:
      - "9000:9000" # CA Web UI
    command: ["step-ca", "--password-file=/home/step/secrets/password"]

  nginx:
    image: nginx:latest
    container_name: nginx
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf
      - ./ssl:/etc/nginx/ssl
    networks:
      - my_network
    depends_on:
      -step-ca
      - service_a
      - service_b
      - service_c

  service_a:
    image: my_service_a_image
    container_name: service_a
    networks:
      - my_network
    extra_hosts:
      - "service_a.local:service_a"
      - "service_b.local:service_b"
      - "service_c.local:service_c"

  service_b:
    image: my_service_b_image
    container_name: service_b
    networks:
      - my_network
    extra_hosts:
      - "service_a.local:service_a"
      - "service_c.local:service_c"

  service_c:
    image: my_service_c_image
    container_name: service_c
    networks:
      - my_network
    extra_hosts:
      - "service_a.local:service_a"
      - "service_b.local:service_b"

networks:
  my_network:
    driver:bridge

3. Step CA component analysis

  • step-ca service: Smallstep CA is used for internal certificate issuance. Its Docker image is smallstep/step-ca, which is used for internal management and automated certificate issuance.
  • volumes: CA configuration and keys are persistently stored in the ./ca-data directory to prevent losing keys every time the CA is restarted.
  • ports: The CA's web UI is exposed via port 9000 and can be accessed in a browser to manage and view issued certificates.

4. Generate and issue certificate

Use Smallstep CA to issue SSL certificates for your services (e.g. service_a, service_b).

Initialize Step CA

The first time you run Step CA, you need to initialize it:

docker exec -it step-ca step ca init --name "Internal CA" \
  --dns "step-ca" --address ":9000" \
  --provisioner "[email protected]"

This will initialize the CA and generate the initial CA root certificate and keys. The CA configuration and data will be saved in the ./ca-data directory.

####Issue certificate

Generate certificates for each service (such as service_a) with the following command:

docker exec -it step-ca step ca certificate "service_a.local" \
  ./ssl/service_a.local.crt ./ssl/service_a.local.key

This will generate a certificate for the service_a.local domain name using an internal CA and save it in the ./ssl directory, which Nginx will use to serve the HTTPS reverse proxy.

5. Nginx configuration

Nginx's HTTPS configuration will reference the certificate issued by Smallstep CA, similar to the following:

server {
    listen 443 ssl;
    server_name service_a.local;

    ssl_certificate /etc/nginx/ssl/service_a.local.crt;
    ssl_certificate_key /etc/nginx/ssl/service_a.local.key;

    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers HIGH:!aNULL:!MD5;

    location/{
        proxy_pass http://service_a;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;
    }
}

server {
    listen 80;
    server_name service_a.local;

    # Redirect HTTP requests to HTTPS
    return 301 https://$host$request_uri;
}

6. Docker Compose complete process

  1. Step CA initialization: When Docker Compose starts, Step CA runs as an internal CA service.
  2. Issue certificate: Use Smallstep CA to issue SSL certificates for each service, and save these certificates in the mounting directory of the Nginx container (./ssl).
  3. Nginx uses SSL certificates: Nginx uses these certificates to handle HTTPS requests and proxy HTTPS requests to the corresponding service (such as service_a).
  4. HTTP redirect to HTTPS: Nginx also listens to port 80 and redirects all HTTP requests to HTTPS.

_The premise of all the above is that the domain name of lobe-database itself does not need to be exposed to the public network. But the model needs to access your domain name to read your images and files. _

@lobehub lobehub locked and limited conversation to collaborators Sep 30, 2024
@arvinxx arvinxx converted this issue into discussion #4221 Sep 30, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees
No one assigned
Labels
🐛 Bug Something isn't working | 缺陷
Projects
Lobe Chat Routine
Archived in project
Milestone
No milestone
Development

No branches or pull requests
7 participants
@KingDoum @binaryYuki @BiFangKNT @lobehubbot @baihuyan @okidoki2me @zhangleijun111