Unable to create user using Postman - Nodemon App Crashed












0















js and in learning phase. I tried to create a new user by saving it into database using mongodb. But when i tried to post the data using POSTMAN, I am getting the following error:



Could not get any response. There was an error connecting to http://localhost:3000/create-user



Nodemon also crashed showing [nodemon] app crashed - waiting for file changes before starting...



I manually run the file and checked but when I tried to post data, connection got lost and terminated.



Below is the server.js file:



const express = require('express');
const morgan = require('morgan');
const mongoose = require('mongoose');

var User = require('./models/user');

const app = express();

mongoose.connect('mongodb://test:check123@ds211694.mlab.com:11694/parpet', { useNewUrlParser: true }, (err) => {
if(err) {
console.log(err);
} else {
console.log('Connected Successfully');
}
})
// Middleware for log data
app.use(morgan('dev'));
app.use(express.json());
app.use(express.urlencoded({ extended: false }));

app.post('/create-user', (req, res) => {
var user = new User();
user.profile.name = req.body.name;
user.email = req.body.email;
user.password = req.body.password;
user.save(function (err) {
console.log('checking.....');
if(err) {
console.log('Error');
} else {
res.json('Successfully created a new user');
}
});
});

const port = process.env.PORT || 3000;

app.listen(port, (err) => {
if(err) throw err;
console.log(`Server listening on port ${port}`);
});


And the model file is



const mongoose = require('mongoose');
const bcrypt = require('bcrypt');

var Schema = mongoose.Schema;

/* Creating User Schema */
var UserSchema = new Schema({
email: {
type: String,
unique: true,
lowercase: true
},
password: String,
profile: {
name: {
type: String,
default: ''
},
picture: {
type: String,
default: ''
}
},
address: String,
history: [{
date: Date,
paid: {
type: Number,
default: 0
},
// item:
}]
});

/* Hash the password */
UserSchema.pre('save', function (next) {
var user = this;
if(!user.isModified('password')) {
return next();
}
bcrypt.genSalt(10, function (err, salt) {
if(err) return next(err);
bcrypt.hash(user.password, salt, null, function (err, hash) {
if(err) return next(err);
user.password = hash;
next();
});
});
});

/* Comparing typed password with that in DB */
UserSchema.methods.comparePassword = function (password) {
return bcrypt.compareSync(password, this.password);
}

module.exports = mongoose.model('User', UserSchema);


I tried disabling ssl connections as posted in other stackoverflow questions, but this was not helpful.



So can someone please help me to figure it out. It would be really helpful.



node --version    = v8.9.3
npm --version = 6.4.1
nodemon --version = 1.17.5
express --version = 4.16.0


Thanks










share|improve this question























  • Try running without nodemon to see what the console output shows. Also, you should send a response to create-user even if user.save() fails.

    – Jim B.
    Nov 19 '18 at 3:53













  • @JimB. Yeah i tried running without nodemon. When I do the server connection is getting lost and exit from server. Can you please tell how to send response to create-user when user.save fails?

    – DEEPESH KUMAR R
    Nov 19 '18 at 3:55











  • Difficult to debug without your mongodb connection.

    – KibGzr
    Nov 19 '18 at 4:08











  • By any chance are you using any proxy in postman? You can check that by going to Settings > Proxy Sometimes I have seen people struggling with this issue.

    – Sivcan Singh
    Nov 19 '18 at 6:35











  • @SivcanSingh : Yeah i tried at first, but still facing the same issue

    – DEEPESH KUMAR R
    Nov 19 '18 at 8:24
















0















js and in learning phase. I tried to create a new user by saving it into database using mongodb. But when i tried to post the data using POSTMAN, I am getting the following error:



Could not get any response. There was an error connecting to http://localhost:3000/create-user



Nodemon also crashed showing [nodemon] app crashed - waiting for file changes before starting...



I manually run the file and checked but when I tried to post data, connection got lost and terminated.



