Back

ENOTFOUND Error on domain address

  • 0
  • Databases
  • Auth
  • Web
  • Self Hosted
Misho
11 Jul, 2024, 17:27
TypeScript
Error getting current user: TypeError: fetch failed
    at node:internal/deps/undici/undici:12345:11
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async _Client.call (webpack-internal:///(rsc)/./node_modules/.pnpm/node-appwrite@13.0.0/node_modules/node-appwrite/dist/client.mjs:272:22)
    at async Databases.getDocument (webpack-internal:///(rsc)/./node_modules/.pnpm/node-appwrite@13.0.0/node_modules/node-appwrite/dist/services/databases.mjs:1667:12)
    at async getUserDB (webpack-internal:///(rsc)/./src/lib/actions/users/get-user.ts:12:22)
    at async getCurrentUser (webpack-internal:///(rsc)/./src/lib/actions/users/get-current-user.ts:19:22)
    at async Home (webpack-internal:///(rsc)/./src/app/(public)/page.tsx:15:18) {
  cause: Error: getaddrinfo ENOTFOUND domain-aaa.store
      at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26)
      at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
    errno: -3007,
    code: 'ENOTFOUND',
    syscall: 'getaddrinfo',
    hostname: 'domain-aaa.store'
  }
}

I had this error a few times in development, can that be probelmatic in production or maybe there is some bug or issue or time incosistencies that i should match or dunno, please help me to solve this issue, i am using Nextjs

TL;DR
Developers are encountering a ENOTFOUND error related to fetching the current user on a domain address. The issue appears to be with DNS lookup failing for the domain. This error might cause problems in production. To resolve this, ensure the domain address is correct and properly configured for fetching requests.
Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more