Can't connect to MongoDb
While following the guide to creating MongoDB Replica set, I was logged out of my database and now I am not able to connect to it.
f84b8495-1be2-40f3-b207-984d80785a2f
19 Replies
Project ID:
f84b8495-1be2-40f3-b207-984d80785a2f
you broke it bro
I broke it? What deos that mean this recoverable?
I don't know what you did to it, all I can say as these databases are provided to you completely unmanaged, if you did something to break it, there's not too much we can help you with unfortunately
I can tell you that I used this command
/bin/sh -c "ENCODED_KEY=$(echo -n "${AUTH_SECRET}" | base64) && TMP_KEYFILE=$(mktemp) && echo "${ENCODED_KEY}" > "${TMP_KEYFILE}" && chmod 600 "${TMP_KEYFILE}" && mongod --keyFile ${TMP_KEYFILE} --replSet rs0 --ipv6 --bind_ip ::,0.0.0.0"
Now it is stuck in a replica mode
look complicated to me
just use mongo in a single node π
I wanted changeStreams
atlas π
or even better yet, not using mongodb, use sql
So you are saying this is irrecoverable
I had some data I wanted from it.
I have zero clue, I don't use mongo
So I have to change my plan to pro
kek
what's that have to do with it?
So I can get pro support?
lol
that doesn't change the fact that railway isn't responsible and won't restore data if the user is at fault
remember, these databases are provided to you completely unmanaged
I am not blaming anyone I am asking for directions if someone has it.
I know, they don't have to lift a single finger for this but maybe someone knows something
hey if you wanna buy pro to have the team tell you that you shouldn't have ran commands you weren't familiar with, be my guest β€οΈπ€£
I hope that's not all they say.