Your MongoDB service in the "infra" project is logging repeated "pthread_create failed" and "Thread creation failed" errors, which means it cannot create new threads to handle incoming connections - this is typically caused by the service hitting its memory limit. You can check the Metrics tab for this service to see if memory usage is at its ceiling, and if so, consider increasing the memory limit in the service settings.

Railway doesn't manage your databases. Deploying a database is really just deploying a template.

Attach more information to help debug the issue. Logs etc

they offer the service to deploy mongoDB on their interface, but its always failing and is crap. weekly issues

Yes that is really just a template, a preconfigured service. They don't manage it for you.

MongoServerSelectionError: connection to [********]:27017 closed

at Topology.selectServer (/app/node_modules/mongodb/src/sdam/topology.ts:635:30)

at async AggregationCursor.cursorInit (/app/node_modules/mongodb/src/cursor/abstract_cursor.ts:949:21)

at async AggregationCursor.fetchBatch (/app/node_modules/mongodb/src/cursor/abstract_cursor.ts:987:7)

at async AggregationCursor.fetchBatch (/app/node_modules/mongodb/src/cursor/abstract_cursor.ts:987:7)

at async AggregationCursor.next (/app/node_modules/mongodb/src/cursor/abstract_cursor.ts:608:9)

at async AggregationCursor.[Symbol.asyncIterator] (/app/node_modules/mongodb/src/cursor/abstract_cursor.ts:502:26)

at async AggregationCursor.toArray (/app/node_modules/mongodb/src/cursor/abstract_cursor.ts:696:22)

at async Aggregate.exec (/app/node_modules/mongoose/lib/aggregate.js:1104:14)

there is no error in my mong db logs but i cannot connect to my db outside or inside doesnt matter

UP, we cannot see our mongo DB via railyaw or compass. We deployed our mongoDB via railway in first instance

also, all users see same user info right now!

really disappointed service again...

still issue is on