[Bug] next-auth fetch failed with third auth provider #3847

alwqx · 2024-09-08T08:04:36Z

alwqx
Sep 8, 2024

📦 部署环境

Docker

📌 软件版本

v1.15.18

💻 系统环境

Ubuntu

🌐 浏览器

Chrome, Safari

🐛 问题描述

env

lobechat database with third auth provider: auth0, cloudflare-zero-trust.

problem

when click login, will throw error:

$ docker compose logs -f lobechat-db
lobe  | [Database] Start to migration...
lobe  | ✅ database migration pass.
lobe  | -------------------------------------
lobe  |   ▲ Next.js 14.2.8
lobe  |   - Local:        http://localhost:3210
lobe  |   - Network:      http://0.0.0.0:3210
lobe  |
lobe  |  ✓ Starting...
lobe  |  ✓ Ready in 45ms
lobe  | [auth][error] TypeError: fetch failed
lobe  |     at node:internal/deps/undici/undici:13178:13
lobe  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
lobe  |     at async ia (/app/.next/server/chunks/76974.js:357:40645)
lobe  |     at async ic (/app/.next/server/chunks/76974.js:357:43280)
lobe  |     at async ip (/app/.next/server/chunks/76974.js:357:45913)
lobe  |     at async im (/app/.next/server/chunks/76974.js:357:49748)
lobe  |     at async /app/node_modules/.pnpm/next@14.2.8_@babel+core@7.23.6_supports-color@8.1.1__@opentelemetry+api@1.9.0_react-dom@18.3._itjmu72s7n7tov6po6nkhcdpya/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:36932
lobe  |     at async eC.execute (/app/node_modules/.pnpm/next@14.2.8_@babel+core@7.23.6_supports-color@8.1.1__@opentelemetry+api@1.9.0_react-dom@18.3._itjmu72s7n7tov6po6nkhcdpya/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:27548)
lobe  |     at async eC.handle (/app/node_modules/.pnpm/next@14.2.8_@babel+core@7.23.6_supports-color@8.1.1__@opentelemetry+api@1.9.0_react-dom@18.3._itjmu72s7n7tov6po6nkhcdpya/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:38186)
lobe  |     at async doRender (/app/node_modules/.pnpm/next@14.2.8_@babel+core@7.23.6_supports-color@8.1.1__@opentelemetry+api@1.9.0_react-dom@18.3._itjmu72s7n7tov6po6nkhcdpya/node_modules/next/dist/server/base-server.js:1359:42)
lobe  | [NextAuth] Error: {
lobe  |   cause: 'Configuration',
lobe  |   message: 'Wrong configuration, make sure you have the correct environment variables set. Visit https://lobehub.com/docs/self-hosting/advanced/authentication for more details.',
lobe  |   name: 'NextAuth Error'
lobe  | }

📷 复现步骤

lobechat database with auth0,cloudflare-zero-trust auth.

detaild see video:

lobedb-auth-error.mov

🚦 期望结果

I think this may be caused by network timeout config.

when click cloudflare-zero-trust, lohechat will fetch something from cloudfalre but failed. May be we can set fetch timeout to a longer value such as 5s.

📝 补充信息

No response

Answered by arvinxx

Sep 9, 2024

you can try with PROXY_URL

View full answer

lobehubbot · 2024-09-08T08:04:48Z

lobehubbot
Sep 8, 2024
Maintainer

👀 @alwqx

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

@alwqx · 2024-09-08T08:21:04Z

dosubot[bot]
bot Sep 8, 2024

Hey, @alwqx! I'm here to help you with any bugs, questions, or contributions you have. Let's get this issue sorted out!

To resolve the fetch failed error with next-auth when using third-party auth providers like Auth0 and Cloudflare Zero Trust in a Docker-deployed environment, ensure that the environment variables for the Cloudflare Zero Trust provider are correctly set. These variables include CLOUDFLARE_ZERO_TRUST_CLIENT_ID, CLOUDFLARE_ZERO_TRUST_CLIENT_SECRET, and CLOUDFLARE_ZERO_TRUST_ISSUER.

Here is the relevant code snippet for setting up the Cloudflare Zero Trust provider:

import type { OIDCConfig } from '@auth/core/providers';

import { authEnv } from '@/config/auth';

import { CommonProviderConfig } from './sso.config';

export type CloudflareZeroTrustProfile = {
  email: string;
  name: string;
  sub: string;
};

