Images are not showing after deploying website

Website Link: https://jacobwilsondev.netlify.app/

Images inside public/images folder working well in local environment but it is not working on server after deploying. On image failed requests I could see the below error:
"IPX Error: Error:
Something went wrong installing the “sharp”
module libvips - cpp.so .42: cannot open shared object file: No such file or directory

Possible solutions:

  • Install with verbose logging and look for errors: “npm install --ignore-scripts=false --foreground-scripts --verbose sharp”\
  • Install for the current linux - x64 runtime: “npm install --platform=linux --arch=x64 sharp”\
  • Consult the installation documentation: https: //sharp.pixelplumbing.com/install"

Looking forward to hearing from you. I would be very appreciated your help

Daniel Jin

@danieljindev Try googling for ipx error installing sharp, you may find a solution in the results, as it seems to be a common issue not specific to Netlify.

Actually, I tried them all but still not working.

I find that hard to believe, but I’ll take your word for it.

How are you deploying, is it via CLI?

Have you tried searching related threads directly on the forum:
https://answers.netlify.com/search?q=ipx%20error%20installing%20sharp%20order%3Alatest

Could these relate to your situation?
https://answers.netlify.com/t/next-images-dont-show-up/77865/2
https://answers.netlify.com/t/netlify-next-js-images-throw-ipx-error-500/51632/37

Thanks for your quick answer @nathanmartin I didn’t use CLI for deploying but using the dashboard UI for it.

@danieljindev I presume you’re working with Next? If so, which runtime?

Can you provide your full build log instead of just the error snippet.

Yes, I am working with Next.js. The runtime is Node.js, and we are using Node.js version 14 or higher as specified in our package.json file. I have chose 16.x for now.

There is no warning or error while deploying

@danieljindev What version of Next.js are you working with?

Is it an older version?

Those versions of Node are older, (14 is from 2020, 16 is from 2021)

I ask because this user solved their issue by working with a newer version of the Next.js Runtime

It seems this user is also having the same issue:

@danieljindev, you’re using an outdated Next.js version along with Next Runtime v4 which we don’t actively provide support for. Please upgrade to Next.js 13.5+ along with Runtime v5.