10 months ago
I have a mongodb instance which is successfully deployed according to the dashboard, but when I try to connect to it, the request times out.
I used the this template -> railwayapp-templates/mongo-replica-set
The instance worked fine for a while, but I did a redeploy and now I can no longer connect to it.
I tried redeploying again, restarting, redploying previous versions
Nothing gives an error but when trying to connect, it gives a timeout every time
Project ID: ddac6aa2-e521-40c0-8257-cbf31c0a29a0
7 Replies
Probably related because it never did this before, the CPU usage is on 0
This is pretty urgent, our app is currently down because of this, anyone of the railway team an idea how this can happen? All I did is use the redeploy and restart buttons in the UI
I really need a hand here, this does not look like something I can fix, I regenerated the TCP proxy, I redeployed, restarted, rolled back again, but the issue persists
Ok this is very weird, I duplicated my mongodb service
I was able to connect with the new service (still not with the original one)
So I moved the volume attached to the original service to the new one
But now I can no longer connect to the new service, but I can connect to the original one
10 months ago
Hello,
The newest MongoDB deployment has exited; you can check this since the status is listed as completed.