[Bug] 本地Windows部署，登录认证回调报错 #5518

muwingueaiguei · 2025-01-20T09:48:19Z

muwingueaiguei
Jan 20, 2025

📦 部署环境

Other

📌 软件版本

1.47.5

💻 系统环境

Windows

🌐 浏览器

Chrome

🐛 问题描述

我在本地vscode中以server方式正常启动项目

当使用casdoor登录时，回调报错

1、输入登录用户密码后，直接跳转到 https://192.168.1.134:3010/api/auth/error
2、后端报错如下：
[auth][error] AdapterError: Read more at https://errors.authjs.dev#adaptererror at acc.<computed> (E:\17_Vue_React\lobe-chat-main\.next\server\chunks\node_modules__pnpm_3d15eb._.js:1366:31) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Module.callback (E:\17_Vue_React\lobe-chat-main\.next\server\chunks\node_modules__pnpm_3d15eb._.js:3806:33) at async AuthInternal (E:\17_Vue_React\lobe-chat-main\.next\server\chunks\node_modules__pnpm_3d15eb._.js:4859:24) at async Auth (E:\17_Vue_React\lobe-chat-main\.next\server\chunks\node_modules__pnpm_3d15eb._.js:5120:34) at async AppRouteRouteModule.do (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\compiled\next-server\app-route.runtime.dev.js:10:32847) at async AppRouteRouteModule.handle (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\compiled\next-server\app-route.runtime.dev.js:10:39868) at async doRender (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\base-server.js:1452:42) at async responseGenerator (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\base-server.js:1822:28) at async DevServer.renderToResponseWithComponentsImpl (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\base-server.js:1832:28) at async DevServer.renderPageComponent (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\base-server.js:2259:24) at async DevServer.renderToResponseImpl (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\base-server.js:2297:32) at async DevServer.pipeImpl (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\base-server.js:959:25) at async NextNodeServer.handleCatchallRenderRequest (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\next-server.js:281:17) at async DevServer.handleRequestImpl (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\base-server.js:853:17) at async E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\dev\next-dev-server.js:371:20 at async Span.traceAsyncFn (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\trace\trace.js:153:20) at async DevServer.handleRequest (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\dev\next-dev-server.js:368:24) at async invokeRender (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\lib\router-server.js:230:21) at async handleRequest (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\lib\router-server.js:408:24) at async requestHandlerImpl (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\lib\router-server.js:432:13) at async Server.requestListener (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\lib\start-server.js:146:13) [auth][error] AdapterError: Read more at https://errors.authjs.dev#adaptererror at acc.<computed> (E:\17_Vue_React\lobe-chat-main\.next\server\chunks\node_modules__pnpm_3d15eb._.js:1366:31) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Module.callback (E:\17_Vue_React\lobe-chat-main\.next\server\chunks\node_modules__pnpm_3d15eb._.js:3806:33) at async AuthInternal (E:\17_Vue_React\lobe-chat-main\.next\server\chunks\node_modules__pnpm_3d15eb._.js:4859:24) at async Auth (E:\17_Vue_React\lobe-chat-main\.next\server\chunks\node_modules__pnpm_3d15eb._.js:5120:34) at async AppRouteRouteModule.do (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\compiled\next-server\app-route.runtime.dev.js:10:32847) at async AppRouteRouteModule.handle (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\compiled\next-server\app-route.runtime.dev.js:10:39868) at async doRender (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\base-server.js:1452:42) at async responseGenerator (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\base-server.js:1822:28) at async DevServer.renderToResponseWithComponentsImpl (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\base-server.js:1832:28) at async DevServer.renderPageComponent (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\base-server.js:2259:24) at async DevServer.renderToResponseImpl (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\base-server.js:2297:32) at async DevServer.pipeImpl (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\base-server.js:959:25) at async NextNodeServer.handleCatchallRenderRequest (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\next-server.js:281:17) at async DevServer.handleRequestImpl (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\base-server.js:853:17) at async E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\dev\next-dev-server.js:371:20 at async Span.traceAsyncFn (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\trace\trace.js:153:20) at async DevServer.handleRequest (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\dev\next-dev-server.js:368:24) at async invokeRender (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\lib\router-server.js:230:21) at async handleRequest (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\lib\router-server.js:408:24) at async requestHandlerImpl (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\lib\router-server.js:432:13) at async Server.requestListener (E:\17_Vue_React\lobe-chat-main\node_modules\.pnpm\next@15.1.5_@babel+core@7.26.0_@opentelemetry+api@1.9.0_@playwright+test@1.49.1_react-dom@19._gjluzxyayy7ntgi7rjyylzka3q\node_modules\next\dist\server\lib\start-server.js:146:13) GET /api/auth/callback/auth0?code=4Gh8YFyb6efeGX1W-tha_Nh_nyY7CgDIbqegQFduB9Kbs 302 in 3220ms [NextAuth] Error: { cause: 'Configuration', message: 'Wrong configuration, make sure you have the correct environment variables set. Visit https://lobehub.com/docs/self-hosting/advanced/authentication for more details.', name: 'NextAuth Error' } GET /api/auth/error?error=Configuration 200 in 1683ms

