Deploy Next.JS app with O2Switch's CPanel ISSUE

[Benja-san]

Hello Team,
I am currently deploying a test app on my client's server based on 02Switch. Unfortunately it seems a bit complicated to deploy node apps with this host.

I managed successfully to get the ssh connection, I cloned the repo onto the server but when I try to build the app, I have this error coming up :

`error - Failed to load next.config.js, see more info here https://nextjs.org/docs/messages/next-config-error

Build error occurred
RangeError: WebAssembly.instantiate(): Out of memory: wasm memory
at internal/deps/cjs-module-lexer/dist/lexer.js:1:33593
at async initCJSParse (internal/modules/esm/translators.js:72:5)
at async Loader.commonjsStrategy (internal/modules/esm/translators.js:185:18)
at async link (internal/modules/esm/module_job.js:67:21)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! app-name@ build: next build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the app-name@ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/vnzg2266/.npm/_logs/2021-12-01T10_53_56_837Z-debug.log`

Has someone got the same trouble, trying to build a node app onto a server? And if yes, could you help me :D ??

Thanks a lot for taking time reading it!

[slobodanmilinkovic]

I have the exact same problem. Someone, please.

[aboda1986]

same issue for me

[ActivatedDigital]

+1

[asheroto]

Same here...

[hellotreedigital]

SAME :(

[amaurylebouteux]

Same ...

[amaurylebouteux]

Same ...
this worked for me: https://dev.to/techfortified/how-to-host-nextjs-website-on-cpanel-2dij

[onlinejo]

hello some news ?

[loicrey]

Are you using the terminal inside CPanel from your browser ?

[onlinejo]

yes

[loicrey]

The browser Terminal have some limitations. Consider trying with a classic Terminal and SSH connection to your o2switch server
see : https://faq.o2switch.fr/hebergement-mutualise/tutoriels-cpanel/terminal#erreur-de-memoire-nodenpm

[asheroto]

Not for me, running on local, haven't tested in awhile

[mcasters]

"Out of memory: wasm memory" : There is not enough resources to build the project.
Build in local, and copy the .next folder in your production root app.

[onlinejo]

i think o2switch is not good hosting for nextJS , they use old technology

[JayMds]

This is not Next.Js based issue and i'm not even Next.js user, by the way i solved my problem hosting node app on O2switch, the terminal from cpanel is memory limited, you have to login there with SSH (white list your ip 1st), once you're logged use the 'source' cmd specified in node.js app panel of your project, and you could build your app from there

https://faq.o2switch.fr/hebergement-mutualise/tutoriels-cpanel/app-nodejs
from their doc if you read "deploying react app" you will usefull informations but you will have to adapt for your case, also support could give you more informations

[JayMds]

This is not Next.Js based issue and i'm not even Next.js user, by the way i solved my problem hosting node app on O2switch, the terminal from cpanel is memory limited, you have to login there with SSH (white list your ip 1st), once you're logged use the 'source' cmd specified in node.js app panel of your project, and you could build your app from there

https://faq.o2switch.fr/hebergement-mutualise/tutoriels-cpanel/app-nodejs
from their doc if you read "deploying react app" you will usefull informations but you will have to adapt for your case, also support could give you more informations

[sohelzerdoumi]

For o2switch deployment,

Packages

install package from ssh to bypass memory limits and webassembly:

source /home/myaccount/nodevenv/app/myapplication/release/20/bin/activate
cd /home/myaccount/app/myapplication/release
npm install

Prisma

for prisma, change your schema binaryTargets with correct ssl version

generator client {
provider = "prisma-client-js"
binaryTargets = ["native", "debian-openssl-1.0.x"]
previewFeatures = []
}

generate prisma assets:

npm exec prisma generate

Logs

in order to have production logs, update .htaccess with:

PassengerAppLogFile "/home/myaccount/app/myapplication/release/production.log"

All of this worked for me