Error deploying Next.JS With Mongo "Error: querySrv ETIMEOUT _mongodb._tcp." #6870
-
SummarySuddenly I started getting this error on deploy, and the build fails. Error: querySrv ETIMEOUT _mongodb._tcp.
ExampleNo response Steps to ReproduceJust try to run a deploy on Vercel, and I got the error. |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 4 replies
-
I have the same issue with SvelteKit, seems like an issue from today. Error: querySrv ETIMEOUT _mongodb._tcp.*******.skj2pbu.mongodb.net
17:52:41.708 | at QueryReqWrap.onresolve [as oncomplete] (node:internal/dns/promises:291:17)
17:52:41.708 | Emitted 'error' event on Worker instance at:
17:52:41.708 | at [kOnErrorMessage] (node:internal/worker:326:10)
17:52:41.708 | at [kOnMessage] (node:internal/worker:337:37)
17:52:41.708 | at MessagePort.<anonymous> (node:internal/worker:232:57)
17:52:41.709 | at [nodejs.internal.kHybridDispatch] (node:internal/event_target:825:20)
17:52:41.709 | at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28) {
17:52:41.709 | errno: undefined,
17:52:41.709 | code: 'ETIMEOUT',
17:52:41.709 | syscall: 'querySrv',
17:52:41.709 | hostname: '_mongodb._tcp.*******.skj2pbu.mongodb.net'
17:52:41.709 | }
17:52:41.709 |
17:52:41.709 | Node.js v20.13.1
17:52:41.762 | ELIFECYCLE Command failed with exit code 1.
17:52:41.776 | Error: Command "pnpm run build" exited with 1
17:52:42.271 |
Beta Was this translation helpful? Give feedback.
-
also having exactly the same issue today with nextjs deployment |
Beta Was this translation helpful? Give feedback.
-
I used a workaround by building it using a standard MongoDB URI ( |
Beta Was this translation helpful? Give feedback.
-
Hi people, Swarnava from Vercel Customer Success team here. We have received few reports from customers and we are currently investigating this. |
Beta Was this translation helpful? Give feedback.
-
We are sharing update here: https://www.vercel-status.com/incidents/9twxvphwx48c |
Beta Was this translation helpful? Give feedback.
-
There was an issue with Node v20.13.1. We just rolled back to v20.12.1 and it should be fixed now. |
Beta Was this translation helpful? Give feedback.
-
Mine is still showing that error |
Beta Was this translation helpful? Give feedback.
-
This discussion was automatically locked because the community moved to a new site. Please join us at vercel.community |
Beta Was this translation helpful? Give feedback.
There was an issue with Node v20.13.1. We just rolled back to v20.12.1 and it should be fixed now.