Hello, this is an English only community, please use English, thank you for understanding.

The ongoing incident should not affect connections, where is your database hosted?

my bank is on the us east server

Is it hosted on Railway?

Is it hosted on Railway? Yes

Are you connecting to it via the private network?

Are you connecting to it via the private network? No

Please go ahead and do that, you can use the private url variable.

After updating the url to private, and deploying again. the mongoDB database is not active.

What is the state of the database now?

CRASHED

Do you know why it crashed? check the deploy logs.

You are running on a NUMA machine. We suggest launching mongod like this to avoid performance problems: numactl --interleave=all mongod [other options]

/sys/kernel/mm/transparent_hugepage/enabled is 'always'. We suggest setting it to 'never' in this binary version

vm.max_map_count is too low

Updated wire specification

current featureCompatibilityVersion value

Clearing temp directory

Initializing cluster server parameters from disk

Flow Control is enabled on this deployment

Initializing full-time diagnostic data capture

Setting new configuration state

Timestamp monitor starting

Unclean full-time diagnostic data capture shutdown detected, found interim file, some metrics may have been lost

BACKTRACE

How much storage does your mongo database volume currently have used?

After checking, there is enough storage. You might need to handle your Mongo connections and reuse connections rather than reusing the existing connections.

Thanks,
Angelo

I uploaded my recent database, as it had little data, I deleted it and uploaded another one. So far the connection is ok.

That won't solve the root issue as the issue is likely how you are handling connections to the MongoDB instance.