Hello Railway Team,

I am experiencing a persistent connection issue with my MongoDB service and would appreciate your help.

My clients (MongoDB Compass and a local application) are unable to maintain a connection to my database. The server logs show that the connection and authentication are successful, but the client disconnects immediately afterward. The client-side error is usually a generic timeout (read ETIMEDOUT or similar).

Project/Service Information:

• Service: MongoDB

• Public TCP Proxy Address:hopper.proxy.rlwy.net:57293

What I've Done (Troubleshooting Steps):

1. Verified Server Health: I have redeployed the service multiple times. The deployment logs show a successful startup (mongod startup complete) with no crashes or memory errors.

2. Verified Successful Authentication: The server logs clearly show Connection accepted followed by Successfully authenticated for each of my connection attempts.

3. Verified Client Disconnection: Immediately after successful authentication, the logs show Connection ended and Interrupted operation as its client disconnected.

4. Exhaustive Connection String Testing: I have tried connecting with every possible parameter to rule out client-side issues, including:

   • connectTimeoutMS=60000

   • authSource=admin

   • tls=false

   • directConnection=true

Here is the full connection string I am using, which covers all troubleshooting steps: mongodb://mongo:******@hopper.proxy.rlwy.net:57293/?connectTimeoutMS=60000&authSource=admin&tls=false&directConnection=true

Despite all of this, the client still disconnects. This leads me to believe there may be a deeper issue with the TCP proxy or the platform environment that is causing the client driver to fail post-authentication.

Could you please take a look at my service to see if there are any underlying platform issues that could be causing this behavior? I have attached the server logs for your review.

Thank you for your time and assistance.