const provider = {
  id: 'cloudflare-zero-trust',
  provider: {
    ...CommonProviderConfig,
    authorization: { params: { scope: 'openid email profile' } },
    checks: ['state', 'pkce'],
    clientId: authEnv.CLOUDFLARE_ZERO_TRUST_CLIENT_ID,
    clientSecret: authEnv.CLOUDFLARE_ZERO_TRUST_CLIENT_SECRET,
    id: 'cloudflare-zero-trust',
    issuer: authEnv.CLOUDFLARE_ZERO_TRUST_ISSUER,
    name: 'Cloudflare Zero Trust',
    profile(profile) {
      return {
        email: profile.email,
        name: profile.name ?? profile.email,
        providerAccountId: profile.sub,
      };
    },
    type: 'oidc',
  } satisfies OIDCConfig<CloudflareZeroTrustProfile>,
};

export default provider;

Ensure that these environment variables are correctly configured in your Docker environment. You can set them in your Dockerfile or docker-compose.yml file as follows:

Dockerfile:

ENV CLOUDFLARE_ZERO_TRUST_CLIENT_ID=your_client_id
ENV CLOUDFLARE_ZERO_TRUST_CLIENT_SECRET=your_client_secret
ENV CLOUDFLARE_ZERO_TRUST_ISSUER=your_issuer

docker-compose.yml:

version: '3.8'
services:
  app:
    image: your_image
    environment:
      - CLOUDFLARE_ZERO_TRUST_CLIENT_ID=your_client_id
      - CLOUDFLARE_ZERO_TRUST_CLIENT_SECRET=your_client_secret
      - CLOUDFLARE_ZERO_TRUST_ISSUER=your_issuer

Make sure to replace your_client_id, your_client_secret, and your_issuer with the actual values from your Cloudflare Zero Trust setup.

Additionally, ensure that your auth.ts configuration file includes the necessary environment variables for Cloudflare Zero Trust:

export const getAuthConfig = () => {
  return createEnv({
    client: {
      NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY: z.string().optional(),
      NEXT_PUBLIC_ENABLE_CLERK_AUTH: z.boolean().optional(),
      NEXT_PUBLIC_ENABLE_NEXT_AUTH: z.boolean().optional(),
    },
    server: {
      CLERK_SECRET_KEY: z.string().optional(),
      CLERK_WEBHOOK_SECRET: z.string().optional(),
      NEXT_AUTH_SECRET: z.string().optional(),
      NEXT_AUTH_SSO_PROVIDERS: z.string().optional().default('auth0'),
      AUTH0_CLIENT_ID: z.string().optional(),
      AUTH0_CLIENT_SECRET: z.string().optional(),
      AUTH0_ISSUER: z.string().optional(),
      GITHUB_CLIENT_ID: z.string().optional(),
      GITHUB_CLIENT_SECRET: z.string().optional(),
      AZURE_AD_CLIENT_ID: z.string().optional(),
      AZURE_AD_CLIENT_SECRET: z.string().optional(),
      AZURE_AD_TENANT_ID: z.string().optional(),
      AUTHENTIK_CLIENT_ID: z.string().optional(),
      AUTHENTIK_CLIENT_SECRET: z.string().optional(),
      AUTHENTIK_ISSUER: z.string().optional(),
      AUTHELIA_CLIENT_ID: z.string().optional(),
      AUTHELIA_CLIENT_SECRET: z.string().optional(),
      AUTHELIA_ISSUER: z.string().optional(),
      CLOUDFLARE_ZERO_TRUST_CLIENT_ID: z.string().optional(),
      CLOUDFLARE_ZERO_TRUST_CLIENT_SECRET: z.string().optional(),
      CLOUDFLARE_ZERO_TRUST_ISSUER: z.string().optional(),
      GENERIC_OIDC_CLIENT_ID: z.string().optional(),
      GENERIC_OIDC_CLIENT_SECRET: z.string().optional(),
      GENERIC_OIDC_ISSUER: z.string().optional(),
      ZITADEL_CLIENT_ID: z.string().optional(),
      ZITADEL_CLIENT_SECRET: z.string().optional(),
      ZITADEL_ISSUER: z.string().optional(),
      LOGTO_CLIENT_ID: z.string().optional(),
      LOGTO_CLIENT_SECRET: z.string().optional(),
      LOGTO_ISSUER: z.string().optional(),
    },
    runtimeEnv: {
      NEXT_PUBLIC_ENABLE_CLERK_AUTH: !!process.env.NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY,
      NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY: process.env.NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY,
      CLERK_SECRET_KEY: process.env.CLERK_SECRET_KEY,
      CLERK_WEBHOOK_SECRET: process.env.CLERK_WEBHOOK_SECRET,
      NEXT_PUBLIC_ENABLE_NEXT_AUTH: !!process.env.NEXT_AUTH_SECRET,
      NEXT_AUTH_SSO_PROVIDERS: process.env.NEXT_AUTH_SSO_PROVIDERS,
      NEXT_AUTH_SECRET: process.env.NEXT_AUTH_SECRET,
      AUTH0_CLIENT_ID: process.env.AUTH0_CLIENT_ID,
      AUTH0_CLIENT_SECRET: process.env.AUTH0_CLIENT_SECRET,
      AUTH0_ISSUER: process.env.AUTH0_ISSUER,
      GITHUB_CLIENT_ID: process.env.GITHUB_CLIENT_ID,
      GITHUB_CLIENT_SECRET: process.env.GITHUB_CLIENT_SECRET,
      AZURE_AD_CLIENT_ID: process.env.AZURE_AD_CLIENT_ID,
      AZURE_AD_CLIENT_SECRET: process.env.AZURE_AD_CLIENT_SECRET,
      AZURE_AD_TENANT_ID: process.env.AZURE_AD_TENANT_ID,
      AUTHENTIK_CLIENT_ID: process.env.AUTHENTIK_CLIENT_ID,
      AUTHENTIK_CLIENT_SECRET: process.env.AUTHENTIK_CLIENT_SECRET,
      AUTHENTIK_ISSUER: process.env.AUTHENTIK_ISSUER,
      AUTHELIA_CLIENT_ID: process.env.AUTHELIA_CLIENT_ID,
      AUTHELIA_CLIENT_SECRET: process.env.AUTHELIA_CLIENT_SECRET,
      AUTHELIA_ISSUER: process.env.AUTHELIA_ISSUER,
      CLOUDFLARE_ZERO_TRUST_CLIENT_ID: process.env.CLOUDFLARE_ZERO_TRUST_CLIENT_ID,
      CLOUDFLARE_ZERO_TRUST_CLIENT_SECRET: process.env.CLOUDFLARE_ZERO_TRUST_CLIENT_SECRET,
      CLOUDFLARE_ZERO_TRUST_ISSUER: process.env.CLOUDFLARE_ZERO_TRUST_ISSUER,
      GENERIC_OIDC_CLIENT_ID: process.env.GENERIC_OIDC_CLIENT_ID,
      GENERIC_OIDC_CLIENT_SECRET: process.env.GENERIC_OIDC_CLIENT_SECRET,
      GENERIC_OIDC_ISSUER: process.env.GENERIC_OIDC_ISSUER,
      ZITADEL_CLIENT_ID: process.env.ZITADEL_CLIENT_ID,
      ZITADEL_CLIENT_SECRET: process.env.ZITADEL_CLIENT_SECRET,
      ZITADEL_ISSUER: process.env.ZITADEL_ISSUER,
      LOGTO_CLIENT_ID: process.env.LOGTO_CLIENT_ID,
      LOGTO_CLIENT_SECRET: process.env.LOGTO_CLIENT_SECRET,
      LOGTO_ISSUER: process.env.LOGTO_ISSUER,
    },
  });
};

