NodeJS Server Windows Plesk

[Marzio]

After some time I resume the NodeJS topic on Windows Server and Plesk panel, because I would like to be able to use NodeJS also on Windows Hosting (not chosen by me)
I have read the various posts in the community, but I must say that I have a somewhat confused vision and I would like to be sure not to get the configuration wrong and then try to find out why it did not work
I therefore report the images my configuration.
If anyone can confirm to me that everything is correct or is able to point out any errors, thank you:

[ben]

You have not set the remote sever up properly. First you will need to install NodeJS and the configure NodeJS. The NodeJS setup should look like:

You wil need to restart the app after configuration as well as after making changes to the website.

[Marzio]

That’s just what I did for nodejs configuration in the Plesk panel.
Now if you confirm to me that all other settings are right, now I search to understand why the ftp connection gives me an error.

[ben]

This is what the remote File Manager should show:

The node_modules folder does not get uploaded from Wappler; it is created by the remote server.

[Marzio]

Thanks Ben
Wanting to start over, if I understand correctly, not being able to have a working ftp connection, I must first configure the NodeJS App in the Plesk panel.
I state that in the server there is already an app folder (containing App_Data / aspnet_client / tmp), so I create into a new public folder and an index.js file
Then I enable the nodejs app
The result is the following, now what should I do ?:

[Marzio]

I copied the files from Wappler to the server app folder, I set NodeJS on the server and I tried to install NPM
Unfortunately it gives me an error and the NPM folder does not appear in the root

[ben]

I just noticed that you are developing directly on the remote. I am not sure, but that could be the cause of your worries.

Even if it is not the cause, it is always best practice to develop locally and upload when ready.

[Marzio]

It works locally, but if public on the server it doesn’t work
Perhaps the problem is that I can’t create the npm folder

[ben]

When I install NodeJS on the remote, I also get all sorts of error messages. I ignored them and all is well.

[Marzio]

Yes but it does not create the .npm folder in the Root and the .npmrc file in the app folder, as in your case

[Marzio]

I noticed a strange thing
Even if the .npm folder is not listed, if I develop a simple index.js page on localhost, it displays without problems.
If I then change the document root / app setting instead of / app / public on the server, and I upload on remote I can view the page correctly, but every time I have to open the tmp folder and change the permissions to the restart.txt file
And of course this is still a problem

[TMR]

I had similar problems when using NodeJs on a windows server, after a great many attempts I gave up on it - shame really as I did see some great potential.

[Marzio]

Yes, it’s a real shame, also because it could potentially work, but I still haven’t found the right solution
In some moments I try to make it work, but I still don’t quite understand how

[joseph_Honey1]

My experience with NodeJS was similar, after a great deal of experimenting I had to give up on it, as it had a great deal of potential, but I just gave up on it due to bad experiences.