Trying to install node.js but having issues

[supercain]

Hi,

I followed this tutorial here: Node.js Hosting Configuration and Installing Node.js Apps | cPanel Blog and it was going well up until this point where I tested it by
entering the command /opt/cpanel/ea-nodejs10/bin/node app.js for which I get: Server running at http://127.0.0.1:3000.

However, as for the next test:
curl http://127.0.0.1:3000 I get a "failed to connect" error. Why is that?

Thank you.

 

[cPRex]

Hey there! We've updated the instructions a bit since that blog post was written. Can you try working through the steps here instead to see if you get better results?

How to Install a Node.js Application | cPanel & WHM Documentation

This document describes how to install a Node.js web application. Node.js is a JavaScript runtime that allows you to build scalable web applications.

docs.cpanel.net

 

[supercain]

Hi,

thank you for the reply. However, I dont see any significant changes in the updated tutorial. In fact, all the steps up until the point Im having issues are exactly the same. Is there any other way I can troubleshoot this?

Thank you.

 

[cPRex]

Thanks for that feedback. I worked through the steps on a test server and didn't run into an issue. It's important to note that steps 2 and 3 and the "Test the Application" section do mention that you need to log in as the cPanel user to a new terminal window/session. That ensures that you're loading the node application which you started with the "/opt/cpanel/ea-nodejs10/bin/node app.js" command.

When you run "/opt/cpanel/ea-nodejs10/bin/node app.js" do you get the "Server running at http://127.0.0.1:3000/" output in the terminal window? If so, I would expect a telnet command, assuming telnet is installed on the server, to be accessible to the user and to return positive output when tested with the following command:

telnet 127.0.0.1 3000

Here is what I get as the cPanel user when running that on my end:

[username@hostname ~]$ telnet 127.0.0.1 3000
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.

If that doens't work, something is likely keeping the application from either starting to, or binding on port 3000.

 

[supercain]

Thank you for your kind patience.

When you run "/opt/cpanel/ea-nodejs10/bin/node app.js" do you get the "Server running at http://127.0.0.1:3000/" output in the terminal window?

yes. After that, right on that same window I ran telnet 127.0.0.1 3000 but nothing happens. Maybe I am doing something wrong?

EDIT: turns out I dont have telnet on my server. Any other way to test this?

 

[cPRex]

It would be best to install telnet with the "yum install telnet" command, as that package is included with the operating system itself.

 

[supercain]

Hi,

I cant. I am on a shared hosting. Maybe thats the problem all along? I just realized I forgot to mention that, sorry.

My provider performed the first steps for me, the ones that require to be done by the root user, although now Im not exactly sure they did correctly.

 

[cPRex]

Ah, that would be an issue then.

You'd have to work directly with the provider to have them do additional troubleshooting then, as all that testing would have to be done as the root user. Hopefully they are able to get more details on their end for you.

 

[supercain]

Is there any way I can make sure they installed things properly from my end?

 

[cPRex]

Unfortunately, I think you already have - if the previous installation steps would have went well, I would have expected the test app to just work with the command that failed.

 

[supercain]

what should be exactly the problem? port 3000 seems to be open since I get the message.

 

[cPRex]

Unfortunately I'm not sure what the issue may be. You'll have to see why the test app didn't respond on port 3000, but that's something the host would need to test. It could be any number of things on their end with the server setup.

 

[supercain]

it did respond to port 3000. i get the message Server running at http://127.0.0.1:3000.

 

[cPRex]

In your first post you said you got a "failed to connect" error with the curl command, so either the server isn't really running properly or there is some other issue with that port that is keeping you from connecting.

 

[supercain]

so the first test being past means nothing?

 

[cPRex]

I wouldn't say it's meaningless, but everything has to be taken in context. If one message says it's working, and the other says it's not, there's an issue that needs to be addressed.

If your host isn't able to resolve that they are welcome to submit a ticket to our team so we can take a look.

 

[supercain]

thank you. i will let you know.

 

[cPRex]

If they do end up opening a ticket with us and you can get that number (it starts with a 9, currently) please post it here and I can follow along with that on my end.

 

[supercain]

Hi again,

seems like its working since I finally got past the 2 tests. Now i would like to install socket.io but im still having issues so Im opening a new thread.

Thank you.