Below is the server.js file:



const express = require('express');
const morgan = require('morgan');
const mongoose = require('mongoose');

var User = require('./models/user');

const app = express();

mongoose.connect('mongodb://test:check123@ds211694.mlab.com:11694/parpet', { useNewUrlParser: true }, (err) => {
if(err) {
console.log(err);
} else {
console.log('Connected Successfully');
}
})
// Middleware for log data
app.use(morgan('dev'));
app.use(express.json());
app.use(express.urlencoded({ extended: false }));

app.post('/create-user', (req, res) => {
var user = new User();
user.profile.name = req.body.name;
user.email = req.body.email;
user.password = req.body.password;
user.save(function (err) {
console.log('checking.....');
if(err) {
console.log('Error');
} else {
res.json('Successfully created a new user');
}
});
});

const port = process.env.PORT || 3000;

app.listen(port, (err) => {
if(err) throw err;
console.log(`Server listening on port ${port}`);
});


And the model file is



const mongoose = require('mongoose');
const bcrypt = require('bcrypt');

var Schema = mongoose.Schema;

/* Creating User Schema */
var UserSchema = new Schema({
email: {
type: String,
unique: true,
lowercase: true
},
password: String,
profile: {
name: {
type: String,
default: ''
},
picture: {
type: String,
default: ''
}
},
address: String,
history: [{
date: Date,
paid: {
type: Number,
default: 0
},
// item:
}]
});

/* Hash the password */
UserSchema.pre('save', function (next) {
var user = this;
if(!user.isModified('password')) {
return next();
}
bcrypt.genSalt(10, function (err, salt) {
if(err) return next(err);
bcrypt.hash(user.password, salt, null, function (err, hash) {
if(err) return next(err);
user.password = hash;
next();
});
});
});

/* Comparing typed password with that in DB */
UserSchema.methods.comparePassword = function (password) {
return bcrypt.compareSync(password, this.password);
}

module.exports = mongoose.model('User', UserSchema);


I tried disabling ssl connections as posted in other stackoverflow questions, but this was not helpful.



So can someone please help me to figure it out. It would be really helpful.



node --version    = v8.9.3
npm --version = 6.4.1
nodemon --version = 1.17.5
express --version = 4.16.0


Thanks










share|improve this question























  • Try running without nodemon to see what the console output shows. Also, you should send a response to create-user even if user.save() fails.

    – Jim B.
    Nov 19 '18 at 3:53













  • @JimB. Yeah i tried running without nodemon. When I do the server connection is getting lost and exit from server. Can you please tell how to send response to create-user when user.save fails?

    – DEEPESH KUMAR R
    Nov 19 '18 at 3:55











  • Difficult to debug without your mongodb connection.

    – KibGzr
    Nov 19 '18 at 4:08











  • By any chance are you using any proxy in postman? You can check that by going to Settings > Proxy Sometimes I have seen people struggling with this issue.

    – Sivcan Singh
    Nov 19 '18 at 6:35











  • @SivcanSingh : Yeah i tried at first, but still facing the same issue

    – DEEPESH KUMAR R
    Nov 19 '18 at 8:24














0












0








0








js and in learning phase. I tried to create a new user by saving it into database using mongodb. But when i tried to post the data using POSTMAN, I am getting the following error:



Could not get any response. There was an error connecting to http://localhost:3000/create-user



Nodemon also crashed showing [nodemon] app crashed - waiting for file changes before starting...



I manually run the file and checked but when I tried to post data, connection got lost and terminated.



Below is the server.js file:



const express = require('express');
const morgan = require('morgan');
const mongoose = require('mongoose');

var User = require('./models/user');

const app = express();

mongoose.connect('mongodb://test:check123@ds211694.mlab.com:11694/parpet', { useNewUrlParser: true }, (err) => {
if(err) {
console.log(err);
} else {
console.log('Connected Successfully');
}
})
// Middleware for log data
app.use(morgan('dev'));
app.use(express.json());
app.use(express.urlencoded({ extended: false }));

