Skip to content
Discussion options

You must be logged in to vote

This usually happens when you're using a custom image loader or have misconfigured your next.config.js.


✅ Fix:

Make sure your next.config.js has an images section like this:

// next.config.js
module.exports = {
  images: {
    domains: ['yourdomain.com'], // update to match your image sources
  },
};

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by morlanandini
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Help
Labels
None yet
2 participants