zeabur-startup-order

A connection refused error occurs during startup when a service attempts to connect to a dependency like a database or Redis before that dependency is fully initialized and ready to accept connections.

To fix startup order connection refused errors, you can implement health check configurations on dependency services or add a command-line wait loop to ensure dependencies are ready before the dependent service launches.

A health check for startup dependencies is a configuration applied to services like databases to verify their readiness, ensuring dependent services only launch after the dependency is fully initialized and accepting connections.

Yes, you can use a command-line wait loop as an alternative method to resolve service startup issues when health check configurations cannot be applied directly to the dependency service.

You can restart a service after applying a startup order fix by using the provided quick restart command with the specific service ID to relaunch the dependent service successfully.