# Fly.io Machines Proxy Timeout **URL:** \ **Category:** Questions / Help\ **Created:** [September 16, 2022, 9:00pm UTC](https://community.fly.io/t/fly-io-machines-proxy-timeout/7217 "2022-09-16T21:00:02Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![ignoramous](https://avatars.discourse-cdn.com/v4/letter/i/a9adbd/32.png) [@ignoramous](https://community.fly.io/u/ignoramous)\ **Post date:** [September 19, 2022, 9:08pm UTC](https://community.fly.io/t/fly-io-machines-proxy-timeout/7217/5 "2022-09-19T21:08:09Z")
Gotcha. Btw, you can straight up hit the GraphQL (?) / REST (?) Machine APIs from within Machine VMs via `_api.internal`: [Fly Machines Manager - #2 by kurt](https://community.fly.io/t/fly-machines-manager/6236/2) > [@sascha-m10](#): > > If you look at the error I sent above, it seems like there is some issue with resolving the [Fly.io](http://Fly.io) machine API itself. I’m not sure what causes this. True. It is upto Fly engs to know what causes it as frequently as you report to have encountered them. I guess, you can treat the API as unstable and address it with retries, graceful degradation, monitoring and alerts, workarounds, etc. That said, `flyctl-proxy` [_is_ running `wireguard`](https://community.fly.io/t/remote-chrome-dev-tools-debugging/6026/3) (like you pointed out), and I don’t think is intended for production use (I may be wrong, of course). Fwiw, Machines themselves have sharp edges. Just today a Machine VM was stuck in `replacing` state and blocked all subsequent `deploy`s for me. I had to rid of it with a `-f`: `fly m remove -a -f` 🤷 --- _[View the full topic](https://community.fly.io/t/fly-io-machines-proxy-timeout/7217)._