Rails app restart loop prevents health check
The application started but did not answer on any port it publishes. The deploy log has the per-port result; a worker or queue-only app can ignore this. | The application is restarting, not running. Docker reports app (Restarting (1) 5 seconds ago). Nothing answered on any published port because the process keeps exiting. Read the container output with container_service_logs; the reason it exits is there.
TypeWarningAn issue PanelAlpha Engine catches around a deploy that does not break it. It tells you, before or after, that you may need to do something.
Seen5 times
WhereRails
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The image built and the container started, but the Rails process exited during application initialization while loading routes. Docker then restarted the container, so nothing remained listening on port 3000. The exact Ruby exception is outside the captured log tail and needs the full container output.
What the log looks like
Deploy log
Image project-app BuiltContainer project-app-1 StartedHealth check: http://[ip]:3000/ did not answer — Failed to connect to [ip] port 3000The application is restarting, not running. Docker reports app (Restarting (1) 4 seconds ago).app-1 | from .../publify_core-96c1f61b273e/config/routes.rb:3:in `<top (required)>'app-1 | from .../gems/railties-7.1.6/lib/rails/application/routes_reloader.rb:50:in `load'