6 days ago
Mongodb is up and added whitelist ip 0.0.0.0/0
crash log
{
"message": "Kind: Server selection timeout: No available servers. Topology: { Type: ReplicaSetNoPrimary, Set Name: atlas-n9gp9i-shard-0, Servers: [ { Address: ac-fgc4zik-shard-00-01.t5kfhtz.mongodb.net:27017, Type: Unknown, Error: Kind: I/O error: timed out, labels: {}, source: None }, { Address: ac-fgc4zik-shard-00-00.t5kfhtz.mongodb.net:27017, Type: Unknown, Error: Kind: I/O error: timed out, labels: {}, source: None }, { Address: ac-fgc4zik-shard-00-02.t5kfhtz.mongodb.net:27017, Type: Unknown, Error: Kind: I/O error: timed out, labels: {}, source: None } ] }, labels: {}, source: None",
"severity": "error",
"attributes": {
"level": "error"},
"tags": {
"project": "067c2394-0729-4fd2-adf3-13cafbf332c0",
"environment": "24b058e6-6ca8-435c-be9a-f40becacc46f",
"service": "6d031d25-6ad0-4dd9-b09b-7b1ad6c85b7c",
"deployment": "79172029-912c-4b75-975f-32521b4b6fb4",
"replica": "08df412c-6856-4984-a2eb-a0179a559320"},
"timestamp": "2026-05-17T07:03:29.617712791Z"
}
1 Replies
6 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 6 days ago
5 days ago
Use the Atlas SRV connection string (mongodb+srv://...) with tls=true, ensure Railway outbound networking is allowed in Atlas Network Access, and test connectivity from inside the container because this looks like a Railway-to-Atlas networking/DNS timeout issue.
this is not a MongoDB whitelist issue anymore — the ReplicaSetNoPrimary + I/O error: timed out error