Railway•4mo ago

MongoDB is not working on the hosting

My bot uses mongo DB, writes a message there, takes it from the DB and sends it to the chat, on my personal pc everything works without errors, the bot calmly interacts in the DB, however when I run the same code on hosting, there are eternal errors.

Error saving the message: SSL handshake failed: ac-egvayl4-shard-00-01.rbw6t12.mongodb.net:27017: [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1129) (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms),SSL handshake failed: ac-egvayl4-shard-00-00.rbw6t12.mongodb.net:27017: [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1129) (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms),SSL handshake failed: ac-egvayl4-shard-00-02.rbw6t12.mongodb.net:27017: [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1129) (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms), Timeout: 30s, Topology Description: <TopologyDescription id: 66a4efa56c82852b552a1a21, topology_type: ReplicaSetNoPrimary, servers: [<ServerDescription ('ac-egvayl4-shard-00-00.rbw6t12.mongodb.net', 27017) server_type: Unknown, rtt: None, error=AutoReconnect('SSL handshake failed: ac-egvayl4-shard-00-00.rbw6t12.mongodb.net:27017: [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1129) (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms)')>, <ServerDescription ('ac-egvayl4-shard-00-01.rbw6t12.mongodb.net', 27017) server_type: Unknown, rtt: None, error=AutoReconnect('SSL handshake failed: ac-egvayl4-shard-00-01.rbw6t12.mongodb.net:27017: [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1129) (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms)')>, <ServerDescription ('ac-egvayl4-shard-00-02.rbw6t12.mongodb.net', 27017) server_type: Unknown, rtt: None, error=AutoReconnect('SSL handshake failed: ac-egvayl4-shard-00-02.rbw6t12.mongodb.net:27017: [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1129) (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms)')>]>

Error saving the message: SSL handshake failed: ac-egvayl4-shard-00-01.rbw6t12.mongodb.net:27017: [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1129) (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms),SSL handshake failed: ac-egvayl4-shard-00-00.rbw6t12.mongodb.net:27017: [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1129) (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms),SSL handshake failed: ac-egvayl4-shard-00-02.rbw6t12.mongodb.net:27017: [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1129) (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms), Timeout: 30s, Topology Description: <TopologyDescription id: 66a4efa56c82852b552a1a21, topology_type: ReplicaSetNoPrimary, servers: [<ServerDescription ('ac-egvayl4-shard-00-00.rbw6t12.mongodb.net', 27017) server_type: Unknown, rtt: None, error=AutoReconnect('SSL handshake failed: ac-egvayl4-shard-00-00.rbw6t12.mongodb.net:27017: [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1129) (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms)')>, <ServerDescription ('ac-egvayl4-shard-00-01.rbw6t12.mongodb.net', 27017) server_type: Unknown, rtt: None, error=AutoReconnect('SSL handshake failed: ac-egvayl4-shard-00-01.rbw6t12.mongodb.net:27017: [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1129) (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms)')>, <ServerDescription ('ac-egvayl4-shard-00-02.rbw6t12.mongodb.net', 27017) server_type: Unknown, rtt: None, error=AutoReconnect('SSL handshake failed: ac-egvayl4-shard-00-02.rbw6t12.mongodb.net:27017: [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1129) (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms)')>]>

Solution:

hey, this wouldnt be an issue with railway, you would need to get in contact with mongo

Jump to solution

4 Replies

Percy•4mo ago

Project ID: d490243c-94b3-470f-b39d-0a32c56fd03c

hycosiOP•4mo ago

d490243c-94b3-470f-b39d-0a32c56fd03c bump

Solution

Brody•4mo ago

hey, this wouldnt be an issue with railway, you would need to get in contact with mongo

hycosiOP•4mo ago

ok, ty

Gaming

Programming

MongoDB is not working on the hosting