502 with `auto_stop_machines = true`

I like this feature but isn’t it supposed to simply wait until the machine has started? This feature feels a bit useless to me if it gives 502 errors :grimacing:

A cold start in the morning when customers start using my app is acceptable, but a 502 is not.

We’re not running nginx in front of your app, so the 502 is not coming from fly.io. Are you running nginx?

Ah, right! Yes I do use Nginx, I’m using the default Laravel config. So it’s directing traffic to my machine before it’s done booting I suppose? Would that be solved by defining an http health check?

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.