Preventing 502s for initial wake up request call to Machines app

1

I’m using the tired proxy to stop my machine after a period of inactivity. Is there a way to prevent having my app’s endpoint (xxxx.fly.dev) throw a 502 bad gateway error when I hit it the first time after the machine has been stopped?

Ideally, i would see a cold start instead where the page just takes longer to load, instead of throwing a 502 immediately. Is there a way to set up this behavior? Do I need to do something like set up my own nginx reverse proxy?

2

Hi there!

Check out this post, which has a fork with an improvement to help with that condition: Improved tired-proxy for use with Fly Machines

(this is new to me also! PR’s welcome on the tired proxy!

1 Like
3

Thanks! Taking a look at this.

4

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