Deployment of a Next.js application in Arsys + Plesk

[hugocruzlfc]

Summary

Context

I am trying to deploy an application built with Next.js in Arys + Plesk. However, I have not found clear documentation or specific guides on how to do this deployment effectively. I would like to open a discussion to gather best practices, recommendations or possible configurations to accomplish this.

Problem details

When I enter the application web site it loads the login and all the serever side pages perfectly. When I login or register, it goes fine, but I get the following error:

webpack-61986b0a62ba55ed.js:1 Uncaught ChunkLoadError: Loading chunk 974 failed.
(error: https://www.evaluacioncontenidos.com/_next/static/chunks/app/page-535b35af1b4c2c27.js)
at r.f.j (webpack-61986b0a62ba55ed.js:1:2812)
at webpack-61986b0a62ba55ed.js:1:1211
at Array.reduce ()
at r.e (webpack-61986b0a62ba55ed.js:1:1190)
at i (964-02efbd2195ef91bd.js:1:135730)
at 964-02efbd2195ef91bd.js:1:149831
at t (964-02efbd2195ef91bd.js:1:151289)

I don't know if I'm missing files to copy, or some Nginix configuration or something else.

Additional information

- **Next.js version**: 15.4.5
- Deployment platform**: Plext inside Arsys, with Node 22 active and npm
- Local environment**: Node.js 20.18.0, npm 10.8.2, macOS Sequoia 15.6 operating system.
- **Steps performed**:
  1. I upload the project to Plesk via git, install dependencies and do build, then run: 
cp -r public .next/standalone/ && cp -r .next/static .next/standalone/.next/
  2. The output in nextConfig is “standalone”.

Example

https://www.evaluacioncontenidos.com/

[SametDulger]

Hi @hugocruzlfc,

Thanks for sharing your setup and detailed error.

The ChunkLoadError you’re seeing (Loading chunk 974 failed) usually means that the browser can’t find or load a JavaScript chunk file generated by Next.js during client-side navigation. This often happens when the deployed static files or build output are incomplete, missing, or served from an incorrect path.

Here are some tips and best practices for deploying a Next.js standalone build on Arsys + Plesk:

1. Verify Static Files Deployment
   When using the standalone output, you must copy the entire .next/standalone folder along with the .next/static and public folders to your server.

Your step cp -r public .next/standalone/ && cp -r .next/static .next/standalone/.next/ is on the right track, but confirm these files are fully present on the server and accessible.

The _next/static folder should be served statically by your web server (Nginx or Plesk proxy). Make sure the paths match the URLs the browser requests.

2. Check Base Path / Asset Prefix
   If your app is served from a subpath or with a base path, you need to configure basePath or assetPrefix in next.config.js accordingly.

Missing or incorrect base path settings cause chunk loading failures because URLs to JS files are wrong.

3. Web Server / Proxy Configuration
   Make sure your web server or Plesk proxy correctly serves the .next/static files under the /_next/static route.

Configure proper cache headers for these static assets.

Confirm there are no URL rewrites or redirects interfering with static files.

4. Node.js Version
   Your production Node.js 22 version is quite recent; if you experience issues, consider testing with the recommended LTS versions (Node 18 or 20) to rule out compatibility problems.

5. Troubleshooting Steps
   Inspect the network tab in the browser’s developer tools to see which chunk files fail to load and their URLs.

Confirm those files exist on the server at the expected paths.

Restart your Node.js server after deploying new files to ensure changes take effect.

Test with a minimal Next.js app deployed the same way to isolate configuration issues.

Summary
Ensure .next/standalone, .next/static, and public folders are correctly copied and served.

Check your next.config.js for basePath or assetPrefix settings.

Verify your web server serves static assets correctly on /_next/static.

Consider downgrading Node.js if needed.

Use browser dev tools to debug missing chunk URLs.

If you want, I can help you review your next.config.js or your server setup configs.

Good luck with your deployment!