SECURITY WARNING: Never run commands you don't understand. Always review code before execution. Use at your own risk.
FixMyError.net
Frontend New Added 8 September 2026

Next.js: Invalid src prop, hostname is not configured under images

next/image optimises remote images on your server, so every external host has to be allowed explicitly. Without the allowlist any URL could be turned into a proxy through your own infrastructure, which is why the component throws rather than falling back to the raw URL.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix
// next.config.js
module.exports = {
  images: {
    remotePatterns: [
      { protocol: 'https', hostname: 'cdn.example.com', pathname: '/images/**' },
      { protocol: 'https', hostname: '**.cloudinary.com' },
    ],
  },
};

// Restart the dev server: next.config.js is not hot reloaded

// Skip optimisation for one image if the host cannot be known ahead of time
<Image src={url} unoptimized width={400} height={300} alt="" />

How to diagnose Frontend errors

Modern frontend errors are dominated by the boundary between server rendering and client hydration. A hydration mismatch means the HTML the server produced does not match what the client would have rendered, usually because of a date, a random value, a browser-only API, or user-specific content rendered during SSR. The second large family is bundler resolution, where the error names a module but the real cause is configuration.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

  1. For hydration errors, read the diff the framework prints: React, Nuxt and Astro all show the mismatched node. Look for Date, Math.random, window, localStorage and locale formatting in that subtree.
  2. Deliberately defer browser-only rendering with a mount effect or the framework's client-only directive rather than suppressing the warning.
  3. For resolution errors, run the bundler with verbose logging and check whether the package ships ESM, CJS or both, and whether your conditions / mainFields configuration selects the right one.
  4. Diagnose layout shift with Lighthouse or the Performance panel's Layout Shift regions. Nearly all CLS comes from images without dimensions, injected banners, and web fonts without font-display: swap.
  5. Reproduce production build failures locally with NODE_ENV=production; dev servers are far more forgiving than production builds.

Tools worth reaching for

  • Lighthouse
  • Chrome Performance panel
  • vite build --debug
  • webpack-bundle-analyzer
  • React DevTools

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

nextjs.org

Related Frontend errors

See all 23 Frontend errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.