# Fly Machines Manager

**URL:** <https://community.fly.io/t/fly-machines-manager/6236>\
**Category:** General\
**Created:** [August 3, 2022, 3:47pm UTC](https://community.fly.io/t/fly-machines-manager/6236 "2022-08-03T15:47:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kurt](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kurt/32/43757_2.png) [@kurt](https://community.fly.io/u/kurt)\
**Post date:** [August 3, 2022, 4:02pm UTC](https://community.fly.io/t/fly-machines-manager/6236/2 "2022-08-03T16:02:53Z")

</div>

This looks cool!

If this is running as a Fly app or machine, you don’t need wireguard. `_api.internal` will work just fine. Wireguard is just used to connect you to the same private network.

You can [`update` a machine](https://fly.io/docs/reference/machines/#update-a-machine) to get it using a new image.

When you say that machines take ~4 min to stop, do you mean when you’ve called “stop” via our API? Or your own idle logic is taking 4 min to exit?

If it’s taking a long time to stop when you call our API, it’s likely not handling `sigint` properly.

You can run `fly logs -i <machine id>` to see more about what’s happening in our infrastructure to debug stop timings.

---

_[View the full topic](https://community.fly.io/t/fly-machines-manager/6236)._