I'm deploying a Typesense server on Railway, but I'm encountering multiple issues that prevent the server from running stably and responding to requests. The issues include:

Connection Timeouts:

My application logs show repeated messages such as:

Request to Node 0 failed due to "ECONNABORTED timeout of 10000ms exceeded"

This indicates that my application is not able to establish a connection with the Typesense instance within the expected time frame.

Health Endpoint Unresponsive:
Attempts to access the health endpoint (e.g., via cURL) do not return a response, meaning the server isn’t starting correctly or isn’t accessible for health checks.

I have verified that:

My Railway configuration (host, port, protocol, API key) is correct.
The persistent volume is correctly bound to the Typesense service.
Only one instance is intended to be running, yet the error persists.
What steps can I take to clean up stale lock files, prevent multiple instances from interfering, and ensure that my Typesense server starts up and responds to connection requests properly on Railway?

View Deploy details

ⓘ Deployment information is only viewable by project members and Railway employees.