Failed due to unhealthy allocations - not rolling back to stable job version 6 as current job has same specification and deploying as v7

1

I keep getting this error when deploying. I had deployed successfully before though. How do I solve this?

2

The port in the fly.toml is 8080; so as in the Dockerfile

3

I haven’t seen such an error before.

Can you see what the output from fly status --all -a <app-name> tells you?

Check if the health checks are setup approp, and the server is in fact listening on the right ports and interfaces.

4

It appears there was no running instance. I did a restart and it worked.

2 Likes