Simple Node JS Server on Ubuntu MEAN one click image

Hello there

I tried to setup a simple express server using the advice on here:

I followed the steps, and now have my main app.js file in the folder /opt/healthPill. I installed the node modules from here successfully.

I have tried to access the server through with no luck. I also tried, and in both cases I get net::ERR_CONNECTION_REFUSED returned in my browser (Chrome) console log.

It is worth noting that I could not run the final command in the tutorial, as I did not have grunt installed, nor a gruntfile.js. As a result, I have tried with and without running the truncated command “NODE_ENV=production PORT=80”.

I am sorry if this is a really basic question, I am quite new to server config. All I am trying to do is create a small node server with one express POST endpoint. Running the project locally allows this.

Any help would be much appreciated.


Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

The instructions in the linked tutorial are for running an app based on the MEAN.js stack, but you are by no way limited to using that tool set. The MEAN One-Click image simply gives you Node.js and MongoDB pre-installed with a sample project in /opt/mean

Grunt itself is installed and available system-wide, but of course unless you have a gruntfile.js in your project it isn’t very useful. In that case, just start the app as you normally would with npm start or calling node app.js directly.