配置信息如下

`APP_URL=http://192.168.1.134:3010

NextAuth related configurations

NEXT_AUTH_SSO_PROVIDERS=casdoor
NEXT_AUTH_SECRET=NX2kaPE923dt6BL2U8e9oSre5RfoT7hg

Casdoor secret

AUTH_CASDOOR_ID=4da6d609208ebe15b658
AUTH_CASDOOR_SECRET=b0f98d7addeb7d099679886cfa3f5f01b30d3e5d
AUTH_CASDOOR_ISSUER=http://192.168.153.120:8000/
AUTH_URL=http://192.168.1.134:3010/api/auth
NEXTAUTH_URL=http://192.168.1.134:3010/api/auth

Auth0 configurations

AUTH_AUTH0_ID=uf4NQbhAKT5lfBP5bSlimDGjQFBlJ87T
AUTH_AUTH0_SECRET=-NgEz1fajy0yDvcinHmFXXDgD3-6S2xXNKVHdcA4p3TYJSd7bLeFLh8vLpofSrtd
AUTH_AUTH0_ISSUER=https://dev-rpj0kfqyvk1xt060.us.auth0.com

NEXT_PUBLIC_SERVICE_MODE=server

Postgres database URL

数据库配置

Postgres 相关，也即 DB 必须的环境变量

必填，用于加密敏感信息的密钥，可以使用 openssl rand -base64 32 生成

KEY_VAULTS_SECRET=Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=

必填，Postgres 数据库连接字符串，用于连接到数据库

格式：postgresql://username:password@host:port/dbname，如果你的 pg 实例为 Docker 容器且位于同一 docker-compose 文件中，亦可使用容器名作为 host

DATABASE_URL=postgresql://postgres:mysecretpassword@192.168.153.120:5432/my-postgres`

casdoor配置如下

auth0配置如下

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

我的casdoor是装在局域网下的docker中，auth0是用的官网的域名。搞几天了，还是不行。忘回复！

lobehubbot · 2025-01-20T09:48:30Z

lobehubbot
Jan 20, 2025
Maintainer

👀 @muwingueaiguei

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。我们会尽快调查此事，并尽快回复您。请确保您已经提供了尽可能多的背景信息。

0 replies

muwingueaiguei · 2025-01-20T09:50:25Z

muwingueaiguei
Jan 20, 2025
Author

分别使用casdoor和auth0，都是报同样的错误。

0 replies

lobehubbot · 2025-01-20T09:50:37Z

lobehubbot
Jan 20, 2025
Maintainer

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

Using casdoor and auth0 respectively, the same error is reported.

0 replies

@muwingueaiguei · 2025-01-20T09:52:00Z

dosubot[bot]
bot Jan 20, 2025

@muwingueaiguei 你好！我是一个可以帮助你解决bug，回答问题，并成为贡献者的机器人。我可以在等待人类维护者的时候帮助你。

To resolve the AdapterError encountered during Casdoor login callback in your locally deployed LobeChat application on Windows, ensure the following:

Protocol Consistency: Make sure that the protocol in the Casdoor callback URL matches the protocol specified in the AUTH_URL setting in your .env file. If your AUTH_URL uses http://, then your Casdoor callback URL should also use http://.
Correct Callback URL: Verify that the Casdoor application is configured with the correct redirect URL. For a local development environment, it should be http://localhost:3010/api/auth/callback/casdoor. Ensure this matches the setup in your Casdoor application settings.
Environment Variables: Double-check that the AUTH_CASDOOR_ID, AUTH_CASDOOR_SECRET, and AUTH_CASDOOR_ISSUER environment variables are correctly set in your LobeChat configuration. For a local development environment, AUTH_CASDOOR_ISSUER should be http://192.168.153.120:8000/.
Network Configuration: If you are using a local network IP, ensure that the IP and port settings are correctly configured as per your deployment setup. For example, http://192.168.1.134:3010 for LobeChat and http://192.168.153.120:8000 for Casdoor.

