Hi guys, I've just installed Node 0.10.43 and jsbin on one of my Webfaction servers. This installation went fine, I can see the modules installed correctly in Node's directory and I go the default Hello World appearing for Node on my site. However, I cannot for the life of me get jsbin to appear instead. I've tried configuring the host and port settings in jsbin and also the start command for Node as detailed at the bottom of here: Webfaction Community: install-nodejs-with-express-framework All I get is a 502 Bad Gateway message when I try to view the site. Any help or detailed instructions gratefully accepted, thanks. asked 31 Mar '16, 11:49 zilog8bit |
To use jsbin, please create a Node.js 0.10.43 app and note down the app's port. Assign it to a website entry and note down the domain that you are going to use. Then start an ssh session and run the following commands:
In that file type the following:
Change the host value to the domain you are going to use to server the app. You should now be able to start your app using the following command:
where NNNNN is the port assigned from the control panel. answered 31 Mar '16, 13:32 iliasr ♦♦ Thank you iliasr, unfortunately I'm still getting a 502 Bad Gateway. I've removed the previous application via the Webfaction control panel, created a new one and followed your suggestions down to the letter and still no luck :(
(31 Mar '16, 20:29)
zilog8bit
|
Ilias' procedure worked for me, but with a couple of changes. First, I had to add the "static" parameter to my config, like this:
Then, I dropped the environment variables for
Once I did that, the app was up and running and accessible via the site to which it was assigned. answered 01 Apr '16, 00:17 seanf |
Hi guys, thank you for the input so far, unfortunately still a no-go for me. Not sure what I'm doing wrong. I spent 14 hours the last two days running through tutorials for Node on a home Ubuntu server and honestly have found it an absolute nightmare to get anything running properly, if at all. I know folks claim Python to be awkward but at least it's logical to learn, even without documentation, Node just doesn't want to do anything. I'll be dumping jsbin and sticking to online jsfiddles just to check code for a couple of sites but just in case anybody else hits the same issue, here are the errors that I get each time:
If I don't get the errors I either end up with the 502 Bad Gateway and nothing in the server logs or I get the default Hello World app running which I presume is the cron firing it back up when it's taken me more than 20 minutes to make head or tail of what's going on. answered 01 Apr '16, 13:37 zilog8bit Feel free to raise a support ticket and we can take a look at your deployment.
(01 Apr '16, 13:41)
iliasr ♦♦
|