6 months ago
Hi Railway Support,
I need urgent help recovering access to my Database (MongoDB) after a migration/recreation incident.
Background: My Database service was migrated/recreated by Railway,
What I need: Access to my Database again.
Restore the original Database initialization credentials that were used with this volume?
Reset the volume's authentication system while preserving my application data?
Provide an alternative way to access my data from this volume?
This is blocking my entire application. I wouldn't have encountered this issue if the migration hadn't initially occurred.
Please help - thank you!
10 Replies
6 months ago
Did you, at some point, change the mongo credentials? I cannot access it via the Database UI
Status changed to Awaiting User Response Railway • 6 months ago
6 months ago
Yes I did that was 3 months ago and I was able to access the db no problem. By the way i made a backup then not sure if before or after changing the variables.
Status changed to Awaiting Railway Response Railway • 6 months ago
6 months ago
I am unsure what can be the issue since it does appear that your data is present on disk.
With that said, if you want to run commands against the container, you can SSH onto the instance to perform a credential reset.
Attachments
Status changed to Awaiting User Response Railway • 6 months ago
6 months ago
Ok, what would explain the fact that all of sudden my credentials do not work?
Also is there a way for me to download the backup?
Status changed to Awaiting Railway Response Railway • 6 months ago
6 months ago
By the way I am at my wits end here... how does SSL help, can I specify no-auth for the instance and restart?
6 months ago
Ok, I guess there is nobody who can remotely answer to my issue that I did not create.. I will try restoring the old db and perhaps that will work.
Status changed to Awaiting User Response Railway • 6 months ago
6 months ago
By altering the password but not committing it, this problem was created. You will now need to SSH in and reset the credentials.
6 months ago
ok, but if you take time to respond, can you please provide a complete solution? first of all how is it that "I" created a problem? everything was working fine until you guys decided to migrate. So at minimum, can you please provide actual support and not just bits of sentences here and there.
I asked:
1) Is it possible to download my backup db? -- NO ANSWER FROM RAILWAY
2) is possible to specifiy no-auth when starting db? -- NO ANSWER FROM RAILWAY
3) how does SSH help? The one bit of information provided was to copy paste tthe SSH command does not work or DOES NOT EXIST
Attachments
Status changed to Awaiting Railway Response Railway • 6 months ago
5 months ago
Hi there, apologies we’ll do our best to help you out and I’ll try to address your concerns one by one:
1) You can use mongodump https://www.mongodb.com/docs/database-tools/mongodump/ to get the current data - you could have to restore a backup to be able to get the older data but of course that would remove the current data. I would advice to run a manual backup right before you take the mongodump. You will have to SSH into the machine for this.
2) I wouldn't recommend this as it is your production environment but you would have to do this within mongo. I would suggest exploring their documentation and then adding a flag such as --noauth to your start command https://www.mongodb.com/docs/manual/reference/program/mongod/#std-option-mongod.--noauth
3) Once you SSH it will help you be within the machine where your database is. You can then update the credentials. Could you please make sure to update your railway CLI for this to work and run this directly from your terminal?
Hope this helps you get closer to resolving the issue. If you need further assistance or specific commands for SSH, please let me know!
Status changed to Awaiting User Response Railway • 6 months ago
4 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 4 months ago