Next.js Discord

Discord Forum

Upstream Image Response Failure

Unanswered
Gray-tailed Tattler posted this in #help-forum
Open in Discord
Gray-tailed TattlerOP
Occasionally getting 

 ⨯ upstream image response failed for /collection-navigation-bg-jeans.webp ResponseAborted
    at Object.fetch (node:internal/deps/undici/undici:11372:11)
    at async globalThis.fetch (webpack-internal:///(rsc)/./node_modules/next/dist/server/lib/patch-fetch.js:216:16)
    at async invokeRequest (/Users/james/Sites/flears/frontend/node_modules/next/dist/server/lib/server-ipc/invoke-request.js:17:12)
    at async /Users/james/Sites/flears/frontend/node_modules/next/dist/server/next-server.js:600:35
    at async imageOptimizer (/Users/james/Sites/flears/frontend/node_modules/next/dist/server/image-optimizer.js:576:13)
    at async cacheEntry.imageResponseCache.get.incrementalCache (/Users/james/Sites/flears/frontend/node_modules/next/dist/server/next-server.js:181:65)
    at async /Users/james/Sites/flears/frontend/node_modules/next/dist/server/response-cache/index.js:90:36
    at async /Users/james/Sites/flears/frontend/node_modules/next/dist/lib/batcher.js:41:32
ImageError: "url" parameter is valid but upstream response is invalid
    at imageOptimizer (/Users/james/Sites/flears/frontend/node_modules/next/dist/server/image-optimizer.js:588:19)
    at async cacheEntry.imageResponseCache.get.incrementalCache (/Users/james/Sites/flears/frontend/node_modules/next/dist/server/next-server.js:181:65)
    at async /Users/james/Sites/flears/frontend/node_modules/next/dist/server/response-cache/index.js:90:36
    at async /Users/james/Sites/flears/frontend/node_modules/next/dist/lib/batcher.js:41:32 {
  statusCode: 500


when using a Next Image with a local webp image.

3 Replies

Gray-tailed TattlerOP
possibly was a result of installing sharp for npm run start which was recommended in the terminal
Cape lion
I get the same error without installing Sharp...
Gray-tailed TattlerOP
Are you previewing a build? After removing sharp I haven’t had it back yet. Looks like it’s a bug without a resolution perhaps https://github.com/vercel/next.js/issues/53715