Librechat exits with code 0 on start

[mschultz-aofl]

Hey, I deployed librechat with essentially the helm chart, and for some reason, the application is not listening on any port as far as I can tell, and exits with code 0 after ~15s or so. There's not much in the logs either, but I pasted them below. Any idea where to look for debugging?

k logs librechat-6c5f74f47b-pwfsd -f
> [email protected] backend
> cross-env NODE_ENV=production node api/server/index.js
2025-06-03 23:11:37 info: [Optional] Redis not initialized.
2025-06-03 23:11:39 info: [Optional] IoRedis not initialized for rate limiters.
2025-06-03 23:11:48 error: An error occurred while fixing Token indexes: Operation `tokens.indexes()` buffering timed out after 10000ms
npm notice
npm notice New major version of npm available! 10.8.2 -> 11.4.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.4.1
npm notice To update run: npm install -g [email protected]
npm notice

[danny-avila]

I didn't write the helm chart but this kind of error happens when the mongo connection is not successful. Are you setting MONGO_URI to anything?

[mschultz-aofl]

Yeah we're using AWS DocuDB for our mongo connection. The value is MONGO_URI=mongodb://root:<PASSWORD>@librechat.cluster-REDACTED.us-west-2.docdb.amazonaws.com:27017/?replicaSet=rs0&readPreference=secondaryPreferred&retryWrites=false

I can confirm that the cluster is up and running via the AWS console's connection, but that uses a different authentication mechanism. Is there a way to enable verbose logging so I can see why it's failing to connect? I'm following this guide for the connection string: https://docs.aws.amazon.com/documentdb/latest/developerguide/connect_programmatically.html#connect_programmatically-tls_disabled

and confirmed TLS is disabled on the cluster.

[danny-avila]

Could this be related? double check the query string:

Automattic/mongoose#15018 (comment)

Was reported here for DocumentDB with a different error:

#5574

[mschultz-aofl]

Hey thanks for pointing me in that direction. Turns out it was a firewall rule I wasn't aware of from our IT side, but took a dig into the logs on disk and found that connection error - no change to the auth required. Turns out a lot of logging doesn't go to the console, even with DEBUG_CONSOLE enabled which surprised me. Thanks for your help!