Closed zhangleijun111 closed 1 month ago
👀 @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。我们会尽快调查此事,并尽快回复您。 请确保您已经提供了尽可能多的背景信息。
I found some similar discussions and issues that might help with your Logto login problem:
--ignore-certificate-errors --unsafely-treat-insecure-origin-as-secure=http://192.168.31.11:3002
To troubleshoot your issue, follow these steps:
Check Docker Logs:
docker logs -f lobe-logto
docker logs -f lobe-database
docker logs -f lobe-minio
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
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;
}
}
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
Restart Services: After making any changes, restart the Docker services to apply the new configurations:
docker compose up -d
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.
📦 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
📝 Additional Information
No response
logto的DB_URL
改成@lobe-postgres
,因为你是在同一个compose里的,所以不能用服务名称而应该用容器名称
📦 环境
码头工人
📌 版本
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; }
}
🚦 预期行为
📝 其他信息
无响应
logto的改成,因为你是在同一个compose里的,所以不能用服务名称而应该用容器名称
DB_URL``@lobe-postgres
DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@lobe-postgres:5432/logto 这样是吗,databaseurl 需要修改吗
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= DATABASEURL=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
📝 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?
📦 环境
码头工人
📌 版本
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; }
}
🚦 预期行为
📝 其他信息
无响应
logto的改成,因为你是在同一个compose里的,所以不能用服务名称而应该用容器名称
DB_URL
@lobe-postgres ``DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@lobe-postgres:5432/logto 这样是吗,databaseurl 需要修改吗
要的
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
📝 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
📦 环境
码头工人
📌 版本
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; }
}
🚦 预期行为
📝 其他信息
无响应
logto的改成,因为你是在同一个compose里的,所以不能用服务名称而应该用容器名称
DB_URL
@lobe-postgres ``DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@lobe-postgres:5432/logto 这样是吗,databaseurl 需要修改吗
听说最新版本修复了这个bug,你试试
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
📝 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
上周试过貌似不行,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: @.***>
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_AUTHSECRET=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: @.***>
上周试过貌似不行,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: @.***>
今天更新了两版啊
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
docker-compose是吗
发自我的iPhone
------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月9日 18:33 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题,可否帮忙看下,下面提供了具体的配置 (Issue #3852)
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)
docker-compose是吗 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月9日 18:33 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题,可否帮忙看下,下面提供了具体的配置 (Issue #3852)
哦不对,定睛一看是六版
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.
作者
昨天的版本是要这么改的,但是最新版本改了网络相关的,现在这么写不行了,我还在琢磨 #3814
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
好的,那我nginx这段还要修改吗
发自我的iPhone
------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月9日 19:10 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题,可否帮忙看下,下面提供了具体的配置 (Issue #3852)
兄弟交流交流 ,我跟你一样的情况啊
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.
好的,那我nginx这段还要修改吗 发自我的iPhone … ------------------ 原始邮件 ------------------ 发件人: 彼方 @.> 发送时间: 2024年9月9日 19:10 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题,可否帮忙看下,下面提供了具体的配置 (Issue #3852)
目前改用cloudflare了,logto感觉问题很多,官方都打算改成别的方案了 #3814
兄弟交流交流 ,我跟你一样的情况啊
同上
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
cloudflare logto登录后台3002那个端口的后台就会出现Internal server error. 容器日志显示域名无法解析,3001端口对应的那个域名就是404
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.
作者
昨天的版本是要这么改的,但是最新版本改了网络相关的,现在这么写不行了,我还在琢磨 #3814
我试试看最新版本不是用logto了是吗
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?
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 has changed network-related things. Now it doesn't work like this. I'm still thinking about it #3814
Hahaha I know how to do it, I've done it
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Author
Yesterday’s version wanted to change it like this, but the latest version changed network-related things. Now it doesn’t work like this. I’m still thinking about it #3814
Hahaha I know how to do it, I've done it
This is a dns problem in docker
我用的caddy 代理的 ,只能代理 4443这种端口,你是咋直接访问 443端口的,很牛。
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
The caddy proxy I use can only proxy port 4443. How do you directly access port 443? It's awesome.
怎么改呢
发自我的iPhone
------------------ 原始邮件 ------------------ 发件人: baihuyan @.> 发送时间: 2024年9月10日 13:41 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题,可否帮忙看下,下面提供了具体的配置 (Issue #3852)
作者
昨天的版本是要这么改的,但是最新版本改了网络相关的,现在这么写不行了,我还在琢磨 #3814
我已修改了url的名字还是报图中的这个错误
哈哈哈 我知道怎么弄了,我弄好了
你这个是docker里面的dns问题
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
我应该如何修改
发自我的iPhone
------------------ 原始邮件 ------------------ 发件人: baihuyan @.> 发送时间: 2024年9月10日 13:41 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题,可否帮忙看下,下面提供了具体的配置 (Issue #3852)
作者
昨天的版本是要这么改的,但是最新版本改了网络相关的,现在这么写不行了,我还在琢磨 #3814
我已修改了url的名字还是报图中的这个错误
哈哈哈 我知道怎么弄了,我弄好了
你这个是docker里面的dns问题
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
https://lobe-s3-ui.msftconnecttest.com/ 这种 你是能直接访问么?(这种 我都打不开你的) 我的因为是家里的迷你主机,443端口被封闭了,我使用4443端口去代理的。
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
https://lobe-s3-ui.msftconnecttest.com/ Can you access this directly? (I can't even open yours.) Because mine is a mini host at home, port 443 is blocked. I use port 4443 to proxy.
我写了nginx
发自我的iPhone
------------------ 原始邮件 ------------------ 发件人: King @.> 发送时间: 2024年9月10日 14:15 收件人: lobehub/lobe-chat @.> 抄送: zhangleijun111 @.>, Mention @.> 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题,可否帮忙看下,下面提供了具体的配置 (Issue #3852)
大家好,用的是 #3814 ,第一个方案 三个解决方案:
本地创建 或本机 , 其中内容仅包含 字段,并映射进容器中resolv.conf/etc/resolv.conf
nameserver
nameserver 223.5.5.5
nameserver 8.8.8.8
nameserver 192.168.0.1 更改 Docker 默认行为,修改 配置文件后重启 Docker 进程,如:/etc/docker/daemon.json``sudo systemctl restart docker { "dns-opts":[ "ndots:1" ] } 从容器镜像下手,每次启动时执行 来移除此字段sed -i '/ndots:0/d' /etc/resolv.conf 我的文件resolv.conf,内容是
nameserver 127.0.0.11
nameserver 192.168.0.1
nameserver 223.5.5.5
nameserver 8.8.8.8 搞定用这个方法
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Hello everyone, I am using #3814, the first solution and three solutions:
Created locally or natively, the content only contains the field and is mapped into the container resolv.conf/etc/resolv.conf
nameserver
nameserver 223.5.5.5
nameserver 8.8.8.8
nameserver 192.168.0.1 Change the default behavior of Docker and restart the Docker process after modifying the configuration file, such as: /etc/docker/daemon.json``sudo systemctl restart docker { "dns-opts":[ "ndots:1" ] } Start with the container image and execute sed -i '/ndots:0/d' /etc/resolv.conf every time you start to remove this field. My file resolv.conf, the content is
nameserver 127.0.0.11
nameserver 192.168.0.1
nameserver 223.5.5.5
nameserver 8.8.8.8 Use this method to get it done
就是现在会出现登录注册的时候,需要返回重新加载两次,会让登录用户产生困扰,你们能解决这个问题么
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
It is now that when logging in and registering, you need to go back and reload twice, which will cause trouble to logged in users. Can you solve this problem?
你也是用 nginx 代理的数据么?
------------------ 原始邮件 ------------------ 发件人: "lobehub/lobe-chat" @.>; 发送时间: 2024年9月10日(星期二) 下午2:32 @.>; @.**@.>; 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题,可否帮忙看下,下面提供了具体的配置 (Issue #3852)
就是现在会出现登录注册的时候,需要返回重新加载两次,会让登录用户产生困扰,你们能解决这个问题么
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
你也是用 nginx 代理的数据么? … ------------------ 原始邮件 ------------------ 发件人: "lobehub/lobe-chat" @.>; 发送时间: 2024年9月10日(星期二) 下午2:32 @.>; @.**@.>; 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题,可否帮忙看下,下面提供了具体的配置 (Issue #3852) 就是现在会出现登录注册的时候,需要返回重新加载两次,会让登录用户产生困扰,你们能解决这个问题么 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
用的是nginx 没问题
你也是用 nginx 代理的数据么? … ------------------ 原始邮件 ------------------ 发件人: "lobehub/lobe-chat" @.>; 发送时间: 2024年9月10日(星期二) 下午2:32 @.>; @.**@.>; 主题: Re: [lobehub/lobe-chat] [Bug] 我还是想请问题logto登录的问题,可否帮忙看下,下面提供了具体的配置 (Issue #3852) 就是现在会出现登录注册的时候,需要返回重新加载两次,会让登录用户产生困扰,你们能解决这个问题么 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
是啊
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Now when logging in and registering, you need to go back and reload twice, which will cause trouble for logged in users. Can you solve this problem?
I've done the mapping but it still doesn't seem to be working, bro?
📦 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:
'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:
'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:
'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:
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;
}
server { listen 443 ssl; server_name lobe-auth-ui.msftconnecttest.com;
}
🚦 Expected Behavior
报错截图
📝 Additional Information
No response