Mongoose error: The uri parameter to openuri() must be string, got “object”. Make sure the first...
0
Why am I getting this error if i have connected to databases before this way?
Here is my code:
const express = require('express');
const router = express.Router();
const mongoose = require('mongoose');
const Player = require('../models/player'); //import player database
const db = mongoose.connect('mongodb://user:pass@ds263493.mlab.com:63493/user', { useNewUrlParser: true });
mongoose.Promise = global.Promise; //Promise type avoids warnings mongoose throws
mongoose.connect(db, function(err)
{
if(err){
console.error("Error! "+ err);
}
});
router.get('/players', function(req, res) //make req to players
{
console.log('Get request for all players');
Player.find({}) //connected to players collection in database
.exec(function(err, players) //once players are found, send as response to browser
{
if(err)
{
console.log("Error retrieving players");
}
else
{
res.json(players);
}
})
});
module.exports = router;
I changed the username and password for database to default, just for this question, that is not the problem.
Somehow it is saying the parameter for mongoose.connect("") is not a string when it is, i even tried useNewUrlParser:true, but it is still giving me same error.
node.js mongodb mongoose mean-stack
asked Nov 21 at 3:32
james
556
add a comment |
0
Why am I getting this error if i have connected to databases before this way?
Here is my code:
const express = require('express');
const router = express.Router();
const mongoose = require('mongoose');
const Player = require('../models/player'); //import player database
const db = mongoose.connect('mongodb://user:pass@ds263493.mlab.com:63493/user', { useNewUrlParser: true });
mongoose.Promise = global.Promise; //Promise type avoids warnings mongoose throws
mongoose.connect(db, function(err)
{
if(err){
console.error("Error! "+ err);
}
});
router.get('/players', function(req, res) //make req to players
{
console.log('Get request for all players');
Player.find({}) //connected to players collection in database
.exec(function(err, players) //once players are found, send as response to browser
{
if(err)
{
console.log("Error retrieving players");
}
else
{
res.json(players);
}
})
});
module.exports = router;
I changed the username and password for database to default, just for this question, that is not the problem.
Somehow it is saying the parameter for mongoose.connect("") is not a string when it is, i even tried useNewUrlParser:true, but it is still giving me same error.
node.js mongodb mongoose mean-stack
asked Nov 21 at 3:32
james
556
1
Not sure where you saw that syntax, but it'smongoose.connect(<uri>,<options>, function(err) { ...You calledconnecttwice, and tried to pass the result in the second time. Just do it once correctly.
– Neil Lunn
Nov 21 at 3:35
@NeilLunn i see, i didn't notice i was connecting twice. Worked for the guy who did the youtube video...haha. Thanks!!
– james
Nov 21 at 3:37
1
I would advise referencing official documentation over some video. The documentation could be improved to actually say this, but the recommended way is with the callback/Promise implementation. Legacy forms which don't force you to actually await the connection have reliability issues, and other potential pitfalls in your code unless you really know what you are doing.
– Neil Lunn
Nov 21 at 3:44
add a comment |
0
0
0
Why am I getting this error if i have connected to databases before this way?
Here is my code:
const express = require('express');
const router = express.Router();
const mongoose = require('mongoose');
const Player = require('../models/player'); //import player database
const db = mongoose.connect('mongodb://user:pass@ds263493.mlab.com:63493/user', { useNewUrlParser: true });
mongoose.Promise = global.Promise; //Promise type avoids warnings mongoose throws
mongoose.connect(db, function(err)
{
if(err){
console.error("Error! "+ err);
}
});
router.get('/players', function(req, res) //make req to players
{
console.log('Get request for all players');
Player.find({}) //connected to players collection in database
.exec(function(err, players) //once players are found, send as response to browser
{
if(err)
{
console.log("Error retrieving players");
}
else
{
res.json(players);
}
})
});
module.exports = router;
I changed the username and password for database to default, just for this question, that is not the problem.
Somehow it is saying the parameter for mongoose.connect("") is not a string when it is, i even tried useNewUrlParser:true, but it is still giving me same error.
node.js mongodb mongoose mean-stack
asked Nov 21 at 3:32
james
556
Why am I getting this error if i have connected to databases before this way?
Here is my code:
const express = require('express');
const router = express.Router();
const mongoose = require('mongoose');
const Player = require('../models/player'); //import player database
const db = mongoose.connect('mongodb://user:pass@ds263493.mlab.com:63493/user', { useNewUrlParser: true });
mongoose.Promise = global.Promise; //Promise type avoids warnings mongoose throws
mongoose.connect(db, function(err)
{
if(err){
console.error("Error! "+ err);
}
});
router.get('/players', function(req, res) //make req to players
{
console.log('Get request for all players');
Player.find({}) //connected to players collection in database
.exec(function(err, players) //once players are found, send as response to browser
{
if(err)
{
console.log("Error retrieving players");
}
else
{
res.json(players);
}
})
});
module.exports = router;
I changed the username and password for database to default, just for this question, that is not the problem.
Somehow it is saying the parameter for mongoose.connect("") is not a string when it is, i even tried useNewUrlParser:true, but it is still giving me same error.
node.js mongodb mongoose mean-stack
node.js mongodb mongoose mean-stack
asked Nov 21 at 3:32
james
556
asked Nov 21 at 3:32
james
556
asked Nov 21 at 3:32
james
556
asked Nov 21 at 3:32
james
556
asked Nov 21 at 3:32
james
556
556
1
Not sure where you saw that syntax, but it'smongoose.connect(<uri>,<options>, function(err) { ...You calledconnecttwice, and tried to pass the result in the second time. Just do it once correctly.
– Neil Lunn
Nov 21 at 3:35
@NeilLunn i see, i didn't notice i was connecting twice. Worked for the guy who did the youtube video...haha. Thanks!!
– james
Nov 21 at 3:37
1
I would advise referencing official documentation over some video. The documentation could be improved to actually say this, but the recommended way is with the callback/Promise implementation. Legacy forms which don't force you to actually await the connection have reliability issues, and other potential pitfalls in your code unless you really know what you are doing.
– Neil Lunn
Nov 21 at 3:44
add a comment |
1
Not sure where you saw that syntax, but it'smongoose.connect(<uri>,<options>, function(err) { ...You calledconnecttwice, and tried to pass the result in the second time. Just do it once correctly.
– Neil Lunn
Nov 21 at 3:35
@NeilLunn i see, i didn't notice i was connecting twice. Worked for the guy who did the youtube video...haha. Thanks!!
– james
Nov 21 at 3:37
1
I would advise referencing official documentation over some video. The documentation could be improved to actually say this, but the recommended way is with the callback/Promise implementation. Legacy forms which don't force you to actually await the connection have reliability issues, and other potential pitfalls in your code unless you really know what you are doing.
– Neil Lunn
Nov 21 at 3:44
1
1
Not sure where you saw that syntax, but it's
mongoose.connect(<uri>,<options>, function(err) { ... You called connect twice, and tried to pass the result in the second time. Just do it once correctly.– Neil Lunn
Nov 21 at 3:35
Not sure where you saw that syntax, but it's
mongoose.connect(<uri>,<options>, function(err) { ... You called connect twice, and tried to pass the result in the second time. Just do it once correctly.– Neil Lunn
Nov 21 at 3:35
@NeilLunn i see, i didn't notice i was connecting twice. Worked for the guy who did the youtube video...haha. Thanks!!
– james
Nov 21 at 3:37
@NeilLunn i see, i didn't notice i was connecting twice. Worked for the guy who did the youtube video...haha. Thanks!!
– james
Nov 21 at 3:37
1
1
I would advise referencing official documentation over some video. The documentation could be improved to actually say this, but the recommended way is with the callback/Promise implementation. Legacy forms which don't force you to actually await the connection have reliability issues, and other potential pitfalls in your code unless you really know what you are doing.
– Neil Lunn
Nov 21 at 3:44
I would advise referencing official documentation over some video. The documentation could be improved to actually say this, but the recommended way is with the callback/Promise implementation. Legacy forms which don't force you to actually await the connection have reliability issues, and other potential pitfalls in your code unless you really know what you are doing.
– Neil Lunn
Nov 21 at 3:44
add a comment |
active
oldest
votes
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53404876%2fmongoose-error-the-uri-parameter-to-openuri-must-be-string-got-object-mak%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53404876%2fmongoose-error-the-uri-parameter-to-openuri-must-be-string-got-object-mak%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
1
Not sure where you saw that syntax, but it's
mongoose.connect(<uri>,<options>, function(err) { ...You calledconnecttwice, and tried to pass the result in the second time. Just do it once correctly.– Neil Lunn
Nov 21 at 3:35
@NeilLunn i see, i didn't notice i was connecting twice. Worked for the guy who did the youtube video...haha. Thanks!!
– james
Nov 21 at 3:37
1
I would advise referencing official documentation over some video. The documentation could be improved to actually say this, but the recommended way is with the callback/Promise implementation. Legacy forms which don't force you to actually await the connection have reliability issues, and other potential pitfalls in your code unless you really know what you are doing.
– Neil Lunn
Nov 21 at 3:44