app.post('/create-user', (req, res) => {
var user = new User();
user.profile.name = req.body.name;
user.email = req.body.email;
user.password = req.body.password;
user.save(function (err) {
console.log('checking.....');
if(err) {
console.log('Error');
} else {
res.json('Successfully created a new user');
}
});
});

const port = process.env.PORT || 3000;

app.listen(port, (err) => {
if(err) throw err;
console.log(`Server listening on port ${port}`);
});


And the model file is



const mongoose = require('mongoose');
const bcrypt = require('bcrypt');

var Schema = mongoose.Schema;

/* Creating User Schema */
var UserSchema = new Schema({
email: {
type: String,
unique: true,
lowercase: true
},
password: String,
profile: {
name: {
type: String,
default: ''
},
picture: {
type: String,
default: ''
}
},
address: String,
history: [{
date: Date,
paid: {
type: Number,
default: 0
},
// item:
}]
});

/* Hash the password */
UserSchema.pre('save', function (next) {
var user = this;
if(!user.isModified('password')) {
return next();
}
bcrypt.genSalt(10, function (err, salt) {
if(err) return next(err);
bcrypt.hash(user.password, salt, null, function (err, hash) {
if(err) return next(err);
user.password = hash;
next();
});
});
});

/* Comparing typed password with that in DB */
UserSchema.methods.comparePassword = function (password) {
return bcrypt.compareSync(password, this.password);
}

module.exports = mongoose.model('User', UserSchema);


I tried disabling ssl connections as posted in other stackoverflow questions, but this was not helpful.



So can someone please help me to figure it out. It would be really helpful.



node --version    = v8.9.3
npm --version = 6.4.1
nodemon --version = 1.17.5
express --version = 4.16.0


Thanks










share|improve this question














js and in learning phase. I tried to create a new user by saving it into database using mongodb. But when i tried to post the data using POSTMAN, I am getting the following error:



Could not get any response. There was an error connecting to http://localhost:3000/create-user



Nodemon also crashed showing [nodemon] app crashed - waiting for file changes before starting...



I manually run the file and checked but when I tried to post data, connection got lost and terminated.



Below is the server.js file:



const express = require('express');
const morgan = require('morgan');
const mongoose = require('mongoose');

var User = require('./models/user');

const app = express();

mongoose.connect('mongodb://test:check123@ds211694.mlab.com:11694/parpet', { useNewUrlParser: true }, (err) => {
if(err) {
console.log(err);
} else {
console.log('Connected Successfully');
}
})
// Middleware for log data
app.use(morgan('dev'));
app.use(express.json());
app.use(express.urlencoded({ extended: false }));

app.post('/create-user', (req, res) => {
var user = new User();
user.profile.name = req.body.name;
user.email = req.body.email;
user.password = req.body.password;
user.save(function (err) {
console.log('checking.....');
if(err) {
console.log('Error');
} else {
res.json('Successfully created a new user');
}
});
});

const port = process.env.PORT || 3000;

app.listen(port, (err) => {
if(err) throw err;
console.log(`Server listening on port ${port}`);
});


And the model file is



const mongoose = require('mongoose');
const bcrypt = require('bcrypt');

var Schema = mongoose.Schema;

/* Creating User Schema */
var UserSchema = new Schema({
email: {
type: String,
unique: true,
lowercase: true
},
password: String,
profile: {
name: {
type: String,
default: ''
},
picture: {
type: String,
default: ''
}
},
address: String,
history: [{
date: Date,
paid: {
type: Number,
default: 0
},
// item:
}]
});

/* Hash the password */
UserSchema.pre('save', function (next) {
var user = this;
if(!user.isModified('password')) {
return next();
}
bcrypt.genSalt(10, function (err, salt) {
if(err) return next(err);
bcrypt.hash(user.password, salt, null, function (err, hash) {
if(err) return next(err);
user.password = hash;
next();
});
});
});

