Machine status remains in warning state

Hi there,

we have a fairly simple Django application deployed on Fly. We’ve recently had major problems with just about every deploy failing for some reason. The fly status interface says that the health check has failed, but when looking at our machine logs we can clearly see that the machine has responded with a 200 OK status.

Here’s a snippet of the relevant section of our fly.toml:

[http_service]
  internal_port = 8000
  force_https = true
  auto_stop_machines = 'stop'
  auto_start_machines = true
  min_machines_running = 1
  processes = ['app']

[[http_service.checks]]
  grace_period = "5s"
  interval = "30s"
  method = "GET"
  timeout = "1s"
  path = "/_health/"

  [http_service.checks.headers]
    Host = "<domain>.com"
    X-Sentry-Ignore = "true"

As mentioned, we see the machine come up, we see in request logs from the machine that it responds with 200 on /_health/, but the checks in fly.io’s UI never turn green. Have we missed something obvious?

We’ve temporarily removed the health checks and our app is now deploying just fine, so something seems to be wrong with the health check setup

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