TypeError: immutable

[Darkhorse-Fraternity]

GET / 200 in 4030ms
 POST / 303 in 21ms
[auth][error] CallbackRouteError: Read more at https://errors.authjs.dev#callbackrouteerror
[auth][cause]: Error: fetch failed
    at context.fetch (/project/create-t3-turbo/node_modules/next/dist/server/web/sandbox/context.js:292:38)
    at fetch (webpack-internal:///(rsc)/../../node_modules/next/dist/compiled/react/cjs/react.react-server.development.js:189:16)
    at doOriginalFetch (webpack-internal:///(rsc)/../../node_modules/next/dist/esm/server/lib/patch-fetch.js:387:24)
    at eval (webpack-internal:///(rsc)/../../node_modules/next/dist/esm/server/lib/patch-fetch.js:536:24)
    at eval (webpack-internal:///(rsc)/../../node_modules/next/dist/esm/server/lib/trace/tracer.js:115:36)
    at NoopContextManager.with (webpack-internal:///(rsc)/../../node_modules/next/dist/compiled/@opentelemetry/api/index.js:2:7062)
    at ContextAPI.with (webpack-internal:///(rsc)/../../node_modules/next/dist/compiled/@opentelemetry/api/index.js:2:518)
    at NoopTracer.startActiveSpan (webpack-internal:///(rsc)/../../node_modules/next/dist/compiled/@opentelemetry/api/index.js:2:18108)
    at ProxyTracer.startActiveSpan (webpack-internal:///(rsc)/../../node_modules/next/dist/compiled/@opentelemetry/api/index.js:2:18869)
    at eval (webpack-internal:///(rsc)/../../node_modules/next/dist/esm/server/lib/trace/tracer.js:97:103)
    at NoopContextManager.with (webpack-internal:///(rsc)/../../node_modules/next/dist/compiled/@opentelemetry/api/index.js:2:7062)
    at ContextAPI.with (webpack-internal:///(rsc)/../../node_modules/next/dist/compiled/@opentelemetry/api/index.js:2:518)
    at NextTracerImpl.trace (webpack-internal:///(rsc)/../../node_modules/next/dist/esm/server/lib/trace/tracer.js:97:28)
    at patched (webpack-internal:///(rsc)/../../node_modules/next/dist/esm/server/lib/patch-fetch.js:180:75)
    at eval (webpack-internal:///(rsc)/../../node_modules/@auth/core/lib/actions/callback/oauth/callback.js:72:20)
    at authenticatedRequest (webpack-internal:///(rsc)/../../node_modules/oauth4webapi/build/index.js:925:45)
[auth][details]: {
  "name": "ConnectTimeoutError",
  "code": "UND_ERR_CONNECT_TIMEOUT",
  "message": "Connect Timeout Error",
  "provider": "discord"
}
 ⨯ Error [TypeError]: immutable
    at _Headers.delete (file:///project/create-t3-turbo/node_modules/next/dist/compiled/edge-runtime/index.js:1:657096)
    at <unknown> (file:///project/create-t3-turbo/node_modules/next/dist/server/web/sandbox/sandbox.js:117:47)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async runWithTaggedErrors (file:///project/create-t3-turbo/node_modules/next/dist/server/web/sandbox/sandbox.js:107:9)
    at async DevServer.runEdgeFunction (file:///project/create-t3-turbo/node_modules/next/dist/server/next-server.js:1201:24)
    at async NextNodeServer.handleCatchallRenderRequest (file:///project/create-t3-turbo/node_modules/next/dist/server/next-server.js:248:37)
    at async DevServer.handleRequestImpl (file:///project/create-t3-turbo/node_modules/next/dist/server/base-server.js:816:17)
    at async (file:///project/create-t3-turbo/node_modules/next/dist/server/dev/next-dev-server.js:339:20)
    at async Span.traceAsyncFn (file:///project/create-t3-turbo/node_modules/next/dist/trace/trace.js:154:20)
    at async DevServer.handleRequest (file:///project/create-t3-turbo/node_modules/next/dist/server/dev/next-dev-server.js:336:24)
 ○ Compiling /_error ...
 ✓ Compiled /_error in 529ms (866 modules)
 GET /api/auth/callback/discord?code=I09tvV8ebQuVFgGBlt9Ojdfl 500 in 10906ms

i got an error by use discord Oauth2, It seems to be caused by a network problem

[strathausen]

First check your discord API key and app id!

If you still get the error: I had the same problem - and its solution came from an unexpected place. I didn't have the right database settings: by default, only vercel's postgres is supported. I ended up using a (free) dev database from vercel instead, and the error went away. Alternatively, you could edit the drizzle config (see the readme or drizzle docs) to support a normal postgres database. I feel like the error message isn't ideal.