/* Comparing typed password with that in DB */
UserSchema.methods.comparePassword = function (password) {
return bcrypt.compareSync(password, this.password);
}

module.exports = mongoose.model('User', UserSchema);


I tried disabling ssl connections as posted in other stackoverflow questions, but this was not helpful.



So can someone please help me to figure it out. It would be really helpful.



node --version    = v8.9.3
npm --version = 6.4.1
nodemon --version = 1.17.5
express --version = 4.16.0


Thanks







javascript node.js express postman






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 19 '18 at 3:49









DEEPESH KUMAR RDEEPESH KUMAR R

6610




6610













  • Try running without nodemon to see what the console output shows. Also, you should send a response to create-user even if user.save() fails.

    – Jim B.
    Nov 19 '18 at 3:53













  • @JimB. Yeah i tried running without nodemon. When I do the server connection is getting lost and exit from server. Can you please tell how to send response to create-user when user.save fails?

    – DEEPESH KUMAR R
    Nov 19 '18 at 3:55











  • Difficult to debug without your mongodb connection.

    – KibGzr
    Nov 19 '18 at 4:08











  • By any chance are you using any proxy in postman? You can check that by going to Settings > Proxy Sometimes I have seen people struggling with this issue.

    – Sivcan Singh
    Nov 19 '18 at 6:35











  • @SivcanSingh : Yeah i tried at first, but still facing the same issue

    – DEEPESH KUMAR R
    Nov 19 '18 at 8:24



















  • Try running without nodemon to see what the console output shows. Also, you should send a response to create-user even if user.save() fails.

    – Jim B.
    Nov 19 '18 at 3:53













  • @JimB. Yeah i tried running without nodemon. When I do the server connection is getting lost and exit from server. Can you please tell how to send response to create-user when user.save fails?

    – DEEPESH KUMAR R
    Nov 19 '18 at 3:55











  • Difficult to debug without your mongodb connection.

    – KibGzr
    Nov 19 '18 at 4:08











  • By any chance are you using any proxy in postman? You can check that by going to Settings > Proxy Sometimes I have seen people struggling with this issue.

    – Sivcan Singh
    Nov 19 '18 at 6:35











  • @SivcanSingh : Yeah i tried at first, but still facing the same issue

    – DEEPESH KUMAR R
    Nov 19 '18 at 8:24

















Try running without nodemon to see what the console output shows. Also, you should send a response to create-user even if user.save() fails.

– Jim B.
Nov 19 '18 at 3:53







Try running without nodemon to see what the console output shows. Also, you should send a response to create-user even if user.save() fails.

– Jim B.
Nov 19 '18 at 3:53















@JimB. Yeah i tried running without nodemon. When I do the server connection is getting lost and exit from server. Can you please tell how to send response to create-user when user.save fails?

– DEEPESH KUMAR R
Nov 19 '18 at 3:55





@JimB. Yeah i tried running without nodemon. When I do the server connection is getting lost and exit from server. Can you please tell how to send response to create-user when user.save fails?

– DEEPESH KUMAR R
Nov 19 '18 at 3:55













Difficult to debug without your mongodb connection.

– KibGzr
Nov 19 '18 at 4:08





Difficult to debug without your mongodb connection.

– KibGzr
Nov 19 '18 at 4:08













By any chance are you using any proxy in postman? You can check that by going to Settings > Proxy Sometimes I have seen people struggling with this issue.

– Sivcan Singh
Nov 19 '18 at 6:35





By any chance are you using any proxy in postman? You can check that by going to Settings > Proxy Sometimes I have seen people struggling with this issue.

– Sivcan Singh
Nov 19 '18 at 6:35













@SivcanSingh : Yeah i tried at first, but still facing the same issue

