Next auth use Logto provider fail

[fanyinghao]

📦 Platform

Self hosting Docker

📦 Deploymenet mode

server db(lobe-chat-database image)

📌 Version

1.77.17

💻 Operating System

Ubuntu

🌐 Browser

Chrome

🐛 Bug Description

使用宝塔部署镜像 lobehub/lobe-chat-database:latest
next auth配置 自定义的logto
环境变量：
- APP_URL=https://lobe.domain.com
- NEXT_PUBLIC_ENABLE_NEXT_AUTH=1
- NEXTAUTH_URL=https://lobe.domain.com/api/auth
- DATABASE_URL=postgresql://:5432/lobechat
- KEY_VAULTS_SECRET=
- NEXT_AUTH_SECRET=
- NEXT_AUTH_SSO_PROVIDERS=logto
- AUTH_LOGTO_ID=
- AUTH_LOGTO_SECRET=
- AUTH_LOGTO_ISSUER=https://sso.domain.com/oidc
- LOGTO_WEBHOOK_SIGNING_KEY=
- S3_ACCESS_KEY_ID=
- S3_SECRET_ACCESS_KEY=
- S3_ENDPOINT=https://
- S3_BUCKET=lobe-chat
- S3_PUBLIC_DOMAIN=https://
- PORT=3210

错误日志：
�[31m[auth][error]�[0m TypeError: fetch failed
at node:internal/deps/undici/undici:13502:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async at (/app/.next/server/chunks/34587.js:368:49370)
at async an (/app/.next/server/chunks/34587.js:368:52244)
at async as (/app/.next/server/chunks/34587.js:368:54886)
at async al (/app/.next/server/chunks/34587.js:368:59042)
at async to.do (/app/node_modules/.pnpm/next@15.2.3_@babel+core@7.26.10_@opentelemetry+api@1.9.0_@playwright+test@1.51.1_react-dom@19_y7h2nyx2k4fnnufqoqdsdv2mxi/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:18:18605)
at async to.handle (/app/node_modules/.pnpm/next@15.2.3_@babel+core@7.26.10_@opentelemetry+api@1.9.0_@playwright+test@1.51.1_react-dom@19_y7h2nyx2k4fnnufqoqdsdv2mxi/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:18:23632)
at async doRender (/app/node_modules/.pnpm/next@15.2.3_@babel+core@7.26.10_@opentelemetry+api@1.9.0_@playwright+test@1.51.1_react-dom@19_y7h2nyx2k4fnnufqoqdsdv2mxi/node_modules/next/dist/server/base-server.js:1513:42)
at async NextNodeServer.renderToResponseWithComponentsImpl (/app/node_modules/.pnpm/next@15.2.3_@babel+core@7.26.10_@opentelemetry+api@1.9.0_@playwright+test@1.51.1_react-dom@19_y7h2nyx2k4fnnufqoqdsdv2mxi/node_modules/next/dist/server/base-server.js:1915:28)

📷 Recurrence Steps

No response

🚦 Expected Behavior

正常使用logto登录

📝 Additional Information

No response

[lobehubbot]

👀 @fanyinghao

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

[dosubot[bot]]

你好，@fanyinghao！我是一个可以帮助你解决bug、回答问题和成为贡献者的机器人。在你等待人类维护者的同时，我会在这里帮助你！

I found a similar discussion that might be relevant to your issue. In the thread "请教一下lobechat本地部署database版本使用logto登录问题" ^[1], the problem was resolved by bypassing SSL/TLS certificate verification due to issues with local certificates. You can try setting the environment variable NODE_TLS_REJECT_UNAUTHORIZED=0 to bypass certificate verification.

Regarding the 'fetch failed' error, it commonly occurs when LobeChat cannot access the authentication service. Ensure your authentication service is running properly and that LobeChat's network can reach it. You can use the curl command within the LobeChat container to test access to your authentication service at https://sso.domain.com/.well-known/openid-configuration. If it returns JSON formatted data, your authentication service is functioning correctly ^[2].

To continue talking to Dosu, mention @dosu.

---

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

[arvinxx]

fetch failed 说明连通性有问题，需要你检查下和 logto 的连接

[fanyinghao]

@arvinxx 确实是网络问题，logto那边配置的ssl问题。提个建议，错误日志可以提供详细的内容，这样能大概也能看出问题了。再次谢谢！