aaP_mdestafadilah_simrs Hi Kern, After minor update to v7.0.3 i change node js in PM2 manager, it's always default to v4.2.0 not select to my choice. like below
aaPanel_Kern Hello, this is caused by the unsuccessful node version installation. It is recommended that you use the node project.
aaP_mailkevin Getting same error. Only one version is installed in NPM Seems i might be an issue with the current update? (version 7.0.5) Downgrading (temporarily) solved it for me : https://github.com/AaronYES/aaPanel but the issue reverts after fixing the panel from 'bt' command
aaPanel_Kern Hello, this is a plug-in problem. It is recommended that you use the node project manager to manage it. aaP_mailkevin
aaP_mailkevin I have an app that requires usage of both node version manager and pm2 how do you mean by plugin issue exactly?
aaPanel_Kern Hello, pm2 currently knows that restarting the server will cause the project to be lost, and the node version cannot be newly installed.
aaP_mailkevin So what's the solution to getting the same version installed via Noe Version Manager to appear in pm2 then? And how come it was working in previous Panel versions and not working now? What's he angle of "disabling" it as it were?
aaP_mailkevin So what's the solution to getting the same version installed via Node Version Manager to appear in Pm2 as well? I have version 16.13.2 installed in Node Version Manager and I'd like that same version to appear as 'Current Version' in pm2 (instead of v4.2.0)
aaP_mailkevin I have an app that requires me to set its "app.js" file to run effectively thus I need to use pm2 manager to do this(using Project list) what's the alternative way to do this using node project manager?
aaP_mailkevin This is my file location containing the 'app.js' file. Kindly advice how to achieve what you've suggested /www/wwwroot/mydomain.com
aaP_mailkevin This approach seems to be working so far on my end cd /www/wwwroot/mydomain.com pm2 start app.js --name "mynodejsappname" pm2 save pm2 startup Kindly work on fixing that pm2 bug on v7.0.5 Cheers!