DeprecationWarning: current URL string parser is deprecated

Question

DeprecationWarning: current URL string parser is deprecated

foli opened this issue 7 years ago · 50 comments

(node:13868) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.

is there any way to pass the new option, the data does get saved though

Answer 1 · 2018-07-08T12:47:49.000Z

DeprecationWaringin: Current UEL string parser is deprecated and will be removed in future version

how to solve this error?

Answer 2 · 2018-07-09T06:29:15.000Z

use this
mongoose.connect('mongodb://user:password@sample.com:port/dbname', { useNewUrlParser: true })

Answer 3 · 2018-07-09T06:51:12.000Z

to avoid this problem use this
MongoClient.connect(url, {useNewUrlParser: true } )

Answer 4 · 2018-07-18T12:26:57.000Z

when using MongoClient.connect(url, {useNewUrlParser: true } ) Im getting this new warning

UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch()

Answer 5 · 2018-07-21T06:53:59.000Z

I have the same error. Any solution?

Answer 6 · 2018-07-23T11:28:22.000Z

Here is what I did
db.mongoConnect = () => {
mongoose.Promise = global.Promise
mongoose.connect(config.mongo.mongodb_url, {useNewUrlParser: true})
.then(() => {
console.log('mongoDB is connected...')
})
.catch((err) => {
throw err
})
}

Answer 7 · 2018-07-25T11:22:10.000Z

HI @grety22 , @Brayan1013 and @skyerh i have tried all your options but keep chasing my tail :) so any further ideas will be appreciated.

In its original form, this is what i had:
const express = require('express');
const mongoose = require('mongoose');
...
...
...

//DB Config
const db = require('./config/keys').mongoURI;

// Connect to MongoDB
mongoose.connect(db)
.then(() => console.log('MongoDB Connected'))
.catch((err) => console.log(err));

And it has worked fantastic for past three weeks until this morning. Then one by one i tried all your options but keep still getting the error below in different forms:

"DeprecationWarning: current URL string parser is deprecated, and will be removed in a future
version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect."

Then, I tried to adapt it to:

const express = require('express');
const mongoose = require('mongoose');
const { MongoClient } = require('mongodb');
const mongoURI = 'mongodb://localhost:27017';
...
...
...

//DB Config
const db = require('./config/keys').mongoURI;

// Connect to MongoDB
MongoClient.connect(db, { useNewUrlParser: true })
.then(() => console.log('MongoDB Connected'))
.catch((err) => console.log(err));

No luck. Instead, i now started getting errors:

"Server on port 5000
{ MongoNetworkError: failed to connect to server [ds227858.mlab.com:27858] on first connect [MongoNetworkError: connect ETIMEDOUT 52.49.63.15:27858]" etc etc

I also tried adapting what @grety22 and @skyerh has and still no luck.

Answer 8 · 2018-07-25T11:27:03.000Z

@Hixsav I think your error is different to the topic.
It looks like a network connection error ?

Server on port 5000
{ MongoNetworkError: failed to connect to server [ds227858.mlab.com:27858] on first connect [MongoNetworkError: connect ETIMEDOUT 52.49.63.15:27858]" etc etc

Answer 9 · 2018-07-25T11:43:41.000Z

Yes, but only after i try any of the solutions outlined here or elsewhere. Otherwise it remains as a deprecation warning. Which tells me the basic connection fundamentals seem ok, so long as the deprecation issue is solved. And when i try solve it, i get a connection error.

I think the connection error may have to do with with my keys.js file. But i am a newbie, have managed to scale this mountain until this morning. Its looking too high to scale beyond this..

Answer 10 · 2018-07-26T05:00:51.000Z

Tried to use {useNewUrlParser: true} to get rid of the deprecation warning, but it resulted in all the backend calls involving DB access stalling (spinner, nothing is returned). Reverting to useNewUrlParser: false resolved the issue for now.

Answer 11 · 2018-07-26T06:26:04.000Z

@jarecsni, can you perhaps explain further please, did u try using the original example above? Or are u referring to one u are also having problems with?

Answer 12 · 2018-07-26T07:17:07.000Z

@jarecsni i think i understand you now! I reverted to my original code, and it worked! Only when i pay attention to the deprecation warning does my code break. So, i resolved to do nothing for now. Talk about playing ostrich :)

Answer 13 · 2018-07-26T22:51:29.000Z

This works for me in the moment @Hixsav =)
mongoose.connect('url', { useNewUrlParser: true }, (err, res) => {
if (err) throw err;

console.log('Database online');

});

