• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved next.js images not loading error 500

itexpertnow

New Pleskian
Hi,

I am get issue while loading the image in NextJS project.
The issue is with NextJS <Image> tag. If I use <Image/> than in production the image not get load/display. It gives 500 error.
If I add unoptimized in <Image /> than it get load in production.

I tried deploying the same github repo to another server, and it's working fine...

No error
https://dev.amcolubricants.com/images/footage-placeholder.png

Error 500
https://dev.amcolubricants.com/_next/image?url=/images/footage-placeholder.png&w=3840&q=75


deployed on another server (vercel):
 
Review the logs and see what the logs says, it's hard to say what the issue is without looking at the logs. (You can just go to the domain in question in Plesk and click on logs).
 
The issue is solved in this thread:
 
Back
Top