My next.js app goes blank after deploying on cPanel

[Wiseard]

Summary

I deployed my Next.js app on cPanel and its blank. It works fine locally. Here are the steps I followed :

1.First, I created a custom server.js in my root directory with the following code :

`const { createServer } = require('http')
const { parse } = require('url')
const next = require('next')

const dev = process.env.NODE_ENV !== 'production'
const hostname = 'localhost'
const port = 3000
// when using middleware hostname and port must be provided below
const app = next({ dev, hostname, port })
const handle = app.getRequestHandler()

app.prepare().then(() => {
createServer(async (req, res) => {
try {
// Be sure to pass true as the second argument to url.parse.
// This tells it to parse the query portion of the URL.
const parsedUrl = parse(req.url, true)
const { pathname, query } = parsedUrl

  if (pathname === '/a') {
    await app.render(req, res, '/a', query)
  } else if (pathname === '/b') {
    await app.render(req, res, '/b', query)
  } else {
    await handle(req, res, parsedUrl)
  }
} catch (err) {
  console.error('Error occurred handling', req.url, err)
  res.statusCode = 500
  res.end('internal server error')
}

})
.once('error', (err) => {
console.error(err)
process.exit(1)
})
.listen(port, () => {
console.log(> Ready on http://${hostname}:${port})
})
})
`

2. Then I edited the package.json file to set the environment to production on the start script :

"scripts": { "dev": "next dev", "build": "next build", "start": "NODE_ENV=production node server.js", "lint": "next lint" },

3. npm run build and compress the following files :

4. Imported and extracted all in the File Manager Root Directory :

5. Created my application on Setup Node.js App with the following information :

6. Stop Application - Run NPM install and then restart the application

After all these steps, my app is blank, and I don't know what I did wrong.

Here is a Github link where you can see all the app code. I'm stuck since yesterday and I appreciate any help you can give me to resolve this problem. I know the issue is due to my app but I can't figure it out. But I'm pretty sure the main problem is located on the server.js file.

I hope all the information I provided could help you to understand.

Additional information

No response

Example

No response

[rahulsharmacode]

I am also facing same issue, my app also works fine in local but, after hosting in cpanel with all steps followed, the app goes blank.

[Yiaoma]

Same here, we had a website hosted on cpanel for almost a year already, it crashed when I updated my packages to match nextjs13

[nicolez9911]

Same thing. I tested some versions, 13.4.13 is the last one that works for me. With later versions I just get empty responses (even with the example project).

[Yiaoma]

How do you downgrade nextjs to 13.4.13, do you just put this version in package.json file?

[nicolez9911]

Yes, that‘s what I did. And then of course npm install and a new build. I‘m nor sure if that‘s the way to go, but it worked for me..

[Yiaoma]

Thank you, it did work but only on nodesj application. We were using passenger before, it is completely broken right now even with downgraded version. Have you had any issues with next images ? I'm getting current error: ""url" parameter is valid but upstream response is invalid"

[nicolez9911]

didn't have any issues with images..

[comtrast-remi]

Same issue here but on a Plesk server. I've also made changes to the package.json file and created a server.js file.

I'm using Next 13.4.19 and Node 16.20.

[Yiaoma]

At the moment the only version we've managed to run without any problems is 13.4.4

[one-and-only]

Bumping this, as the issue still persists with Next.JS 14 and 15-RC.0.

[ByAnthony]

Managed to deploy on CPanel with Next.js 14.2.4. Wrote a wee guide; hope that helps 🙏

[one-and-only]

Managed to deploy on CPanel with Next.js 14.2.4. Wrote a wee guide; hope that helps 🙏

I appreciate the effort. However, the issue here seems that after a while, all page responses end up return literally an empty HTML body after all the headers. The server runs for the first few hours or so, but it eventually "dies". The issue still persists in its original form (I just testedd with latest Canary on Node 22).