Answer 14 · 2018-07-27T07:32:08.000Z

Thanks @Brayan1013 i will give it a try! :)

Answer 15 · 2018-07-30T13:35:05.000Z

I get this warning
MongoError: port must be specified

after i added the code...
mongoose.connect('mongodb://user:password@sample.com:port/dbname', { useNewUrlParser: true })

Answer 16 · 2018-08-04T06:57:34.000Z

const dbpath = "mongodb://localhost:27017/batch2";

const mongo = mongoose.connect(dbpath, {useNewUrlParser: true });
mongo.then(() => {
console.log('connected');
}).catch((err) => {
console.log('err', err);
});

This works for me, without any error or warning.

Answer 17 · 2018-10-05T06:28:31.000Z

i had this issude. in server file for example app.js you should add this code

var mongoose = require('mongoose');
mongoose.connect('your url', { useNewUrlParser: true });
mongoose.set('useCreateIndex', true);

Answer 18 · 2018-10-21T14:24:11.000Z

Solution is :

const mongoose = require('mongoose');

mongoose.set('useNewUrlParser', true)
mongoose.set('useFindAndModify', true)
mongoose.set('useCreateIndex', true)

conn = mongoose.createConnection(dbUrl)

OR as module: (FOLDER CONFIG/MONGOOSE.JS)

const mongoose = require('mongoose')
const { mongo, env } = require('./vars')

mongoose.Promise = Promise

mongoose.connection.on('error', (err) => {
console.error(MongoDB connection error: ${err})
process.exit(-1)
})

if (env === 'development') {
mongoose.set('debug', true)
}

exports.connect = () => {
mongoose.connect(mongo.dbUrl, {
keepAlive: 1,
reconnectTries: 30,
useFindAndModify: true,
useCreateIndex: true,
useNewUrlParser: true,
user: process.env.MONGO_USER,
pass: process.env.MONGO_PASSWORD,
auth: {
authdb: process.env.MONGO_DB
}
}).then(() => { return mongoose.connection },
err => { console.log(err) }
)
}

AND USE IN SERVER/INDEX:

const mongoose = require('./config/mongoose')
mongoose.connect()

HERE MORE INFOS
https://mongoosejs.com/docs/deprecations.html

Answer 19 · 2018-10-22T10:42:55.000Z

Thanks a lot 👍

I made a slight edit to your solution from above as in:

mongoose.set('useFindAndModify', true);
mongoose.set('useCreateIndex', true);
mongoose
.connect(db, { useNewUrlParser: true })
.then(() => console.log('MongoDB Connected'))
.catch((err) => console.log(err));

And this helped my resolve my week-long issues! :-)

Answer 20 · 2018-11-12T19:13:40.000Z

Here is what I did
db.mongoConnect = () => {
mongoose.Promise = global.Promise
mongoose.connect(config.mongo.mongodb_url, {useNewUrlParser: true})
.then(() => {
console.log('mongoDB is connected...')
})
.catch((err) => {
throw err
})
}

what is initial db in that?
What should be there inside mongoConnect = () function parentheses?

Answer 21 · 2018-12-22T14:29:50.000Z

Here is how I did it, note that if your're needs are GridFS or GridFS Storage you need additional params.
// AS A MODULE "server/mongoMongoose.js"
// USE CONNECTION ON PROJECT AS: "mongoConnect"

const mongoose = require('mongoose');

const mongoConnect = () => {
mongoose
.connect(
database,
{
useNewUrlParser: true,
useFindAndModify: true,
useCreateIndex: true,
keepAlive: 1,
reconnectTries: 30 // keep an eye open for performance and security
}
)
.then(() => console.log('Connected To Mongo!!'))
.catch(err => console.log(err));
};

module.exports = mongoConnect;

Answer 22 · 2018-12-23T13:26:43.000Z

Hi guys, I simply added the {useNewUrlParser:true} argument and it passed perfectly with no error

mongoose.connect( 'URL string*' ,{useNewUrlParser:true});

Answer 23 · 2018-12-24T04:22:45.000Z

@dinho-afsn This worked for me. Hats off to you!

Answer 24 · 2018-12-24T07:10:59.000Z

am glad. Your welcome

…

