#Econnrefused MONGODB
35 messages · Page 1 of 1 (latest)
Project ID: 4263b3c0-dd34-4b48-8661-ef64cb333f27
Nevermind, solved the issue!
don't open duplicate threads please
Sorry, I didn't understand this message "Nevermind, solved the issue!", I just thought the ticket was closed
have you redeployed your service since the database came back online?
Explain ?
The system was online A while ago today is offline 🙂
do a redeployment
push a commit
something to make railway rebuild your app since the db credentials have understandingly been regened
This database system 🙂
bruh
^
The system from railway.app just told me how to push the commit and it's not linked to github how 😂♥️
^
bruh
This is Database system
Give me the path, I will send it to technical support. The account is not with me
just tell them to redeploy the service
They are not programmers, they are clients
then who has the account with railway
client
A customer is not me, if it was me, I would have solved the problem 🤣
so why are you here if you cant fix the issue
The account is not with me, and I am not a subscriber to the Database system, so I do not know your practical environment because I have my own servers
locking thread