# App down **URL:** \ **Category:** General\ **Created:** [July 28, 2022, 2:32am UTC](https://community.fly.io/t/app-down/6176 "2022-07-28T02:32:50Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![jascha](https://avatars.discourse-cdn.com/v4/letter/j/bcef8e/32.png) [@jascha](https://community.fly.io/u/jascha)\ **Post date:** [July 28, 2022, 2:32am UTC](https://community.fly.io/t/app-down/6176/1 "2022-07-28T02:32:50Z")
One of my app instances died randomly, I am getting only these errors in the logs: ```auto 2022-07-28T02:18:20Z proxy[Na4Rxxb6] iad [error]Error: timed out while connecting to app 2022-07-28T02:18:20Z proxy[Na4Rxxb6] iad [error]Error: timed out while connecting to app 2022-07-28T02:18:35Z proxy[Na4Rxxb6] iad [error]Error: timed out while connecting to app 2022-07-28T02:18:37Z proxy[Na4Rxxb6] iad [error]Error: timed out while connecting to app 2022-07-28T02:18:49Z proxy[Na4Rxxb6] iad [error]Error: timed out while connecting to app 2022-07-28T02:19:02Z proxy[Na4Rxxb6] iad [error]Error: timed out while connecting to app ``` Sure enough if I check the status it says that the health check for the iad location is critical: ```auto App Name = my-example-app Owner = my-example-org Version = 12 Status = running Hostname = my-example-app.fly.dev Instances ID PROCESS VERSION REGION DESIRED STATUS HEALTH CHECKS RESTARTS CREATED Na4Rxxb6 app 12 iad run running 1 total, 1 critical 0 2022-07-19T17:17:55Z xoZ634s5 app 12 ewr run running 1 total, 1 passing 0 2022-07-01T19:56:05Z CQslW63c app 12 yyz run running 1 total, 1 passing 0 2022-06-08T18:16:55Z ``` And if I check the instance ```auto Instance ID = Na4Rxxb6 Process = Version = 12 Region = iad Desired = run Status = running Health Checks = 1 total, 1 critical Restarts = 0 Created = 2022-07-19T17:17:55Z Recent Events TIMESTAMP TYPE MESSAGE 2022-07-19T17:17:44Z Received Task received by client 2022-07-19T17:18:28Z Task Setup Building Task Directory 2022-07-19T17:19:06Z Started Task started by client Checks ID SERVICE STATE OUTPUT 219dd48c285e84611f2e717kj tcp-443 critical dial tcp 172.19.36.162:443: i/o timeout ``` This seems very similar to [Any thoughts on why my app randomly died? - #2 by greg](https://community.fly.io/t/any-thoughts-on-why-my-app-randomly-died/4427/2) but this app is only running nginx. The only thing I am wondering: Why did the app not automatically restart upon having a failed instance. But it seems that the default for `restart_limit` is 0, which means it never restarts. So I will be adding that to my config files, still seems a bit of an odd choice as my developer expectation would be that a failed instance restarts automatically. ---
**Author:** ![jsierles](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/jsierles/32/595_2.png) [@jsierles](https://community.fly.io/u/jsierles)\ **Post date:** [July 28, 2022, 7:07am UTC](https://community.fly.io/t/app-down/6176/2 "2022-07-28T07:07:33Z")
Is there anything in `fly logs`? You can also use `fly ssh console -s` to log in to the specific instance to inspect it. ---
**Author:** ![jascha](https://avatars.discourse-cdn.com/v4/letter/j/bcef8e/32.png) [@jascha](https://community.fly.io/u/jascha)\ **Post date:** [July 28, 2022, 7:33am UTC](https://community.fly.io/t/app-down/6176/3 "2022-07-28T07:33:04Z")
Unfortunately not as the logs don’t go far enough back and the container itself just logs to `/dev/stdout`. A good reminder that I have to setup persistent logging for debugging these cases (would love to see [fly.io](http://fly.io) providing a solution for that build into the platform). It’s the first time a nginx container has crashed in 6+ months, so I don’t really expect it to happen again. If it does I have change dthe `restart_limit` to `5` which hopefully restarts the container (this was as well how I solved it). I just think `0` is not really a sane default for `restart_limit` but maybe I am missing something. ---
**Author:** ![jsierles](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/jsierles/32/595_2.png) [@jsierles](https://community.fly.io/u/jsierles)\ **Post date:** [July 28, 2022, 11:52am UTC](https://community.fly.io/t/app-down/6176/4 "2022-07-28T11:52:17Z")
We’ll take a look at the host the VM was on. Did you redeploy the app? ---
**Author:** ![jascha](https://avatars.discourse-cdn.com/v4/letter/j/bcef8e/32.png) [@jascha](https://community.fly.io/u/jascha)\ **Post date:** [July 28, 2022, 12:23pm UTC](https://community.fly.io/t/app-down/6176/5 "2022-07-28T12:23:34Z")
Yes, I just restarted it via `fly restart`. I can send you the exact app name and instance IDs via email if you like ---
**Author:** ![jascha](https://avatars.discourse-cdn.com/v4/letter/j/bcef8e/32.png) [@jascha](https://community.fly.io/u/jascha)\ **Post date:** [July 31, 2022, 8:16am UTC](https://community.fly.io/t/app-down/6176/6 "2022-07-31T08:16:34Z")
@jsierles one thing that still trips me up thinking about this: Why does the fly load balancer continues to send traffic to an unhealthy app? I kind of thought that having my app being run in multiple locations safeguards me as well against a single instance failing. Or is this not how it’s supposed to work? ---
**Author:** ![jsierles](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/jsierles/32/595_2.png) [@jsierles](https://community.fly.io/u/jsierles)\ **Post date:** [July 31, 2022, 3:45pm UTC](https://community.fly.io/t/app-down/6176/7 "2022-07-31T15:45:02Z")
The errors you see are the health checks timing out - not actual traffic. Does that make sense? ---
**Author:** ![jascha](https://avatars.discourse-cdn.com/v4/letter/j/bcef8e/32.png) [@jascha](https://community.fly.io/u/jascha)\ **Post date:** [August 1, 2022, 2:36am UTC](https://community.fly.io/t/app-down/6176/8 "2022-08-01T02:36:59Z")
But the instances where being served traffic from the fly proxy despite not responding which lead to actual downtime. ---
**Author:** ![jsierles](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/jsierles/32/595_2.png) [@jsierles](https://community.fly.io/u/jsierles)\ **Post date:** [August 1, 2022, 10:28am UTC](https://community.fly.io/t/app-down/6176/9 "2022-08-01T10:28:54Z")
OK - that’s certainly not the intended behavior. I’ll ask around about this and get back to you. ---
**Author:** ![rahmatjunaid](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/rahmatjunaid/32/837_2.png) [@rahmatjunaid](https://community.fly.io/u/rahmatjunaid)\ **Post date:** [August 5, 2022, 4:18pm UTC](https://community.fly.io/t/app-down/6176/10 "2022-08-05T16:18:49Z")
Hi @jascha just checking in are you still seeing this error message with your app? ---
**Author:** ![jascha](https://avatars.discourse-cdn.com/v4/letter/j/bcef8e/32.png) [@jascha](https://community.fly.io/u/jascha)\ **Post date:** [August 5, 2022, 5:51pm UTC](https://community.fly.io/t/app-down/6176/11 "2022-08-05T17:51:38Z")
Hey @rahmatjunaid, thanks for asking. I am of course no longer seeing it, this is a production app and any kind of downtime is really bad. That’s why I would like to understand why the fly load balancer kept sending traffic to an unhealthy instance instead of rerouting to a healthy one.