On Mon, Dec 24, 2018 at 7:22 AM fromage9747 ***@***.***> wrote: @dinho-afsn <https://github.com/dinho-afsn> This worked for me. Hats off to you! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AfS34agMm5Bwtule_jjjveMNCSUkdw0jks5u8FaWgaJpZM4U8xND> .

Answer 25 · 2019-01-02T07:29:08.000Z

this works for me.

// DB config
const db = require("./config/keys").mongoURI;

//connect to mongodb
mongoose
.connect(
db,
{ useNewUrlParser: true }
)
.then(() => console.log("MongoDb Connected"))
.catch(err => console.log(err));

Answer 26 · 2019-01-02T10:56:48.000Z

@olufemi424 Can you please tell me your MongoDB URI so I can compare it with mine?

Answer 27 · 2019-01-02T11:15:59.000Z

hii @HixOba , can you please tell me what was the code that worked for you finally in both server.js and keys.js?

Answer 28 · 2019-01-02T18:43:03.000Z

this is my URI linked in my keys.js
module.exports = {
mongoURI: "mongodb://:@ds147354.mlab.com:47354/friendconnect"
};

Answer 29 · 2019-01-04T15:14:05.000Z

@olufemi424 Thanks! But for some reason it was not working for me (obviously after putting the right username and password). But my connection to the databse worked when I switched to MongoDB Atlas :)

Answer 30 · 2019-02-11T08:23:46.000Z

DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.
这个是怎么导致的?

Answer 31 · 2019-02-12T23:26:11.000Z

let options = {useNewUrlParser: true};
let uri = 'mongodb://localhost/yourdbname';

mongoose.connect(uri, options).then(
() => {
    console.log('Connected to the database!')
},
    err => { console.log('Error! Could not connect') }
);

Answer 32 · 2019-02-19T13:00:38.000Z

mongoose.connect('urlToDataBase', { useNewUrlParser: true })
This works for me.

Answer 33 · 2019-03-06T08:22:26.000Z

Here the doc explained the reason:
https://mongoosejs.com/docs/connections.html
https://mongoosejs.com/docs/deprecations.html
Unfortunately, while i use createConnection function like this:mongoose.createConnection('mongodb://127.0.0.1:27017/test', { useNewUrlParser: true });,the warning still there.I believe it's mongoose's unfixed bug.

The test is under mongoose@5.4.17 on mac.

Answer 34 · 2019-03-20T17:57:22.000Z

I tried all the alternatives above and realized that forgot to do the required steps to connect to MongoDB, which is installing and running mongo:
If you haven't tapped yet (using Homebrew):
brew tap mongodb/brew
then (assuming you don't want the enterprise version):
brew install mongodb-community@4.0
Run MongoDB:
mongod --config /usr/local/etc/mongod.conf

And at last start your app again.

Answer 35 · 2019-04-01T11:14:34.000Z

Does this issue have anything to do with TypeORM? Seems to be full of questions about mongoose?

Answer 36 · 2019-05-22T14:01:26.000Z

This worked for me:
mongoose.createConnection('mongodb://127.0.0.1:27017/test', { useNewUrlParser: true });

Answer 37 · 2019-07-19T11:40:57.000Z

mongoose.connect("mongodb://127.0.0.1:27017/vidly", { useNewUrlParser: true, useCreateIndex: true });

above code work for me , what was missing in my code initially is { useNewUrlParser: true, useCreateIndex: true } the ip & port number was different because i was making use of docker environment

Answer 38 · 2019-07-19T16:07:31.000Z

Thank you so much ❤️

…

On Fri, 19 Jul, 2019, 5:11 PM Alabi Temitope Wahab, < ***@***.***> wrote: mongoose.connect("mongodb://127.0.0.1:27017/vidly", { useNewUrlParser: true, useCreateIndex: true }); above code work for me , what was missing in my code initially is { useNewUrlParser: true, useCreateIndex: true } the ip & port number was different because i was making use of docker environment — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=ALBL4KGSQYPRNDAEQHKX67DQAGR45A5CNFSM4FHTCNB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2LMPYY#issuecomment-513198051>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALBL4KAWWXTEYCLCDLYNGMLQAGR45ANCNFSM4FHTCNBQ> .

Answer 39 · 2019-07-31T16:16:25.000Z

How would we do this if we are not using mongoose take the typescript mongo repo as an example. This is similar to how my project is setup.

So I do not have mongoose.connect() or MongoClient.connect(). I am using the following and ormconfig.json

// Connects to the Database
const connection: Connection = await createConnection();

{
    "type": "mongodb",
    "url": "mongodb+srv://x:y@cluster?retryWrites=true&w=majority",
}

Edit, connect takes in ConnectionOptions, I just didn't read the error properly. It was complaining about wanting the type too. Then I notice well I can just add the property to ormconfig.json.

{
    "type": "mongodb",
    "useNewUrlParser": true,
    "url": "mongodb+srv://x:y@cluster?retryWrites=true&w=majority",
}

Answer 40 · 2019-08-07T07:02:58.000Z

I wasted hours on trying to connect to mongodb

Hope this will help someone with "no users authenticated" and "failed to connect to server [localhost:27017] on first connect" errors

Create a user for your database :

use DBNAME
db.createUser(
  {
    user: "DBUSER",
    pwd: "DBPASS",
    roles: [ { role: "readWrite", db: "DBNAME" },
  }
)

Use 127.0.0.1 instead of localhost

const options: ConnectionOptions = {
    type: "mongodb",
    host: "127.0.0.1",
    database: "DBNAME",
    logging: ["query", "error"],
    username: "DBUSER",
    password: "DBPASS",
    synchronize: true,
    useNewUrlParser: true,
    entities: [User]
}

Check firewall for remote host
And finally connect to mongo..

await createConnection(options);

Answer 41 · 2019-11-17T08:51:20.000Z

Use to avoid deprecated method
mongoose.connect('mongodb://localhost:27017/dbname', { useNewUrlParser: true, useUnifiedTopology: true } )

Answer 42 · 2019-11-29T20:58:23.000Z

This works like sharm :

var mongoose = require('mongoose');

mongoose.connect(config.db_config.uri, { useUnifiedTopology: true ,useNewUrlParser: true })
    .then(() => {
        console.log('mongo connection created');
        resolve(db);
    })
    .catch(err => {
        console.log('error creating db connection: ' + err);
        reject(db);
    });
});

