Nodejs RestAPI working on localhost but not on server

Question

I developed a Node.js RestAPI to communicate with a MongoDB database. While I was developing using localhost everything worked fine, but now I need to deploy it to a server so users can test it.

The server is running Ubuntu 16.04, and I have successfully installed the software I need (Node.js and MongoDB) and I'm able to start the server, however, I can't make any request using the client.

If I ping the server I'm able to get a response. I have my Node.js RestAPI running on port 4000.

Any idea what I might be doing wrong or what I might have forgotten? This is the first time I'm deploying to a server.

My server.js file is:

const port = 4000

const bodyParser = require('body-parser')
const express = require('express')

const jwt = require('jsonwebtoken')
const cors = require("cors")
const mongoose = require('mongoose')
const databaseConfig = require('./database')

const server = express()

server.use(cors())
server.options('*', cors());

server.use(bodyParser.urlencoded({ extended: true }))
server.use(bodyParser.json())

server.set('superSecret', databaseConfig.secret)

server.listen(process.env.port || port, function () {
    console.log('Listening')
})

mongoose.connect(databaseConfig.database, function(err, db) {
    if (err) {
        console.log('Unable to connect to the server. Please start the server. Error:', err);
    } else {
        console.log('Connected to Server successfully!');
    }
});

module.exports = server

Any help is appreciated. Thank you.

If you hitting request from local then make sure you have enable the `CORS` in node server — Aabid, Sep 20 '18 at 10:53
Please refer this https://stackoverflow.com/questions/7067966/how-to-allow-cors — Aabid, Sep 20 '18 at 11:03
What is error or response code when you make the request using client? — Ashish, Sep 20 '18 at 11:06
@Aabid I just installed CORS module and added `const cors = require("cors") server.use(cors())` It still does not work. Do I need to change my client requests? — kyrers, Sep 20 '18 at 11:42

score 0 · Answer 1 · answered Sep 20 '18 at 14:40

0

To stop anyone from wasting time on this topic turns out the employee at my university that was supposed to make the host machine IP public forgot to do it! That was the problem, nothing else.

answered Sep 20 '18 at 14:40

kyrers

489
1
6
22

you can close this question – Aabid Sep 21 '18 at 10:11

Nodejs RestAPI working on localhost but not on server

1 Answers1