Show an actionable error when Fastify isn't on the host

After spending a whole day on figuring out the issue with Fastify, I found out it’s the host! After resolving it by chance, I saw you exactly point to this issue here:

So, is there any possibility you can show a better error when this happens?
I was getting just: “Program exited with code 0”.
Even a link to the common troubleshooting solutions doc would’ve been better :slight_smile:


1 Like

Here is an example app we wrote a while back and since has changed a lot, but it at least has the fix to your issue I believe. We ran into the same issue if I remember correctly.

We’re working on better errors when health checks fail. The link to troubleshooting is a good idea!

You’ll find in the latest version of flyctl that this now happens on all failed deployments…

2020-12-16T11:16:03Z [info] [2020-12-16T11:16:03Z] Program exited with code: 0
2020-12-16T11:16:04Z [info] [    1.090683] reboot: Restarting system
***v7 failed - Failed due to unhealthy allocations - no stable job version to auto revert to

Troubleshooting guide at