jlfdzdev/hestiacp-nodejs

HestiaCP-NodeJS | This plugin allow install multiple nodejs apps using HestiaCP

hestiacp-nodejs's Issues

Invalid Destination Path error when install nodejs app

During installation, I encountered an error with the Node.js app deployment process.
Your assistance would be greatly appreciated.

Error: file /tmp/hst.eDlNv1 was not copied

What could be the problem?

SSH is set to bash, the directories are created...

Bug: Nginx Fails When Port Field is Empty, Default Port Not Set

Description

When the port field is left empty in the configuration, Nginx fails to start due to an invalid port in the upstream configuration. This issue occurs because the default port (3000) is not automatically set when the port field is empty. The error message received when running nginx -t is as follows:

nginx: [emerg] invalid port in upstream "127.0.0.1:" in /home/user/hestiacp_nodejs_config/web/domain.tld/nodejs-app.conf:2

This indicates that Nginx is unable to parse the configuration due to the missing port number after the IP address.

Steps to Reproduce

1. Configure the Nginx upstream to use an IP address without specifying a port.
2. Attempt to start Nginx with the configuration.
3. Observe the error message indicating an invalid port in the upstream configuration.

Generated config files

# .conf
PORT=|START_SCRIPT=""|NODE_VERSION=v20.10.0

# nodejs-app-fallback.conf
location @fallback {
	proxy_pass http://127.0.0.1::/$1;
}

# nodejs-app.conf
location / {
	proxy_pass http://127.0.0.1:;
   	proxy_http_version 1.1;
 	proxy_set_header Upgrade $http_upgrade;
 	proxy_set_header Connection 'upgrade';
 	proxy_set_header Host $host;
	proxy_cache_bypass $http_upgrade;
}

Expected Behavior

It should automatically use the default port (3000) when the port field is empty in the configuration. This would allow Nginx to start successfully without requiring a port to be explicitly specified.

Environment

• HestiaCP version: 1.8.11
• Nginx version: 1.25.5
• Operating System: ubuntu 22.04
• Configuration File: /home/user/hestiacp_nodejs_config/web/domain.tld/nodejs-app.conf

how to start pm2?

Hello, i followed the steps and and im stuck at the latest point.
im not sure if the app is running, pm2 list returns no apps running, but the ecosystem.config file is created.

should i start pm2 manually?

/home/%USER%/%DOMAIN%/private/nodeapp directory is not being created automatically

The /home/%USER%/%DOMAIN%/private/nodeapp directory is not being created automatically despite the user having bash access