Proxy keeps waking machines in the nearest region, even if currently running one are below soft limit

I’m deploying my app on 3 continents, but want to keep only one machine overall to be up when traffic is below soft limit. But proxy always uses the machine in the nearest region, even when the machine isn’t up, which makes a nasty cold-start experience, instead of a quick response from a machine that is already up.

Docs are stating that “If all the running Machines are above their soft_limit setting, then the proxy starts a stopped Machine in the nearest region (if there are any stopped Machines).” which appears to be not true, at least in the case when there is just one machine per region.

It’s a question similar to Issue with fly proxy not routing to last running machine in multi-region phoenix app that unfortunately doesn’t get any answer.

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