By ensuring these configurations are correct, you should be able to resolve the AdapterError during the Casdoor login callback ^[1].

To continue talking to Dosu, mention @dosu.

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

0 replies

arvinxx · 2025-01-20T09:57:57Z

arvinxx
Jan 20, 2025
Maintainer

@cy948 来看看？

0 replies

SpeedupMaster · 2025-01-20T12:19:29Z

SpeedupMaster
Jan 20, 2025

AUTH_CASDOOR_ID=4da6d609208ebe15b658
AUTH_CASDOOR_SECRET=b0f98d7addeb7d099679886cfa3f5f01b30d3e5d
AUTH_CASDOOR_ISSUER=http://192.168.153.120:8000/
AUTH_URL=http://192.168.1.134:3010/api/auth
NEXTAUTH_URL=http://192.168.1.134:3010/api/auth

AUTH_URL=http://192.168.1.134:3010/api/auth 这个不用了

1 reply

muwingueaiguei Jan 20, 2025
Author

不用吗？我删了还是不行

cy948 · 2025-01-20T12:48:25Z

cy948
Jan 20, 2025

介绍一下这几个应用所处的环境，lobechat, pgsql, casdoor。确保lobechat所在的容器能访问数据库和casdoor.

5 replies

muwingueaiguei Jan 20, 2025
Author

lobechat在Windows本地npm run dev启动，pgsql和casdoor都在虚拟机的docker中。

casdoor连接

数据库连接

cy948 Jan 20, 2025

数据库是空库吗？

cy948 Jan 20, 2025

如果是空库，本地dev环境启动的时候要push 表结构

muwingueaiguei Jan 20, 2025
Author

已经pushg过了

cy948 Jan 20, 2025

环境变量加上 NEXT_AUTH_DEBUG=1 启动看看报错日志

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Bug] 本地Windows部署，登录认证回调报错 #5518

{{title}}

Replies: 7 comments 6 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

[Bug] 本地Windows部署，登录认证回调报错 #5518

muwingueaiguei Jan 20, 2025

📦 部署环境

📌 软件版本

💻 系统环境

🌐 浏览器

🐛 问题描述

我在本地vscode中以server方式正常启动项目

当使用casdoor登录时，回调报错

配置信息如下

NextAuth related configurations

Casdoor secret

Auth0 configurations

Postgres database URL

数据库 配置

Postgres 相关，也即 DB 必须的环境变量

必填，用于加密敏感信息的密钥，可以使用 openssl rand -base64 32 生成

必填，Postgres 数据库连接字符串，用于连接到数据库

格式：postgresql://username:password@host:port/dbname，如果你的 pg 实例为 Docker 容器且位于同一 docker-compose 文件中，亦可使用容器名作为 host

casdoor配置如下

auth0配置如下

📷 复现步骤

🚦 期望结果

📝 补充信息

Replies: 7 comments · 6 replies

lobehubbot Jan 20, 2025 Maintainer

muwingueaiguei Jan 20, 2025 Author

lobehubbot Jan 20, 2025 Maintainer

dosubot[bot] bot Jan 20, 2025

arvinxx Jan 20, 2025 Maintainer

SpeedupMaster Jan 20, 2025

muwingueaiguei Jan 20, 2025 Author

cy948 Jan 20, 2025

muwingueaiguei Jan 20, 2025 Author

cy948 Jan 20, 2025

cy948 Jan 20, 2025

muwingueaiguei Jan 20, 2025 Author

cy948 Jan 20, 2025

muwingueaiguei
Jan 20, 2025

数据库配置

Replies: 7 comments 6 replies

lobehubbot
Jan 20, 2025
Maintainer

muwingueaiguei
Jan 20, 2025
Author

lobehubbot
Jan 20, 2025
Maintainer

dosubot[bot]
bot Jan 20, 2025

arvinxx
Jan 20, 2025
Maintainer

SpeedupMaster
Jan 20, 2025

muwingueaiguei Jan 20, 2025
Author

cy948
Jan 20, 2025

muwingueaiguei Jan 20, 2025
Author

muwingueaiguei Jan 20, 2025
Author