Internal Server Error 500

[stalker-66]

Hello!
I did everything according to the instructions.

Installed - https://github.com/virtuosoft-dev/hestiacp-pluginable
Installed - https://github.com/virtuosoft-dev/hcpp-nodeapp

User have bash ssh.
I created a web and I had a nodeapp folder (home/web/domain/nodeapp).

When I go to my link I see a 500 error.

app.outapps.info.error.log:

2024/01/22 19:30:45 [error] 2098#2098: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 95.135.30.188, server: app.outapps.info, request: "GET /favicon.ico HTTP/2.0", upstream: "http://127.0.0.1:50000/favicon.ico", host: "app.outapps.info", referrer: "https://app.outapps.info/"
2024/01/22 19:32:37 [error] 1559#1559: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 95.135.30.188, server: app.outapps.info, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:50000/", host: "app.outapps.info"
2024/01/22 19:32:37 [error] 1559#1559: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 95.135.30.188, server: app.outapps.info, request: "GET /favicon.ico HTTP/2.0", upstream: "http://127.0.0.1:50000/favicon.ico", host: "app.outapps.info", referrer: "https://app.outapps.info/"
2024/01/22 19:36:33 [error] 1559#1559: *13 connect() failed (111: Connection refused) while connecting to upstream, client: 95.135.30.188, server: app.outapps.info, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:50000/", host: "app.outapps.info"
2024/01/22 19:36:33 [error] 1559#1559: *13 connect() failed (111: Connection refused) while connecting to upstream, client: 95.135.30.188, server: app.outapps.info, request: "GET /favicon.ico HTTP/2.0", upstream: "http://127.0.0.1:50000/favicon.ico", host: "app.outapps.info", referrer: "https://app.outapps.info/"

Help! What could be the problem?

How can I see the application's performance? If I log in via ssh, pm2 logs does not work in the console((((

[stalker-66]

How to use log app and pm2?

[Steveorevo]

Did you set the backend template type to NodeApp?

[stalker-66]

Did you set the backend template type to NodeApp?

Yes

[Steveorevo]

Is there an error log in the web domain's ./log folder, adjacent to public_html?

Let's check if NodeJS can be run by the command line. Login to the web domain's user account via SSH; can you get a NodeJS version number via:

node --version

[stalker-66]

Is there an error log in the web domain's ./log folder, adjacent to public_html?

Let's check if NodeJS can be run by the command line. Login to the web domain's user account via SSH; can you get a NodeJS version number via:

node --version

node --version
v12.22.9

node.js installed and working

[Steveorevo]

That node version sounds very old. What OS is this? When you create a new site, and set the backend to NodeApp, a basic "Hello World" should have been created for you (along with the nodeapp folder). Do you see those files there?

[Steveorevo]

Also, what is the location that it reports for the Node runtime? Type:

which node

[stalker-66]

That node version sounds very old. What OS is this? When you create a new site, and set the backend to NodeApp, a basic "Hello World" should have been created for you (along with the nodeapp folder). Do you see those files there?

A test project is created.

[Steveorevo]

This project installs multiple versions of NodeJS (current and the last two LTS (long term support) versions). The command:

which node

Should report that NodeJS is coming from the /opt/nvm/ folder; with a sub folder matching NodeJS v18, v20, etc.

What path are you seeing via "which node"?

[stalker-66]

This project installs multiple versions of NodeJS (current and the last two LTS (long term support) versions). The command:

which node

Should report that NodeJS is coming from the /opt/nvm/ folder; with a sub folder matching NodeJS v18, v20, etc.

What path are you seeing via "which node"?

Ubuntu 22.04 64 bit

[Steveorevo]

It sounds like you're having trouble with the command:

which path

Are you able to login to the user account associated with the website domain via SSH and type:

which path ?

The default response should be something like:

/opt/nvm/versions/node/v20.10.0/bin/node

[LEO318x]

Any solution to this error? I am having the same problem.

In my case:
OS: Ubuntu 22.04.4 LTS
Node version: v20.13.0

Path:
/opt/nvm/versions/node/v20.13.0/bin/node

[Steveorevo]

Which version of HestiaCP do you have installed? Note: this will only work with HestiaCP Ngnix+Apache2 setups. Do you have Nginx present?

[LEO318x]

Which version of HestiaCP do you have installed? Note: this will only work with HestiaCP Ngnix+Apache2 setups. Do you have Nginx present?

Yes, I have nginx and apache2 installed.
HestiaCP: v1.8.11

[Steveorevo]

For the given user, SSH should be enabled for the account. hcpp-nodeapp uses PM2 (process manager 2) to manage NodeJS apps. Login as that user on terminal window and type: pm2 ls Do you see any resulting process list? Or an error message?

…

On Saturday, May 11, 2024, Mike Molina ***@***.***> wrote: Which version of HestiaCP do you have installed? Note: this will only work with HestiaCP Ngnix+Apache2 setups. Do you have Nginx present? Yes, I have nginx and apache2 installed. HestiaCP: v1.8.11 — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE3EB4HY3ZFLKF4QZVOT5TZBZHBVAVCNFSM6AAAAABCFYLJEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVHE2TSMRXHE> . You are receiving this because you commented.Message ID: ***@***.***>