export const authEnv = getAuthConfig();

Additional Steps for Cloudflare Zero Trust Configuration

Create an Application in Cloudflare Zero Trust:
- Visit https://one.dash.cloudflare.com/ and navigate to Access - Applications.
- Click Add an application and select SaaS.
- Fill in the application name (e.g., LobeChat SSO), select OIDC, and click Add application.
- In Redirect URLs, enter https://chat.example.com/api/auth/callback/cloudflare-zero-trust (replace chat.example.com with your instance address).
- Record the Client secret, Client ID, and Issuer for later use.
Set Environment Variables:
- Configure the following environment variables in your Docker environment:
  - NEXT_AUTH_SECRET: Key for encrypting Auth.js session tokens.
  - NEXT_AUTH_SSO_PROVIDERS: Set to cloudflare-zero-trust.
  - CLOUDFLARE_ZERO_TRUST_CLIENT_ID: Your Cloudflare Zero Trust Client ID.
  - CLOUDFLARE_ZERO_TRUST_CLIENT_SECRET: Your Cloudflare Zero Trust Client secret.
  - CLOUDFLARE_ZERO_TRUST_ISSUER: Your Cloudflare Zero Trust Issuer.
  - NEXTAUTH_URL (optional): Specify the callback URL for OAuth verification if the default is incorrect.

By following these steps, you can ensure that your environment variables are correctly configured, which should resolve the fetch failed error with next-auth in a Docker-deployed environment. For more detailed instructions, you can refer to the LobeChat documentation on configuring Cloudflare Zero Trust ^[1]^[2]^[3]^[4].

To continue talking to Dosu, mention @dosu.

0 replies

cy948 · 2024-09-09T00:41:17Z

cy948
Sep 9, 2024

If your server located in mainland China, you will get this networking problem.

0 replies

arvinxx · 2024-09-09T04:53:04Z

arvinxx
Sep 9, 2024
Maintainer

you can try with PROXY_URL

1 reply

alwqx Sep 13, 2024
Author

Thank you! set PROXY_URL works for me. And I find the docs of PROXY_URL in Lobe Docs-Environments.

lobehubbot · 2024-09-09T05:31:23Z

