vercel dev Sentry error

mramericanmike · June 3, 2026, 5:19pm

Whenever I do vercel dev the project runs perfectly, but when I go to the terminal and do Control + C to stop it, then this happens:


Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Terminate batch job (Y/N)? y

Over and over and over.

Why this happens, why is terminating Vercel dev trying to connect to Sentry? How do I disable this. I have Sentry blocked on my PC.

mramericanmike · June 6, 2026, 9:25pm

Just in case the cause is the telemetry that I never enabled, even with telemetry disabled it still happens.

Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Error: An unexpected error occurred!
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: getaddrinfo ENOENT sentry.io
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Terminate batch job (Y/N)? y


λ vercel telemetry status
Vercel CLI 54.7.1 (Node.js 22.13.1)

> Telemetry status: Disabled

> You have opted out of Vercel CLI telemetry
> No data will be collected from your machine

Learn more: https://vercel.com/docs/cli/about-telemetry

ryux1 · June 9, 2026, 3:40pm

Hi MrAmericanMike,

I don’t think this is the normal Vercel CLI telemetry path. Your vercel telemetry status output already shows telemetry is disabled, and the error is specifically a DNS lookup failure for sentry.io.

This looks more like the CLI is hitting an unexpected error while shutting down vercel dev, then trying to report that internal CLI error to Sentry. Because sentry.io is blocked on your machine, the reporting step throws getaddrinfo ENOENT ``sentry.io, which is the error you end up seeing repeatedly.

I’d try to separate the original shutdown issue from the Sentry reporting failure:

npx vercel@latest dev --debug

Then stop it with Ctrl+C and check whether anything appears before the first sentry.io DNS error. If there is an earlier stack trace, that is probably the real bug; the Sentry DNS error is secondary.

Since you’re on Windows and the error is ENOENT rather than the more common ENOTFOUND, this may also be a CLI error-handling edge case when Sentry is blocked at the DNS/hosts/firewall level. I’d test once with a different Node version too, for example Node 20 LTS, just to rule out a Node 22-specific behavior:

node -v
npx vercel@latest --version
npx vercel@latest dev --debug

If it only happens when sentry.io is blocked, the useful bug report details would be:

OS:
Node version:
Vercel CLI version:
Whether it happens with npx vercel@latest dev --debug:
The first stack trace before the sentry.io error, if any:

I wouldn’t paste tokens or project-specific env values, just the CLI/version/debug output around shutdown.

Topic		Replies	Views
Need Help to resolve error - Vercel + Sentry Help nextjs	1	114	September 2, 2024
Vercel is blocking .env download because it validates (and rejects) a value on my behalf Help	3	56	August 4, 2024
Do not receive error report in Sentry when integrate with vercel Help	1	124	September 26, 2025
vercel broke my domains again Help	5	32	May 5, 2026
My project works locally but fails to run on Vercel Help	3	204	December 21, 2024

vercel dev Sentry error

Related topics