Skip to main content

Have node.js installed but cant get socket.io to work

supercain
Hi, I have just installed node.js on my shared server. Seems to be working since I get past the 2 tests. However, I cant get to run socket.io after following this tutorial.

Comments

9 comments

Date Votes
  • cPRex Jurassic Moderator
    Hey hey! Unfortunately, this is even less supported than NodeJS itself from the earlier guide we worked with, so the only thing I can recommend is to work with the host to see if they can chase down errors. It's one of those "it should just work" type of things if the guide is followed, but it seems like there are other issues with this host causing issues, such as the test application from the earlier post not working the first few times.
    0
  • supercain
    Hi, isnt there any way to troubleshoot the problem? If at least we had some kind of errors log to look into.
    0
  • supercain
    Okay so now I got it to work. One problem though. After I start the app on the terminal with /opt/cpanel/ea-nodejs10/bin/node index.js I can access the app at mydomain.com:3000 however as soon as I exit the terminal the app stops working and I cant even access mydomain.com:3000 anymore. Maybe a cronjob will get around this?
    0
  • cPRex Jurassic Moderator
    That's expected behavior - you test the app by starting the process in your terminal, which is why the docs say you have to open a new terminal session to run the test command. That command just executes the test application, but you'll want to register your actual app in cPanel in order to keep things running:
    0
  • supercain
    great, can i do this myself or need root privileges?
    0
  • cPRex Jurassic Moderator
    That's something you should be able to do in cPanel, assuming the tools have been made available to the users.
    0
  • supercain
    Hi, I did register the application from the very beginning but that doesnt change things. Also, am I supposed to be able to access from example.com/myapp ? because if I do so then the chat wont work at all. It only works if I access from example.com:3000 AND the terminal window is still open.
    0
  • cPRex Jurassic Moderator
    This sounds like we're back at the same point as the other thread, more or less. You'll have to reach out to the host to have them check things on their end.
    0
  • supercain
    I dont think its a problem my host should resolve. It all comes to the correct installation of the socket.io app because Im not even sure if it should reside in the same folder as app.js and all the tutorials are rather confusing.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post