Good Luck !

Answer 43 · 2019-12-20T05:31:18.000Z

i think you have to try ip whitelist default 0.0.0.0/0

Answer 44 · 2020-01-12T22:55:19.000Z

Several issues can be happening:

Ip not whitelisted
Password needs to be encoded if it has special chars
Check the URL (if using atlas)
Then follow the errors until you get it to work

Answer 45 · 2020-03-30T07:57:47.000Z

i got this error
(node:6404) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.
(node:6404) DeprecationWarning: current Server Discovery and Monitoring engine is deprecated, and will be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUni

Answer 46 · 2020-05-10T11:55:37.000Z

i got this error
(node:6404) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.
(node:6404) DeprecationWarning: current Server Discovery and Monitoring engine is deprecated, and will be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUni

I raised this issue on stack overflow
on https://stackoverflow.com/questions/61711422/two-node63440-deprecation-warnings-at-the-same-time-current-url-string-parse

Answer 47 · 2020-08-08T07:08:25.000Z

(node:13868) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.

is there any way to pass the new option, the data does get saved though

const mongo = mongoose.connect(URI, {useNewUrlParser: true , useUnifiedTopology: true});
mongo.then(() => {
console.log('connected');
}).catch((err) => {
console.log('err', err);
});

Answer 48 · 2020-08-11T10:24:39.000Z

just add these all
//////////////////////////////////
1.useNewUrlParser: true
2. useFindAndModify: true,
3. useCreateIndex: true,
4.useUnifiedTopology: true
//////////////////////////////////////////
example:
mongoose
.connect(url, {
useNewUrlParser: true,
useFindAndModify: true,
useCreateIndex: true,
useUnifiedTopology: true,
})
.then(() => console.log("DB Connected"))
.catch((err) => console.error(err));
you will never see any warning :-)

Answer 49 · 2021-01-09T19:42:04.000Z

Use to avoid deprecated method
mongoose.connect('mongodb://localhost/db', { useNewUrlParser: true, useUnifiedTopology: true } )

This works for me (2021, January), getting warnings such:

(node:13552) DeprecationWarning: current Server Discovery and Monitoring engine is deprecated, and will be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUnifiedTopology: true } to the MongoClient constructor.
(Use node --trace-deprecation ... to show where the warning was created)

Answer 50 · 2021-01-23T10:41:47.000Z

(node:13868) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.

is there any way to pass the new option, the data does get saved though

use this : mongoose.connect('mongodb://localhost/playground',{useUnifiedTopology : true,useNewUrlParser : true})
It worked for me .. :)