• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Resolved NextJS image not able to optimization

Server operating system version
AlmaLinux 8.4
Plesk version and microupdate number
18.0.56 Update #4
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.

Please help me to resolve it issue.
 
Instead of the App Startup File "node_modules/.bin/next", use the custom server "server.js" as explained on the Next.js website:

Set Document Root to /httpdocs
Set Application Root to /httpdocs

Update the package.json file as explained on the Next.js website:
Code:
{
  "scripts": {
    "dev": "node server.js",
    "build": "next build",
    "start": "NODE_ENV=production node server.js"
  }
}

Run"npm install" -> "npm build" -> "npm start" and the <Image /> tag should work.
 
Instead of the App Startup File "node_modules/.bin/next", use the custom server "server.js" as explained on the Next.js website:

Set Document Root to /httpdocs
Set Application Root to /httpdocs

Update the package.json file as explained on the Next.js website:
Code:
{
  "scripts": {
    "dev": "node server.js",
    "build": "next build",
    "start": "NODE_ENV=production node server.js"
  }
}

Run"npm install" -> "npm build" -> "npm start" and the <Image /> tag should work.
Hi, I have the same problem. But when I run "yarn start" I get a server crash
 
Back
Top