When I am deploying I get the error Failed due to unhealthy allocations [image]

3000 is the wrong port. Apps with the node builtin (and most of the builtins) should be listening on port 8080. That’s why it says internal port 8080 in the fly.toml. I just deployed an node app with express-rate-limit and its responding fine over port 8080. Switch your port to 8080 or set it via th…

Failed due to unhealthy allocations

Codepope September 10, 2020, 2:56pm 10

Those aren’t going to take long and are unlikely to block the app from getting to the listener in time.

Quick check, what port is the app listening on?

Fly deploy failed due to unhealthy allocations

Topic		Replies	Views
Failed due to unhealthy allocations - not rolling back to stable job version 6 as current job has same specification and deploying as v7	3	596	February 9, 2023
Failed due to unhealthy allocations: port setting ? Questions / Help	6	723	May 28, 2023
More unhealthy allocations	1	266	September 12, 2022
Failed due to unhealthy allocations on nodejs running app	1	335	February 21, 2022
Help with deploy error: Failed due to unhealthy allocations Questions / Help	7	781	April 25, 2023

Failed due to unhealthy allocations

Related topics