lobehubbot
Sep 9, 2024
Maintainer

✅ @alwqx

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

0 replies

alwqx · 2024-09-13T16:11:20Z

alwqx
Sep 13, 2024
Author

@arvinxx Hi, set PROXY_URL helps solve one problem. But get bellow error with postgres after auth in auth0:

I use pgvector/pgvector:pg15 docker image

[Database] Start to migration...
✅ database migration pass.
-------------------------------------
  ▲ Next.js 14.2.8
  - Local:        http://localhost:3210
  - Network:      http://0.0.0.0:3210

 ✓ Starting...
 ✓ Ready in 46ms
[auth][error] AdapterError: Read more at https://errors.authjs.dev#adaptererror
[auth][cause]: Error: Connection terminated unexpectedly
    at /app/node_modules/.pnpm/pg-pool@3.6.2_pg@8.12.0/node_modules/pg-pool/index.js:45:11
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/.next/server/chunks/57614.js:16:11989
    at async getUserByAccount (/app/.next/server/app/api/auth/[...nextauth]/route.js:1:3597)
    at async r.<computed> (/app/.next/server/chunks/76974.js:1:42082)
    at async ir (/app/.next/server/chunks/76974.js:357:34268)
    at async ip (/app/.next/server/chunks/76974.js:357:45375)
    at async im (/app/.next/server/chunks/76974.js:357:49748)
    at async /app/node_modules/.pnpm/next@14.2.8_@babel+core@7.23.6_supports-color@8.1.1__@opentelemetry+api@1.9.0_react-dom@18.3._itjmu72s7n7tov6po6nkhcdpya/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:36932
    at async eC.execute (/app/node_modules/.pnpm/next@14.2.8_@babel+core@7.23.6_supports-color@8.1.1__@opentelemetry+api@1.9.0_react-dom@18.3._itjmu72s7n7tov6po6nkhcdpya/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:27548)
[auth][details]: {}
[auth][error] AdapterError: Read more at https://errors.authjs.dev#adaptererror
[auth][cause]: Error: Connection terminated unexpectedly
    at /app/node_modules/.pnpm/pg-pool@3.6.2_pg@8.12.0/node_modules/pg-pool/index.js:45:11
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/.next/server/chunks/57614.js:16:11989
    at async getUserByAccount (/app/.next/server/app/api/auth/[...nextauth]/route.js:1:3597)
    at async r.<computed> (/app/.next/server/chunks/76974.js:1:42082)
    at async ir (/app/.next/server/chunks/76974.js:357:34268)
    at async ip (/app/.next/server/chunks/76974.js:357:45375)
    at async im (/app/.next/server/chunks/76974.js:357:49748)
    at async /app/node_modules/.pnpm/next@14.2.8_@babel+core@7.23.6_supports-color@8.1.1__@opentelemetry+api@1.9.0_react-dom@18.3._itjmu72s7n7tov6po6nkhcdpya/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:36932
    at async eC.execute (/app/node_modules/.pnpm/next@14.2.8_@babel+core@7.23.6_supports-color@8.1.1__@opentelemetry+api@1.9.0_react-dom@18.3._itjmu72s7n7tov6po6nkhcdpya/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:27548)
[auth][details]: {}
[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'
}

2 replies

WhyFear Dec 21, 2024

I also encountered this error. Did you solve it?

alwqx Dec 24, 2024
Author

No need pay more time on this, you can use chatnio or latest lube-chat database with casdoor auth.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Bug] next-auth fetch failed with third auth provider #3847

{{title}}

Replies: 6 comments 3 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

[Bug] next-auth fetch failed with third auth provider #3847

alwqx Sep 8, 2024

📦 部署环境

📌 软件版本

💻 系统环境

🌐 浏览器

🐛 问题描述

env

problem

📷 复现步骤

🚦 期望结果

📝 补充信息

Replies: 6 comments · 3 replies

lobehubbot Sep 8, 2024 Maintainer

dosubot[bot] bot Sep 8, 2024

Additional Steps for Cloudflare Zero Trust Configuration

cy948 Sep 9, 2024

arvinxx Sep 9, 2024 Maintainer

alwqx Sep 13, 2024 Author

lobehubbot Sep 9, 2024 Maintainer

alwqx Sep 13, 2024 Author

WhyFear Dec 21, 2024

alwqx Dec 24, 2024 Author

alwqx
Sep 8, 2024

Replies: 6 comments 3 replies

lobehubbot
Sep 8, 2024
Maintainer

dosubot[bot]
bot Sep 8, 2024

cy948
Sep 9, 2024

arvinxx
Sep 9, 2024
Maintainer

alwqx Sep 13, 2024
Author

lobehubbot
Sep 9, 2024
Maintainer

alwqx
Sep 13, 2024
Author

alwqx Dec 24, 2024
Author