– DEEPESH KUMAR R
Nov 19 '18 at 8:24





@SivcanSingh : Yeah i tried at first, but still facing the same issue

– DEEPESH KUMAR R
Nov 19 '18 at 8:24












2 Answers
2






active

oldest

votes


















1














It looks like this call to bcrypt is quietly crashing:



bcrypt.hash(user.password, salt, null, function (err, hash) {


I am not sure where the null parameter came from. If you remove it:



bcrypt.hash(user.password, salt, function (err, hash) {


It no longer crashes, and returns no error.






share|improve this answer


























  • I tried but it shows the same error Could not get any response in Postman.

    – DEEPESH KUMAR R
    Nov 19 '18 at 4:04











  • How are you debugging? Just running at the command line, or using vscode or another ide?

    – Jim B.
    Nov 19 '18 at 4:05











  • What was the output in the node console prior to the nodemon app crashed message?

    – Jim B.
    Nov 19 '18 at 4:07











  • Debugging from command line. I am getting this error: SyntaxError: Unexpected token - in JSON at position 0

    – DEEPESH KUMAR R
    Nov 19 '18 at 4:16











  • Looks like malformed JSON coming from the client. Can you add your client code?

    – Jim B.
    Nov 19 '18 at 4:17



















0














I was facing the same issue, got it resolved by downgrading the bcrypt package to 2.0.1.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53368070%2funable-to-create-user-using-postman-nodemon-app-crashed%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    It looks like this call to bcrypt is quietly crashing:



    bcrypt.hash(user.password, salt, null, function (err, hash) {


    I am not sure where the null parameter came from. If you remove it:



    bcrypt.hash(user.password, salt, function (err, hash) {


    It no longer crashes, and returns no error.






    share|improve this answer


























    • I tried but it shows the same error Could not get any response in Postman.

      – DEEPESH KUMAR R
      Nov 19 '18 at 4:04











    • How are you debugging? Just running at the command line, or using vscode or another ide?

      – Jim B.
      Nov 19 '18 at 4:05











    • What was the output in the node console prior to the nodemon app crashed message?

      – Jim B.
      Nov 19 '18 at 4:07











    • Debugging from command line. I am getting this error: SyntaxError: Unexpected token - in JSON at position 0

      – DEEPESH KUMAR R
      Nov 19 '18 at 4:16











    • Looks like malformed JSON coming from the client. Can you add your client code?

      – Jim B.
      Nov 19 '18 at 4:17
















    1














    It looks like this call to bcrypt is quietly crashing:



    bcrypt.hash(user.password, salt, null, function (err, hash) {


    I am not sure where the null parameter came from. If you remove it:



    bcrypt.hash(user.password, salt, function (err, hash) {


    It no longer crashes, and returns no error.






    share|improve this answer


























    • I tried but it shows the same error Could not get any response in Postman.

      – DEEPESH KUMAR R
      Nov 19 '18 at 4:04











    • How are you debugging? Just running at the command line, or using vscode or another ide?

      – Jim B.
      Nov 19 '18 at 4:05











    • What was the output in the node console prior to the nodemon app crashed message?

      – Jim B.
      Nov 19 '18 at 4:07











    • Debugging from command line. I am getting this error: SyntaxError: Unexpected token - in JSON at position 0

      – DEEPESH KUMAR R
      Nov 19 '18 at 4:16











    • Looks like malformed JSON coming from the client. Can you add your client code?

      – Jim B.
      Nov 19 '18 at 4:17














    1












    1








    1







    It looks like this call to bcrypt is quietly crashing:



    bcrypt.hash(user.password, salt, null, function (err, hash) {


    I am not sure where the null parameter came from. If you remove it:



    bcrypt.hash(user.password, salt, function (err, hash) {


    It no longer crashes, and returns no error.






    share|improve this answer















    It looks like this call to bcrypt is quietly crashing:



    bcrypt.hash(user.password, salt, null, function (err, hash) {


    I am not sure where the null parameter came from. If you remove it:



    bcrypt.hash(user.password, salt, function (err, hash) {


    It no longer crashes, and returns no error.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Nov 19 '18 at 15:37

























    answered Nov 19 '18 at 3:58









    Jim B.Jim B.

    2,6641929




    2,6641929













    • I tried but it shows the same error Could not get any response in Postman.

      – DEEPESH KUMAR R
      Nov 19 '18 at 4:04











    • How are you debugging? Just running at the command line, or using vscode or another ide?

      – Jim B.
      Nov 19 '18 at 4:05











    • What was the output in the node console prior to the nodemon app crashed message?

      – Jim B.
      Nov 19 '18 at 4:07











    • Debugging from command line. I am getting this error: SyntaxError: Unexpected token - in JSON at position 0

      – DEEPESH KUMAR R
      Nov 19 '18 at 4:16











    • Looks like malformed JSON coming from the client. Can you add your client code?

      – Jim B.
      Nov 19 '18 at 4:17



















    • I tried but it shows the same error Could not get any response in Postman.

      – DEEPESH KUMAR R
      Nov 19 '18 at 4:04











    • How are you debugging? Just running at the command line, or using vscode or another ide?

      – Jim B.
      Nov 19 '18 at 4:05











    • What was the output in the node console prior to the nodemon app crashed message?

      – Jim B.
      Nov 19 '18 at 4:07











    • Debugging from command line. I am getting this error: SyntaxError: Unexpected token - in JSON at position 0

      – DEEPESH KUMAR R
      Nov 19 '18 at 4:16











    • Looks like malformed JSON coming from the client. Can you add your client code?

      – Jim B.
      Nov 19 '18 at 4:17

















    I tried but it shows the same error Could not get any response in Postman.

    – DEEPESH KUMAR R
    Nov 19 '18 at 4:04





    I tried but it shows the same error Could not get any response in Postman.

    – DEEPESH KUMAR R
    Nov 19 '18 at 4:04













    How are you debugging? Just running at the command line, or using vscode or another ide?

    – Jim B.
    Nov 19 '18 at 4:05





    How are you debugging? Just running at the command line, or using vscode or another ide?

    – Jim B.
    Nov 19 '18 at 4:05













    What was the output in the node console prior to the nodemon app crashed message?

    – Jim B.
    Nov 19 '18 at 4:07





    What was the output in the node console prior to the nodemon app crashed message?

    – Jim B.
    Nov 19 '18 at 4:07













    Debugging from command line. I am getting this error: SyntaxError: Unexpected token - in JSON at position 0

    – DEEPESH KUMAR R
    Nov 19 '18 at 4:16





    Debugging from command line. I am getting this error: SyntaxError: Unexpected token - in JSON at position 0

    – DEEPESH KUMAR R
    Nov 19 '18 at 4:16













    Looks like malformed JSON coming from the client. Can you add your client code?

    – Jim B.
    Nov 19 '18 at 4:17





    Looks like malformed JSON coming from the client. Can you add your client code?

    – Jim B.
    Nov 19 '18 at 4:17













    0














    I was facing the same issue, got it resolved by downgrading the bcrypt package to 2.0.1.






    share|improve this answer




























      0














      I was facing the same issue, got it resolved by downgrading the bcrypt package to 2.0.1.






      share|improve this answer


























        0












        0








        0







        I was facing the same issue, got it resolved by downgrading the bcrypt package to 2.0.1.






        share|improve this answer













        I was facing the same issue, got it resolved by downgrading the bcrypt package to 2.0.1.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 16 '18 at 12:22









        Kunal VirkKunal Virk

        313




        313






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53368070%2funable-to-create-user-using-postman-nodemon-app-crashed%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            鏡平學校

            ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

            Why https connections are so slow when debugging (stepping over) in Java?