<@UFLFZ89HT> after checking docker logs.
# orm-helpa
Aditya Gupta
02/25/2019, 7:47 PM@dan after checking docker logs.
j
Jenkins
02/25/2019, 7:48 PMAre you running a separate mongoDB or via
docker-composea
Aditya Gupta
02/25/2019, 7:50 PMi am using mongo atlas
Aditya Gupta
02/25/2019, 7:50 PMnot via docker-compose
j
Jenkins
02/25/2019, 7:55 PMDo you need to authenticate with mongoDB to access it and do you have any pre-existing data in there?
Jenkins
02/25/2019, 7:55 PMThis is out of my field, but I'll try my best to help 🙂
a
Aditya Gupta
02/25/2019, 8:01 PMThanks @Jenkins 🙂
Aditya Gupta
02/25/2019, 8:02 PMwell, Simple SRV is string is require to connect with your cluster like this one "mongodb+srv//<username><PASSWORD>@zipak-zqguc.mongodb.net/test", which contains username or password, and i am using same uri with mongoose, so i don't think authentication is problem here and currently there is no data in this cluster.
d
dan
02/25/2019, 8:11 PMYou also have to whitelist your IP
dan
02/25/2019, 8:11 PMor for now just whitelist any IP
a
Aditya Gupta
02/25/2019, 8:11 PMi did it already
j
Julián Álvarez
02/25/2019, 9:43 PMI tried two days ago and was not working too 😕
a
Aditya Gupta
02/25/2019, 9:58 PM@Julián Álvarez if i find something, i will let you know
j
Julián Álvarez
02/25/2019, 9:58 PM@Aditya Gupta 👌🏽
j
Jorge
02/28/2019, 6:02 AMi have the same issue
Jorge
02/28/2019, 9:01 AMlooks better when I append ?ssl=false to the connection string
Jorge
02/28/2019, 9:01 AMit does help
s
Siroj Inadïas
03/03/2019, 7:59 AMssl=false help (even if it raises some security questions), but still, prisma server is unable to connect to DB
Siroj Inadïas
03/03/2019, 8:00 AMYou can see it with “docker logs CONTAINER_ID” : [INFO] No server chosen by com.mongodb.async.client.ClientSessionHelper$1@3a0eb010 from cluster description ClusterDescription{type=REPLICA_SET, connectionMode=MULTIPLE, serverDescriptions=[ServerDescription{address=….
j
Jorge
03/03/2019, 6:11 PMI figured it out.. I turned ssl=true back on and downgraded the prisma docker image from 1.27 to 1.26.5
Jorge
03/03/2019, 6:11 PMseems to be a bug in 1.27
2 Views