I found the actual root cause in the LibreChat container logs.

I deployed LibreChat twice using the "librechat-official" Railway template, and both deployments failed in the same way in the "sfo" region.

The LibreChat container log shows:

2026-09-23 23:12:21 error: Post-listen initialization failed: available disk space of 231440384 bytes is less than required minimum of 524288000

This means the LibreChat container detects only approximately 221 MB of available disk space, while LibreChat requires at least 500 MB to complete post-listen initialization.

The Railway deployment then fails at:

Network → Healthcheck

Healthcheck failure

So the healthcheck failure appears to be a consequence of the LibreChat process terminating because of insufficient available disk space.

What I would like to clarify is why this is happening on Railway.

According to Railway's current documentation, the Trial plan provides 1 GB of ephemeral storage per service. However, the LibreChat container is reporting only approximately 221 MB of available disk space.

Could this be related to:

• the "sfo" region or a specific Railway host/node,
• • the way ephemeral storage is allocated to this template,
• • the volume configuration of the LibreChat service,
• • or another limitation specific to the Trial environment?

I have also seen reports of LibreChat working when deployed in a different Railway region, so I would like to know whether changing regions is currently a valid workaround for this issue.

I deleted the project after reproducing the same failure twice, so I currently cannot provide a Deployment ID. However, the same error occurred on two separate deployments using the same Railway LibreChat template.

Could Railway please check why the LibreChat service in "sfo" is starting with only ~221 MB of available disk space despite the documented 1 GB ephemeral storage allowance for Trial services?

If this is a template or region-specific issue, please let me know whether the template needs to be updated or whether another Railway region should be used.

Update:

I changed the Railway deployment region from SFO (San Francisco) to Netherlands, and the LibreChat deployment completed successfully.

The same LibreChat template that failed twice in SFO due to:

Post-listen initialization failed: available disk space of 231440384 bytes is less than required minimum of 524288000

is now working correctly in the Netherlands region.

This suggests that the issue may be specific to the SFO region or to the available storage/resources on the SFO deployment environment, rather than the LibreChat configuration itself.

No other significant configuration changes were made; changing the region was sufficient to resolve the problem.

Additional update:

After changing the deployment region to Netherlands, the previous disk-space issue was resolved and the deployment initially started successfully.

However, the LibreChat service is now crashing repeatedly. Restarting the service does not resolve the issue; it starts and then crashes again shortly afterward.

So although changing the region resolved the original disk-space error, the deployment is currently not stable and continues to enter a crash/restart cycle.

I will provide the relevant crash logs if needed.

Can you provide the current crash logs?

My account is on a trial version, LibreChat either won't install or crashes due to insufficient storage space. The problem was resolved once I purchased and installed the paid plan.